Skip to content
Select theme
  • Auto
  • Dark
  • Light
Download

Commands

Type /oasis help in game to see the commands you’re allowed to use. Every command has Tab completion too, so if you forget a word, press Tab and Oasis shows you what fits.

Command What it does Permission
/lookup <filters> Search the history oasis.lookup
/rollback <filters> Undo changes oasis.rollback
/rs <filters> Put back what a rollback removed oasis.restore
/undo Reverse your last rollback or restore oasis.undo
/inspect Click blocks to see their history oasis.inspect
/oasis kept See the blocks your last rollback kept oasis.lookup
/oasis status See how Oasis is doing oasis.status
/oasis incidents See the storage problems Oasis recorded oasis.status
/oasis incidents clear Clear them from the list and the status; the cairn keeps them oasis.purge
/oasis cancel Stop the rollback that’s running oasis.cancel
/oasis purge <filters> Delete history for good oasis.purge
/oasis reload Read config.yml again oasis.reload
/oasis import Bring in CoreProtect history oasis.import
/oasis move Move history to or from Packs Server oasis.move
/oasis fawe patch Fix a FastAsyncWorldEdit bug oasis.fawe
/oasis fawe tune Make FAWE’s memory setting safer oasis.fawe
/cairn share Send the cairn to the Oasis team oasis.cairn

Two permissions have no command of their own. oasis.alerts lets someone see storage problems in chat, and oasis.* gives every permission at once. They all start out as operator only.

A pack is one permission that gives a whole group of them.

Pack Usually given to What it gives
oasis.admin Trusted staff Lookup, inspect, rollback, restore, undo, status and cancel
oasis.owner Server owners and the people who run the server Everything in oasis.admin, plus reload, purge, import, move, the FAWE commands, /cairn share and alerts

Players who aren’t staff usually have oasis.inspect at most. It shows who changed a block, but it can’t change anything.

The everyday commands have short forms: /lo, /rb and /ins. The restore is only /rs, because FastAsyncWorldEdit has a /restore command of its own. Every command also works under /oasis (or /oa), so /oa rb user Griefer last 2h does the same as /rollback user Griefer last 2h, and /oa restore does the same as /rs. That helps if another plugin already uses /rollback or /undo.

Lookup, rollback, restore and purge all understand the same filter words. Each word takes a value after it, and you can put them in any order.

Filter What it matches
user Steve Whose changes. Also takes a natural cause: #explosion, #fire, #water or #hopper.
last 2h How far back to look, in m, h, d or w. day means since midnight.
older 30d Only changes older than this. Also takes mo and y.
near 50 Blocks around you
in world_nether Worlds, or sel for your WorldEdit selection. A lookup and a purge also take a world that is not loaded.
block *_sign A block, item or mob. A * matches any part of a name.
cause explosion A kind of change, named like the events in config.yml
kind containers blocks, containers or entities, which a rollback changes, or items, books, chat, commands or sessions, which are for lookups only
not user Alice Leaves out a user, an in world, a block, a cause or a kind. not user also leaves out what that player set going, like the fire they lit or the water they poured.
page 2 The next page of a lookup

A comma adds more values to user, in, block, cause and kind, after not too. The line matches any of them:

/rollback user Steve, Alex last 1d not cause worldedit, sign
/rollback user Steve in world, world_nether
/rollback near 30 not user Alice, Bob
/lookup user Steve not in world_nether

You can type a space after the comma or not: user Steve,Alex means the same. You can also repeat the word, and you can mix both forms. These three lines name the same players:

/rollback user Steve, Alex, Notch
/rollback user Steve user Alex user Notch
/rollback user Steve, Alex user Notch

Tab completion helps with the list. After you pick one value, the list of suggestions stops. Type a comma to see the suggestions for the same filter again, without the values you already named. Type a space to see the next filter words. A comma needs a value on each side, and last, older, near and page take one value only. in sel stands alone: a WorldEdit selection lies in one world, so it joins no other world. You can’t use not in sel, and Oasis refuses a line that keeps and leaves out the same player or world, like user Alice not user Alice, because it matches nothing.

Oasis doesn’t understand CoreProtect’s u:, t: and r: words or its #preview flags. If you type them out of habit, Oasis runs nothing and shows you the same command in Oasis words, for example 'u:Griefer' is CoreProtect syntax. Did you mean /rollback user Griefer last 2h near 20?

Pick a command, then add filter words and their values. The builder shows the command and what it would do. Copy it and paste it in game.

