* Added advancements crafting data for block breaker and placer
(From 7a31de7b869e67697f85aeca9f0a5099c6bc7d62)
Added Block Breaker Machine (#2871)
* Added a new machine that can break blocks in front of it
(From e56a51da2b0c4e144cdf70ebff53d7097e81b5ce)
Added Block Placer Machine
* Added a new machine that can place blocks in front of it
(From e80de2ec82e0a14f161137e4b147bb455a839e3d)
Added Block Breaker and Placer recipe
(From dccdf76eacb8ceb7075897170e098bc346b8b4db)
Break blocks instead of removing + Refactoring
* 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.
* fix naming in ModelSantaHat.java
* Fix grammar, spelling, and javadocs in RebornCore
* Fix spelling error in datagen
* fix missed variable name
* fix grammar, spelling, and javadoc errors
* fix grammar and spelling errors in project files
* specify indent_size in .editorconfig
Raw metals thought the ingot storage block variant was their variant. THIS AFFECTS STORAGE RECIPES! Effectively means 9 raw variants can be combined to one ingot storage block, so maybe quickly new beta?
* Half of 2 new blocks, other half is a lot of data/model files
* Rest of the data/asset changes for new storage blocks.
* Bugfixes
* made hot tungstensteel storage block opaque
Unified power/time for a couple of similar processings.
All storage blocks of items that could be grinded should be able to be grinded now, with some time save compared to the items themselves.
* Added dust crafting data gen.
Generation works, but how do I get TR to recognize the existence of the new stuff?
* Added generic armor and tools to the datagen. Also resolved conflicts from the merge with recently changed datagen
* Fixed copy-paste error
by accident for second ingredient first would be taken again
* automatized tag generation
* fixed lingering bugs from previous commit
* much much more gen, for about 269 files
* wrongly deleted recipes in last commit
* Added rest of the decorative storage block variants to datagen
Steel's durability is about between iron and diamond, it is almost as tough as diamond, half as tough as netherite, but has same knockback resistance as netherite (which diamond lacks completely). But because we mixed some dirty coal to our iron to make it this tough and resistant, the enchantability is down to 5, which is by far the worst enchantability of all vanilla and TR armors.
Not tested yet, but I basically did the same changes as in the silver armor commit line by line.
Silver is 2 times as durable as gold (still less than iron), -5 of gold's enchantability (still more than diamond and netherite) and cannot pacify/distract piglins. Also, it looks very fancy.
* Initial Energy API refactor
* Allow charging in energy storage BEs
* Remove maven for experimental fabric
Co-authored-by: modmuss50 <modmuss50@gmail.com>