At this point, I've written (parts of) three mods that all use mostly the same method to maintain TileEntity state: a class that knows how to put an ID, the TE coordinates, and whatever the TE wants to read or write into a Packet250CustomPayload and how to read same packet back. It's definitely something that can be externalized to reduce code duplication.
This is not actually a LiquidUU issue as much as a narc0tiq issue, but I only have trackers for the repos, so I may as well leave it here.
At this point, I've written (parts of) three mods that all use mostly the same method to maintain TileEntity state: a class that knows how to put an ID, the TE coordinates, and whatever the TE wants to read or write into a Packet250CustomPayload and how to read same packet back. It's definitely something that can be externalized to reduce code duplication.
This is not actually a LiquidUU issue as much as a narc0tiq issue, but I only have trackers for the repos, so I may as well leave it here.