To export your commands and settings as a project, you can either:
Copy: One method of saving your project manually is to copy the text from above, and paste it into a safe place on your computer.
Download: The other method of manual saving is to download a text file containg the project. To do so, click the 'download' button below.
To import a saved project, you can either:
Paste: One method of importing your project manually is to paste the project text into the area above.
Upload: The other method of manual saving is to upload the '.txt' file containg the project. To do so, click the 'upload' button below.
Upon clicking "Save", your current commands, settings, and signs will be saved as a project on the server. You will be able to open this project under the "Projects" section.
Upon clicking "Rename", your current open project will be saved with the new name that you specified above. You will be still able to open this project under the "Projects" section.
Below is some of the simple things you you use to make you code more readable which will then be compressed
Due to the shear number it will take a while but if you want to help search the project on Github
Writing this would set the block to granite stone whilst allowing your code to be readble rather than numbers
All types shown above and it isnt case sensitive so what ever is best for you
It supports both its real ingame name and it real command name the underscore is optional again for best readability while not case sensitive
It works for all types defined above and in and circumstances you will this type of definition such as /execute, /fill, /setblock and /testforblock if you want to stick with the trend cobblestone is also supported if you use variant it will also be shrunk down to its number form making you code as minimal as possible
Below is a list of the built in functions. They can be used by entering them as a command in the command combiner below!
Writing this would cause the tellraw command to only run once, when the user first runs the compacted command.
The command above would be placed in a repeating command block, overriding whatever the command combiner would have originally made it by default.
The command above would be placed in an impulse command block, which you can then activate by using the TAG feature (explained below).
Both of the '/say' commands would be placed in repeating command blocks
Since '/summon' would be added before each command within the multi-line modifier, this would summon a zombie and a creeper
Using this command in the command combiner would cause a stone block to be placed under any armor_stand which is standing on the ground.
Using these 2 commands in the command combiner would cause the phrase "A player is in creative mode" to be printed to the chat only .lt least one player is in creative mode
The two commands above would have the exact same outcome as the previous example. This is simply a different way to write it, which is easier to see the logic when reviewing your commands.
If you wrote these commands in the command combiner, the "setblock" command would place a dirt block at the location of the "say Hello" command. This is useful when you need to access a certain command blocks coordinates from multiple other command blocks. (Especially useful for /stats)
If you used these commands in the command combiner, it would essentially do the exact same thing as the previous example, except this one is much quicker to type, but it can only be used to target the command prior to the one referencing it.
Using this in the command combiner would allow you to throw a grass block item and a stone block item together on the ground to create 1 diamond sword named "Magic Sword".
You can use as many ingredients and result items as you want, just make sure that ingredient items do not start with 'RES:', but result items do!
If you are already familiar with command blocks, you should already be a master at using the command combiner! Simply write some commands, each on a new line in the large text field below. They will all be placed on a 20hz fill clock in the final command. If there is a command that you only want to run once, just write INIT: before that command. This is mostly useful for adding scoreboard objectives and for /tellraw install messages.
If you were to write these 2 lines in the command combiner, it would give every player 1 stone upon install, then it would constantly spam the chat with "test", 20 times per second.
Comments are a very useful feature to help you organize your project. A line can be commented by placing a # before the line. The commented line will be ignored when the command is generated.
If you were to copy and paste those 2 lines into the command combiner, only the second one would appear in the final command. The commented line would be ignored.