The plugin continues its journey here.
You can create, manage and delete lists in your procedures. You need to have a list of your favorite names for pigs, you can make it!
Features
You can have a small preview of blocks or things you can do in the following picture.
(Before 2.4.4)
Important Information
- This plugin supports Forge 1.19.4 and 1.20.1, NeoForge 1.20.4 and Fabric 1.20.1
- Icon by Tobi-Wan#0482
Changelog
To see a complete changelog of the plugin, check this file.
2.4.8
* Updated to support MCreator 2024.1 (only)
* Added support for NeoForge 1.20.4
* Removed support for Forge 1.18.2 and 1.19.2 and Fabric 1.19.2
Comments
I have a problem: I can't put custom items and blocks into an arraylist, but I can vanilla ones.
So basically I want to check if every block around my block is one of a couple specific blocks, so I created an arraylist, put all the blocks I wanted in it, and checked for them using a for loop.
Everything was working, until I tried to add a non-vanilla block to my arraylist, it gave me an error. It says that CUSTOM:blockname is not a statement.
I added a "is the same block as" statement, and checked what the code looks like if I put my custom block in that, and it was ModName.BLOCKNAME. The vanilla blocks were added to the arraylist in a similar fashion as "Blocks.BLOCKNAME".
Why does this happen? Can you fix it or is the problem with Mcreator?
You can with "filemanager" plugin from Goldorion, it has features to create files and json data, in fact i use that to create .json files. At trigger "when player leaves world" create file and save json data, and retrieves that file content at "when player enters world".
Is there a way to use this in conjunction to store different player UUIDs for different instances of the same block kind? Basically I want to make a block that spawns an item when right clicked for a player, then is locked out for that player on that block. Basically Player A clicks Block A, and can only do it once, but Player A can repeat the process with Block B no trouble and Player B can use Block A no problem. IDK if that example was at all intuitive but you seem to be one of the more knowledgeable users on the platform