[Enhancement] Configurable Boost Blocks

[BlipRanger]

How difficult do you think it would be to add configurable boost block types / percentages?
I'd be willing to write the change if you'd point me in the write direction.
I don't have much (any lol) Kotlin experience, but I assume it would be something like:

• Parse list of "block string"/"boost percent double" pairs from config
• Convert the list to map of Material to Double
• Create a more generic function similar to your *Boost functions which calculates Int = (maxBoost() * blockToPercentMap([block.type]).toInt())

Just thinking out loud. Let me know what you think and thanks for your hard work!

[AtriusX]

Hello @BlipRanger!

Thank you for your interest in the project! I've been planning to add copper block support for a while but I was planning to wait until 1.18 to implement it. Considering that you've taken a bit of interest in this though I'm willing to let you attempt a PR for it.

At present, the acceptable block list is effectively hard-coded into the system. To make something like this work, there would need to be a fairly large adjustment to how the system approaches this going forward. To start, the block detection system would need to be updated to map for a list of blocks instead of a select set, and other systems that test against that block set would also need to be updated.

How the config represents those blocks in memory is also important. We have a parser system in place for reading and writing strings into the appropriate data and back. Depending on the way the setting is formatted will determine if another parser is needed to add support for this. The config command may need updated as well in order to aid ease of use (though this would likely be tedious on its own, and not a necessity).

Just off the top of my head, I could imagine a basic format along the lines of:

power-blocks: [
	["DIAMOND_BLOCK", 0.5],
	["GOLD_BLOCK", 0.33],
	["IRON_BLOCK", 0.2],
	...
]

However this may not be the most optimal way of handling it.