Currently, player entities ignore the custom DATA_CUSTOM_NAME
EntityDataAccessor
, which sadly means that we cannot just easily change the name of the player entity. Hopefully in the future this functionality will be provided so we do not have to apply such hacky methods.
When starting the server:
- PaperClassloaderBytecodeModifier (server) is initialized, this is set in the ClassloaderBytecodeModifier (api) singleton class.
- Providers are created and loaded by a ProviderSource.
Providers provider = Providers.INSTANCE;
provider.addProviders(DirectoryProviderSource.INSTANCE, pluginfile.toPath());
With Minecraft becoming more data driven and registry based, we are unable to tap into this large part of the api due to us having improper ways to handle modifying these registries safely. Most adding into registries must be done at the very start of the server, where before they are frozen, preventing any type of modification after that point. Our current plugin system is built on the entire concept that there must be a server object being passed around, and because at that point there is no Minecraft server this system will not work at all.
We need to be able to introduce a way for plugins to provide a class that is called in this spot, where we can give access to certain registry based apis.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
### Keybase proof | |
I hereby claim: | |
* I am owen1212055 on github. | |
* I am owen1212055 (https://keybase.io/owen1212055) on keybase. | |
* I have a public key ASBtYYuE556RfR5xX_o8QLXO9ns1lCTIWQR4baS7B8Gb0Ao | |
To claim this, I am signing this object: |