General Overview:
Command Blocks - record commands inside a block. (Green blocks)
-/cmdblock [block] [cmd] [args] [#ofuses]
-/cmdblock show -shows which blocks are valid command blocks.
Implementation Idea:
Macro Blocks - record building by player, and can replay these actions.
-/macro record [filename] - records the actions the player does/build. It does not record commands that the player uses while building!
-/macro delete [filename] - deletes the specified macro file.
--Note: The file will be recording the x,y,z coordinates of where to replay the building.
-/macro stop - stops the recording to [filename]
-/macro save [type] - saves the macro as a specific type.
--[type]: air, water, lava
---Place a block to save a location that will trigger the {macro} building. The block should be somewhere near where you were recording since once the block is activated the replay will occur at the original location where you recorded.
----After you place a block Message: "The macro trigger location is now saved at [x, y, z]"
-----A moment later Message: "TIP: Do /macro stop to stop recording to [filename]."
-/macro show - shows where macros are placed. (Blue blocks)
Explanation:
*When a player walks in the macro block it will initiate "building that a player has done before" therefore somewhat creating an automatic building system. I would say macro blocks is almost similar to bots...or their recording formula is.
I got this idea from /mb [type] [message]
Macro is also a good name, since if you know that a "Macro Recorder" for Microsoft Windows, records actions that you do,...and later you can save it, and distribute it to people. When people open it up it will basically replay what you did.
