CRAFTBOOK-3342 - Reported by DoreK

The bugis related to the CraftBook plugin
I can create mechanisms based on objects that should not work at all because they are not in configuration. This makes it very easy to obtain, for example, a stone.
http://i.imgur.com/ukAeXEi.mp4

Comment by me4502

The mechanic just gets told stone. So there isn’t a way to differentiate someone actually wanting to use Stone.

What do you currently have listed as materials that can be used by the gate? The solution is to remove the one that doesn’t exist.

Comment by DoreK

My config.yml and mechanisms.yml files:
https://pastebin.com/N5v5MAT8
https://pastebin.com/fxGmvzfE

Comment by me4502

You have 'NETHER_BRICK_FENCE' in your gate blocks. There is no block called that, but there is a NETHER_FENCE block.

Comment by DoreK

Thanks! :D

Comment by me4502

If you give the game a block that doesn’t exist, it defaults to stone. Something in your config isn’t a real block so the game sees it as stone.

Comment by DoreK

In this case, the mechanism should not be created if the objects that are set in the "mechanisms.yml" file are not detected. How to fix it?
@me4502