Axionize
Axionize
@masmc05 I addressed all the changes you requested. Added comments starting where my patch modifies code, switched to using event.callEvent() and the patch now uses the FQDN instead of imports...
I've addressed all issues that have been brought up. Is there anything else I need to do for this to be merged?
I'll fix the notations but I don't understand your second concern, what exactly is the problem? That the message returned to the player won't reflect the new tick rate?
I've restructured this PR so that mutations will be reflected in messages and return values.
Hi, is there anything left for me to do before this can be merged?
This does not work and leads to an NPE at start when init() is called to try and use reflection to get the methods. I've gone ahead and fixed it...
How does Axion deal with letting themselves send illegal packets (on the Axion-Paper side)? I know they break the 32k limit on Paper do they just hook into paper and...
Would you consider letting us switch over the (non-abstract) entity types?
Understandably, I didn't want to have to do this but I get it. I'll make `Vector3XMutable` classes for each type
@booky10 I've made appropriate changes I think you would find acceptable. I've added a mutable variant and an interface they both share. Is this design acceptable to you?