Want a better Minecraft server? Read about SpigotMC here!
Separate names with a comma.
Discussion in 'News and Announcements' started by md_5, Jan 14, 2018.
Just use the material enum and the valueOf method to get materials. No need to touch nms for that.
well i learned a thing from this so that's good xD
Unfortunately, lots of people don't understand to get the material name from the javadocs, and try the minecraft version anyways. That being said, maybe those people shouldn't be working with configs. I thought it'd be dumb to actually use a method of getting a material that creates two new useless instances. It was still a nice find, though.
the material enum now uses the same name as minecraft again. https://hub.spigotmc.org/stash/proj...a?at=96ba77c034bfcac7f5929eaccaefd36bf064a595
which is super good!
Sweet! Life will be easier being able to tell the difference between acacia_boat and BOAT_ACACIA
getMaterial(); How is it going to work with config?
I'm really looking forward for the new Version.
Is there a way to improve the current Scoreboard API? With some "new" Java Patterns like Observables and so on..
Like any other enum.
or even better
because this doesn't throw an exception if materialString is not a Material enum value or even even better
because this should support the internal lower case String IDs.
propose something. the team is already looking for new contributions from the community.
What deprecation will be completely phased out in 1.13? I know some things have been deprecated since forever. Are you planning to phase them all out?
Hey everyone. I happened to have a bug/thinghy when using PlayerInteractEntityEvent. I comment it here because it may be useful when making the 1.13 update.
That event doesn't fires at all when I click on an Arrow. Thanks!
Or finally undeprecate the Server#getOfflinePlayer(String name) method like it was intended from the beginning
The client is not sending an UseEntity packet for arrows as far as I know.
Then PR a caching solution which is improving lookup time.
To me, in some aspects, it would be much better to have a new API, but in others, it’ll cause me a few problems. Will this affect the plugin Vault?
no idea, however if it did, it wouldn't be hard to update for 1.13
You can look at all the deprecated methods that have been removed in the commit that is linked in the op.
Vault is an API, therefore it's not likely that anything will break.
*finds a way to break it*