Spigot 1.14.3 (Jenkins 2395) git-Spigot-d05d3c1-087a2cf (MC: 1.14.3) (Implementing API version 1.14.3-R0.1-SNAPSHOT)
ExtraHardMode 3.14.alpha-e859c88

Clean installation produced materials lists in config.yml like

        Blocks (Block@id,id2):
        - !!org.bukkit.Material 'COAL_ORE'
        - !!org.bukkit.Material 'IRON_ORE'
        - !!org.bukkit.Material 'GOLD_ORE'
        - !!org.bukkit.Material 'LAPIS_ORE'
        - !!org.bukkit.Material 'REDSTONE_ORE'
        - !!org.bukkit.Material 'EMERALD_ORE'
        - !!org.bukkit.Material 'DIAMOND_ORE'

This cannot be read on server restart. Removing the "!!org.bukkit.Material " preceding the material names makes the configuration readable.

Hmm, and it didn't do this before making the change that eliminated the "expected list" error?

I don't know. I think I build a clean configuration every release (since you don't provide a config.yml in the JAR), but I cannot be certain. I jumped directly from 009e5c7 to e859c88.

Is there a quickfix available for this issue?

Read back: Removing the "!!org.bukkit.Material " preceding the material names makes the configuration readable.

Hmm, note to self: Check where config is written to file, see if can exclude material_list (or convert to string list)

Is there a quickfix available for this issue?

Is there a quickfix available for this issue?

Read back: Removing the "!!org.bukkit.Material " preceding the material names makes the configuration readable.

I did that before i even read this page but i can still mine stone like i can in vanilla, no message whatsoever..

All I did (above) was make the configuration readable. I didn't not test further. Thanks for the info.

Do you have any tips/hints to solve this one?

Wait for RoboMWM to confirm the issue, then make a fix?

The "inhibit stone mining" feature is disabled right now as I need to find a way to also pass in the values for how much damage a tool should incur for mining stone since the whole material@data value syntax is no longer valid as part of the refactor.

The "inhibit stone mining" feature is disabled right now as I need to find a way to also pass in the values for how much damage a tool should incur for mining stone since the whole material@data value syntax is no longer valid as part of the refactor.

How long do you think this process will take?

Well, there you have it. :)
Tips/hints: revert to 1.13.2 in production, which works very well. Reminder: 1.14.x is not production quality. YMMV.

Well, there you have it. :)
Tips/hints: revert to 1.13.2 in production, which works very well. Reminder: 1.14.x is not production quality. YMMV.

Still playing on 1.13.2 but im so excited to play this mod in 1.14.x

Not to hijack this issue than it's already becoming but that should be the only thing not functioning. If nothing else is then those are other issues you should file bug reports for.

Btw, you can file a bug report for that disabled feature anyways so I can update discussion on that. I was thinking of removing it temporarily since Idk demand for it (poll results are still a very small sample, only 20 or so responses).

Another vote: Please restore stone mining. It's an important EHM feature.

Stone mining inhibitors will be restored, it's the damage to tools that idk about, at the moment.

Right. Understood.

Since I'm too lazy to make another issue and it was already brought up here... @robinwezep

Restored the inhibit tunneling feature in af17eb6

Please test: https://ci.appveyor.com/project/RoboMWM39862/extrahardmode/builds/26454564/artifacts

If this feature is not working please make a new issue for it. Thank you!