Welcome!

Hello there, fellow Oasis Staff! This guide will help you get up and running with the Admin Editor, our powerful tool for creating server automations without writing code. Make sure to carefully read through this guide and refer back to it as needed. If you have any questions, don't hesitate to ask your department's lead.

Getting Started

The Admin Editor lets you change server behavior with a visual flow editor. A flow is one editable server feature, such as a command, event response, GUI menu, reward system, or permission check.

Core Ideas

Concept	What it means
Flow	One saved server feature made from nodes and connections.
Node	One configurable step, such as sending a message, checking permission, giving an item, or waiting.
Connection	A line that says what runs next.
Trigger	The node that starts the flow.
Placeholder	A dynamic value like %player.name% or %world.name% that is filled in when the flow runs.

Common Flow Starts

Trigger	Use it when
Command	A player or console runs a command, such as /spawn.
Event	Something happens in game, such as a player joining or breaking a block.
Function	You want a reusable section that another node or GUI click can call.
Button	A player clicks a text button in chat.

What You Can Change

Most flow edits are settings in the right-side Node Inspector:

• Trigger settings: command name, aliases, usage text, permissions, cooldowns, allowed sender type, or event type.
• Message settings: modern text, legacy text, titles, action bars, boss bars, webhooks, and clickable buttons.
• Target settings: triggering player, all players, a specific username, or players with a permission.
• Item settings: material, amount, custom name, lore, enchantments, NBT, GUI slots, armor, offhand, and hotbar slot.
• Flow settings: branches, delays, repeats, function calls, switches, tab completion, and try/catch handling.
• Data settings: variables, booleans, math, arrays, maps, text editing, and database collection actions.

Basic Workflow

1. Open the Dashboard.
2. Create a new flow or open an existing one.
3. Add nodes from the left Node Palette.
4. Connect output handles to input handles.
5. Select each node and adjust its settings in the right Node Inspector.
6. Click Validate to catch missing settings or broken paths.
7. Click Save.
8. Click Deploy to publish the change to the selected server.

Good Habits

• Give flows and functions clear names.
• Keep branches connected to a useful result, such as a message, action, or Stop Flow node.
• Use placeholders instead of hard-coded values when a value should change per player or event.
• Validate before deploying, especially after editing conditions, switches, GUIs, or command arguments.
• Export a flow before large changes if you want an easy backup.

Next Pages

• Dashboard: manage flows, icons, search, and user settings.
• Editor Overview: learn the editor layout.
• Flow Canvas: place, move, connect, and organize nodes.
• Node Inspector: understand field types and settings.