Description:
I really like this new approach for resources generation the mod has right now! A few gimmicks to iron out though.
User manual fails to inform the player of ALL the potential ways a data card can be become corrupted resulting in several people in our server losing their hard earned ores they wanted to put into the card for the miner to get started, as well as me losing a stack of ancient debris (spent 2 hours mining for those) by simply boosting the richness and storage modifiers using enriched nikolite dust and a ridiculous amount of stone which resulted in a corrupted data card, since I didn't know how this mechanic worked at all.
Manual only refers to data corruption if there are too many different types of ores encoded into the card but not on the modifiers.
Steps to Reproduce:
Use a stack of a single ore type to encode and then max out the richness and storage modifiers.
Once the data card reaches 100% it gets corrupted, losing everything you invested in it.
Ideas for consideration or potential improvements
A way to manage the cards and their contents in case something undesirable is added into to them. Like RCing the card pops an UI with everything the card has in it but it must be initially encoded from the encoder machine to be able to use it and keeping the machine still useful that way.
or
A way to recover at least the ores used into the cards while still losing all the modifiers used in them. The recycler or the encoder could add that function!
or
Block further additions into the card if it has reached its limits without it becoming unusable, prompting the players to make another one or make it again better using their resources more efficiently this time.
EDIT 16/2/2023
I also noticed that I can add eg. richness modifiers indefinitely without adding more bonus into the ore card which sounds like a big waste since it requires a kinda expensive to get catalyst for it.
Technical Information:
Minecraft: 1.19.2
Fabric API: 0.72.0
Industrial Revolution: 1.15.1-BETA
Modpack: All Of Fabric 6 - v1.3.0
Logs:
I'll provide them following a request since it's not a crash.
Details:
I'll provide them following a request since it's not a crash.
Description: I really like this new approach for resources generation the mod has right now! A few gimmicks to iron out though.
User manual fails to inform the player of ALL the potential ways a data card can be become corrupted resulting in several people in our server losing their hard earned ores they wanted to put into the card for the miner to get started, as well as me losing a stack of ancient debris (spent 2 hours mining for those) by simply boosting the richness and storage modifiers using enriched nikolite dust and a ridiculous amount of stone which resulted in a corrupted data card, since I didn't know how this mechanic worked at all. Manual only refers to data corruption if there are too many different types of ores encoded into the card but not on the modifiers.
Steps to Reproduce: Use a stack of a single ore type to encode and then max out the richness and storage modifiers. Once the data card reaches 100% it gets corrupted, losing everything you invested in it.
Ideas for consideration or potential improvements A way to manage the cards and their contents in case something undesirable is added into to them. Like RCing the card pops an UI with everything the card has in it but it must be initially encoded from the encoder machine to be able to use it and keeping the machine still useful that way. or A way to recover at least the ores used into the cards while still losing all the modifiers used in them. The recycler or the encoder could add that function! or Block further additions into the card if it has reached its limits without it becoming unusable, prompting the players to make another one or make it again better using their resources more efficiently this time.
EDIT 16/2/2023 I also noticed that I can add eg. richness modifiers indefinitely without adding more bonus into the ore card which sounds like a big waste since it requires a kinda expensive to get catalyst for it.
Technical Information:
Logs: I'll provide them following a request since it's not a crash.
Details: I'll provide them following a request since it's not a crash.