BlockState breaking the API
#4
There might be a few problems though. As I understand it a blockstate represents what we currently use two variables for (blocktype and blockmeta/nibbletype). Methods that currently require those two variables could have problems. We could add deprecated bindings for those to automatically convert the old blocktype/meta variables into a blockstate.

To be honest, while backwards compatibility is nice, this is such a huge architectural change which we need to move forward that I'm fine with a somewhat lacking compatibility layer like deprecated bindings which translate blocktype/meta on the fly.
Reply
Thanks given by:


Messages In This Thread
BlockState breaking the API - by 12xx12 - 03-11-2021, 09:32 PM
RE: BlockState breaking the API - by NiLSPACE - 03-11-2021, 09:43 PM
RE: BlockState breaking the API - by 12xx12 - 03-11-2021, 10:06 PM
RE: BlockState breaking the API - by NiLSPACE - 03-11-2021, 10:13 PM



Users browsing this thread: 1 Guest(s)