Closed riri404 closed 5 months ago
Creating the following TODO
I will change some of these mechanism as I go. I will probably need to handle situations such as one board getting destroyed
After using synchronized block + nonce + debounce logic( stolen from hardware debounce logic), the event no longer fire twice.
Some issues when extending the GoldenChessBoardEntity:
Attempted solutions:
Next steps:
For rendering, the trick is to not subclass the GoldenChessBoardEntity. We just subclass ChessBoardBlockEntity and do it the old way. We may want to introduce an interface on entities for type-management in the events, but that's a relatively benign thing to do. The blockEntityType argument is needed to have things tie together behind the scenes, I believe.
Now that the board is registered in 1.20, I've started the implementation of the quantum board. I am using events for the mechanism, instead of creating a recipe of two quantum boards and an enderpearl. So far, the event is set up, but I have to start the linking process. I brainstormed a little yesterday and will start probably later this week.