Tips and tricks for the new procedure system

Published by Klemen on Sun, 05/06/2018 - 17:44
Tips and tricks for the new procedure system

There have been many questions on MCreator's website on how to use procedure system. We have decided to create a getting started guide for the new procedure system.

We have created a separate wiki page for this purpose. Old event related pages were marked as "legacy" on our wiki, but we will keep them on the website for the users of older MCreator versions.

Many users complained that they can not make things that were possible in event system before. This is not true, however. Just the way how to achieve the same effect is now different. Everything that was possible before is still possible, even with many more options and combinations. This new procedure system is very similar to the one found in Scratch editor. The block system framework we use is called Blockly and is developed by Google. It allows us to make a visual programming experience that was never possible before.

On the procedures wiki page, there are examples of procedures including the explanation of trigger and dependencies. Below, you can see an example of how to make a random possibility condition in the new procedure system.

Random possibility

In this example, we show how to create an if condition that triggers in 70% of the cases. In case it is triggered, the block at x, y, z (these coordinates depend on the trigger that provides actual coordinate values) is removed.

Random possibility of event in the procedure editor

Examples such as the one provided in the citation above and many others can be found on our wiki on the new page dedicated to procedures.

Procedure system wiki page

We will update this wiki page with more examples in the future. If you would like to see a specific example, comment on this post and we will select the best requests and add them to the wiki page. Right now, only some procedures that were most commonly asked are shown. These include examples of how to create conditions that could previously be made using the event condition text box.

Share this on:


personally, I wish there were premade things you could put that was exactly like the old one my brain can't even handle the tutorials of this.

We might implement simple template support in the future, this is a nice idea. Could you please open a support ticket with a feature request for this, so we won't forget about this idea and keep a track of it?

I want to make a timer so something happens after 10 seconds. I made a timer which increments to 200 (since every second is 20 ticks). I thought a while loop would work, but when i add the procedure to the block, it updates after like a second, no matter the size of the timer.

Do i use the "Update tick" property of the block? Does this check every tick or does it do something different? I'd like to know this.

There is much discussion about this on the forums. Right now you can not create delays with a fixed amount of time, but we plan to add a support for this in the future updates, but most likely not yet in 1.8.0.

So I like Mcreator and I use it for 2 years but I have such problem that I cant use GUI(Gui functions like CLEAR SLOT or PLACE ITEM IN GUI SLOT) dont work item dissapears but then returns. I use this programm for many years and I make a wish every update to remove this bug but it stays. Help please!

Submitted by Cyclip on Sat, 06/02/2018 - 17:03

Glad my idea came through

A very little and not very important suggestion :
Can you add a warning error when you are naming a variable x, y or z? Because if you make a variable called "x", "y" or "z" it causes recompilation fail (that's because there are already minecraft x, y, z variables; but I didn't know that they are considered variables as the local ones). Also making local variables be able to be renamed would be nice.
(Sorry for bad English)

Renaming variables is close to impossible due to the way procedure system is implemented. But a nice suggestion for the warning. I will implement this in the future update, so if you name the variable as one of the dependencies, you get warned. If you have time, you can open a ticket on a tracker so the request does not get forgotten :) Thanks!

Yesterday I couldn't login. After writing username and password and pressing the butt9n, it said something like "unexpected error, please try again" in a blank page.
It happened both on my computer an my mobile.
After a few time I tried again to login and it said instead that the host was not allowed to login and to contact the admin. I could still login in pylo website.
I even tried to make a new account (Raol) but same error.
Now fortunately it seems to work