An interactive command builder. It starts empty. Pick /lookup, /rollback or /rs (restore), then add filter words such as user, last, near, block and cause, and pick a value for each. You can change or remove each part of the command, and a plain sentence says what the command does. Several values of one word, such as two players, join with a comma. For example, /rollback user Steve last 1d not cause worldedit rolls back everything Steve did in the last 24 hours, except WorldEdit changes.

Pick a command below

Pick a command to start.

Start with what you want to do

Build a real Oasis command one word at a time, then paste it in game.

With /inspect on, left-click a block to see its history, or right-click a face to see the empty space in front of it, like the spot where a broken block used to be. Clicking won’t break or place anything while it’s on. Anything a rollback already undid is crossed out, and hovering over a line shows what caused it.

A really big rollback asks you to confirm before it starts. Click the link in chat, or type /oa confirm.

A rollback or restore with no user filter asks too, because it takes every player’s changes in that area, not just the griefer’s. The prompt shows the narrower command, like /rollback user <name> near 50. After you confirm three of these, Oasis stops asking you for that reason. A really big one still asks.

Sometimes a rollback finds blocks that someone else has changed since the griefer was there. Oasis leaves those alone, so it doesn’t undo somebody’s repair, and tells you how many it kept. To roll those back as well, click the link or type /oa force. /oasis kept shows you which blocks they were.

With Packs Server, a rollback that covers a lot of chunks also offers Confirm with turbo. See Embedded or Packs Server?

Oasis runs one rollback or restore at a time, and /oasis cancel stops the one that’s running. /oasis purge takes the same filters as a rollback and always asks you to confirm, because what it deletes is gone for good.

A lookup and a purge read the history and never touch the world. So in takes any world that is loaded, that Oasis saw loaded, or that still holds edits in the history. The world needs no folder. Tab completion after in lists these worlds and marks the ones that are not loaded. A name that no world has shows No world named X and the worlds that Oasis knows.

A rollback and a restore write the world. If the world is not loaded, Oasis loads it from its folder for the rollback. If the folder is gone, Oasis refuses and says World X is not loaded, and Oasis cannot load it: its folder is gone. Use /lookup in <world> to read its history, and /oasis purge in <world> to delete it.

To delete every edit of a world, run /oasis purge in world_nether and confirm. A purge that names worlds and a time bound (older) and no other filter is a purge of whole worlds. It deletes the rollback edits of those worlds too, and the entries of those worlds in the operation log for each operation that finished before the cut, so the history of the world is gone. A cut inside an operation keeps the record and the undo of that operation. An operation that covered several worlds stays undoable in the other worlds.

Add user, near, block, cause, kind, last or not and the purge deletes only the edits that match. It then keeps the rollback edits, because they mark what a rollback reversed. The count in the confirmation leaves out the edits that it keeps.

When a purge leaves a world that is not loaded with no edit, Oasis forgets the world. A later lookup of it shows No world named X.

/oasis import coreprotect brings in your CoreProtect history, whether it’s stored in MySQL, SQLite, DuckDB or ClickHouse. Oasis reads CoreProtect’s own settings, so there’s nothing to set up. That file can hold the database password, so Oasis asks before it reads it, every time.

Then it shows you a preview. Click the link, or type /oasis import coreprotect confirm, to start. The import runs in the background while your server stays up, and it never changes the CoreProtect database. /oasis import status shows how far it’s got, and /oasis import cancel stops it. If it stops partway, run the preview and confirm again, and it carries on from where it stopped. CoreProtect can run beside Oasis: the import reads only the rows from before Oasis’s first logged edit, and the preview names that time. Once an import finishes, Oasis won’t import CoreProtect again. Import from CoreProtect walks you through it and explains what comes over.

The cairn is a log Oasis keeps of what it did, in plugins/Oasis/cairn: how each rollback went, and a few of the blocks it touched with the history of each. It helps us find what went wrong when you report a bug, without asking for your whole history.

If we ask for it in your GitHub issue, run /cairn share and post the ID Oasis gives you. Once we approve it, Oasis sends the cairn and gives you a link to post. Nothing is sent before that.

/oasis move moves your history between Packs Embedded and Packs Server. When it ends, Oasis renames the old store and deletes it 7 days later. A cancelled or failed move leaves the old store as it was. See Set up Packs Server.

/oasis fawe patch and /oasis fawe tune are about FastAsyncWorldEdit. See The FAWE patch and Lagging? Check FAWE first.

If Oasis ever stops logging, everyone on the server is told in chat, with no permission needed: when it happens, when they join, and every five minutes until it’s fixed.