* Cache Torus.generate result for Origin
Fusion Coils are laggy, not by ticking block entities, just purely by torus.generate(BlockPos.origin, size)
* Assign TorusListCache
* use cached result
* Resin Basin updated. Thanks to Spearkiller and Ayutac.
Hitbox has been updated to half a block, better matching the model.
Item model has been updated by Spearkiller to look nice.
There was a weird inconsistency about the amount of sap given to player depending on either putting it into an inventory or breaking the block.
Right click to harvest basin didn't work as intended, so removed for now.
Also it seems the block states (full/pouring/pouringTime) are not saved via nbt?
Also also wow the warnings.
* Added removal of sap from basin when right -clicking.
The error was me not understanding that "setFullState" had nothing to do with the variable "isFull". My bad, my bad.
For some reason one right click triggers the onUse twice, and previously I didn't correctly update the sap after the first one, but now it should work. Testing went off without a hitch.
* In-depth update of chrome->chromium, thanks to Ayutac, Xanthian
This fixes Bug #2621 without accidentally destroying items (untested, but the chrome item registration isn't changed) and supersedes PR #2780 which only made language changes.
I just plainly copied the lang changes from Xanthian. As for the chrome stuff, I thought long and hard how to do it properly. Possible variants:
1. Change tag names in constructor for chrome only.
2. Change tag names in enum for chrome only.
3. Don't change the internal tag names of the enums, but change the tag registration process in datagen for chrome only.
4. Introduce CHROMIUM variant, add conversion recipes etc. and hope over time CHROME can be safely removed.
(4) always had the potential of item loss, so I discarded it first. Deciding between (1), (2) and (3) was harder. The drawback of (2) is code bloating by adding a lot of extra enum constructors, especially for cases which already had enum constructor options. But in the end I decided to go with it because it was the cleanest solution to a dirty problem. This is the first time I encountered a datagen drawback, because if we didn't register by running through the enum array, we could have simply changed it there; a possible (5) but still worse than (2).
* Whoops, forgot recipe changes with the tags
* Merged chromium with hardness/resistance
Replaced the isHot argument from constructors with default false while I was at it.
Changes primary output to 2x raw iridium as other recipes that use mercury with this machine generally have a greater output than just with water.
Makes more sense to have the raw ore as the output from this machine instead of an ingot, which you would usually get from a furnace of some type.
* Fixes#2783 hopefully
Needs to be tested still. Goal: changed blasting to use half as much as time as regular furnace for same item.
* Fixed bug in commit thanks to ErrorSys
forgot that order of optional arguments is important and that int can be cast to float automatically
I increased the capacity of tanks to be even remotely considered an alternative to storage units with cells. I kept the values conservative since increasing is always an option, but decreasing might cause item loss.
Changes:
Basic Tank: 35 -> 128 (about 3.5 times)
Advanced Tank: 200 -> 512 (about 2.5 times)
Industrial Tank: 500 -> 1024 (about 2 times)
I oriented myself at the storage unit steps, which are quadrupled with each tier until advanced, then doubled to industrial.
While I was at it, I changed everything to powers of 2 with the shift operator (so other code readers aren't too confused about seemingly arbitrary values) and added explaining comments.
Just like in last commit, assembling machine one is a bit hacky (we add dummy classes), but better than putting an if into RebornRecipe and faster+safer than correcting the differences between assembly_machine and assembling_machine in the code.
Centrifuge one is a bit hacky (we add dummy classes), but better than putting an if into RebornRecipe and faster+safer than correcting the differences between centrifuge and industrial_centrifuge in the code.
