Usage

• //undo undo the latest worldedit command
• //redo redo what was just undone
• //show_journal view what can be undone and redone
• With the more_chatcommands mod, other player's changes can be undone with /run_as <playername> //undo, where <playername> is the other player's name.

Undoing reverts changes of nodes (name, param1 and param2) and metadata. Node timers are not yet supported. The undo functionality should help against accidents; however, it should not be considered reliable since there is no guarantee that undoing always is possible or works correctly.

The changes of nodes after invoking a command such as /set are compressed to improve memory usage.

Related issues:

• Uberi/Minetest-WorldEdit#43
• https://forum.minetest.net/viewtopic.php?p=296543#p296543

Implemented and missing Worldedit commands

Supported chatcommands

• /pos1 and /1
• /pos2 and /2
• /p
• /set and /s
• /mix
• /replace and /r
• /replaceinverse and /ri
• /orient
• /flip
• /cube and /hollowcube
• /sphere and /spr
• /hollowsphere and /hspr
• /dome and /do
• /hollowdome and /hdo
• /cylinder and /cyl
• /hollowcylinder and /hcyl
• /pyramid and /pyr
• /hollowpyramid and /hpyr
• /spiral
• /load
• /mtschemplace
• /luatransform (nodes and metadata changes inside the selected area)
• /y
• /n

Ignored chatcommands

• /lua
• /clearobjects
• /fixlight
• /save
• /mtschemcreate
• /mtschemprob
• /hide
• /suppress
• /highlight
• /restore
• /inspect /i
• /mark /mk
• /unmark /umk
• /volume and /v
• /about

Not yet implemented

• /fixedpos /fp
• /reset /rst
• /shift
• /expand
• /contract
• /outset
• /inset
• /copy
• /move
• /stack
• /stack2
• /drain
• /allocate
• /deleteblocks

Partly implemented

• /transpose (the marker position change is not saved)
• /rotate (the marker position change is not saved)
• /stretch (the marker position change is not saved)

TODO

• Allow undoing changes which happened before other changes (considered unsafe) e.g. //undo ~1 to undo the change before the latest one
• Add code for more of the WorldEdit chat commands (see the lists above)
• Add a verbose option to the //show_journal output to show detailed information such as the UTC time when the changes happened and the required memory to store them