Load supported plugins elements only

Published by Goldorion on Thu, 08/13/2020 - 17:23
Status
Resolved
Product/platform
Not applicable
Priority
Normal
Issue description

When you make a new generator type and you are adding procedure blocks and global triggers, often, a lot of procedure blocks and global triggers are not added in the same update, or can't be added. So, we need to let users know what can be used or not in a separate file, but it's not the best way for many reasons. The first one is that not all users will check this file, and we always need to check the file to see if what we want to use is supported. So I don't know if with the way you implemented Blockly in MCreator will allow this, but a good solution to fix this problem would be to define in a file the name of each procedure block, global triggers, AI tasks and advancement triggers file, so when we will load a workspace with the Fabric generator, for example, I won't have the procedure blocks of MCreator or of ClothCreators we didn't implement yet. I don't know if it can be possible because it requires to load procedure blocks, triggers and AI tasks when we open a workspace and not when MCreator loads (or you could hide them if they are not supported).

Issue comments

MCreator detects if the procedure block is not supported when it is placed in the procedure editor. If it is not supported, there will be warning or error shown in the editor, depending on the procedure block type.

For mod elements, they are marked gray on dropdowns and blocks/items are not listed in the selector.

If it is not supported, there will be warning or error shown in the editor, depending on the procedure block type.

Oh true, I've never seen the warning message.

For mod elements, they are marked gray on dropdowns

Which dropdowns are talking about?

 



Donate to MCreator

By donating to developers you can speed up development, as with more resources, we can dedicate more time to MCreator. It is a free project made by developers working on it in their free time.