The GUI provides visual management of templates, instances, pools, and timers with intuitive menu navigation.

Versioning System: Templates support multiple versions, allowing you to maintain different snapshots of the same region. The "active" version is used by default for restores.

Audience Scopes:

• NEARBY - Notify players within configured radius
• WORLD - Notify all players in the world
• SERVER - Notify all online players
• NONE - Silent restore

Instance Types:

• Pooled - Auto-managed instances for mass cloning
• Manual - Individually created and managed instances

Instance Options:

• boot - Restore on server startup
• vacate - Restore when all players leave
• interval - Auto-restore interval in seconds

Mass Cloner: Automatically manages multiple copies (instances) of a template across configured worlds. Perfect for duels servers that need dozens or hundreds of identical arenas.

Using the Selection Wand:

• Right-click to set positions (alternates between pos1 and pos2)
• Left-click to view current selection info
• Supports cross-world selection detection

Schedule restores to happen after a countdown delay with automatic player notifications. This allows you to schedule restores for a future time and warn players before restoration occurs.

/rr restore in <template> <seconds> [version] [scope]

Features:

• Scheduled Restore - Delay restoration by specified seconds
• Configurable Announce Points - Notify players at specific intervals (default: 60, 30, 10, 5, 4, 3, 2, 1 seconds)
• Audience Scope Control - Choose who receives countdown notifications:
  • NEARBY - Players within configured radius
  • WORLD - All players in the world
  • SERVER - All online players
  • NONE - Silent countdown
• Plurality-Aware Messages - Automatic "second/seconds" grammar

Example - Schedule arena restore in 30 seconds:

/rr restore in my_arena 30 WORLD

Announces to all players: "Restoring region in 30 seconds..." counting down to "Restoring region in 1 second..."

Tip: Use this for scheduled maintenance, event endings, or to give players time to finish their current activity before the restore.

Set up automatic periodic restores for instances or templates.

/rr timer set instance <instanceId> <intervalSeconds> [scope]
/rr timer set template <templateName> <intervalSeconds> [scope]

Features:

• Instance-Based - Timer follows a specific region instance
• Template-Based - Creates a hidden instance at template's original location
• Persistent - Timers survive server restarts
• Configurable Scope - Per-timer audience notification settings

Use Cases:

• Event arenas that reset every 5 minutes
• Practice arenas that auto-reset every 60 seconds
• Lobby areas that refresh periodically

Cancellation:

/rr timer cancel id <instanceId>        # Cancel specific instance timer
/rr timer cancel template-all <name>    # Cancel all timers for a template

Automatically restore regions when the server starts.

Configuration:

mass-cloner {
    worlds=[
        {
            name="duels_world"
            pools=[
                {
                    template-name="classic_arena"
                    restore-on-boot=true
                }
            ]
        }
    ]
}

Instance-Level:

/rr instance create <template> <x> <z> [world] [version] true false [interval]

(5th parameter true enables boot restore)

Use Cases:

• Reset all arenas on server restart
• Ensure plots are clean after maintenance
• Restore event areas to known state

Automatically restore a region when all players leave it.

How It Works:

• Tracks player occupancy in real-time
• Monitors chunk movements, teleports, world changes, joins, and quits
• Triggers restore after all players have left + configurable delay

Configuration:

mass-cloner {
    worlds=[
        {
            name="duels_world"
            pools=[
                {
                    template-name="classic_arena"
                    restore-on-vacate=true
                }
            ]
        }
    ]
}

Instance-Level:

/rr instance create <template> <x> <z> [world] [version] [boot] true [interval]

(6th parameter true enables vacate restore)

Configuration Options:

mass-cloner {
    vacate-delay-seconds=5  # Delay after last player leaves before restoring
}

Use Cases:

• Duels/PvP arenas that auto-reset after matches
• Mini-game instances that clean up when finished
• Private arenas that refresh between uses

Prevent server overload with intelligent concurrent restore limiting.

Configuration:

restore {
    max-concurrent-restores=5  # Maximum simultaneous restores
}

Behavior:

• When limit is reached, new restores are skipped with configurable notification
• Prevents TPS drops from too many simultaneous chunk operations
• Restores automatically queue and execute when slots become available

Notification: Players receive a message explaining why the restore was skipped:

"Region restore skipped: maximum concurrent restores (5) reached"

Example 1: Duels Arena with Vacate

mass-cloner {
    vacate-delay-seconds=3  # 3 second delay after last player leaves
    worlds=[
        {
            name="duels"
            pools=[
                {
                    template-name="1v1_arena"
                    count=20
                    restore-on-vacate=true
                    restore-on-boot=false
                }
            ]
        }
    ]
}

Example 2: Event Arena with Repeating Timer

# Create instance at specific location
/rr instance create event_arena 100 100 events 0 false false

# Set 5-minute repeating timer with WORLD notifications
/rr timer set instance <instance-id> 300 WORLD

Example 3: Lobby with Boot + Timer

mass-cloner {
    worlds=[
        {
            name="lobby"
            pools=[
                {
                    template-name="main_lobby"
                    count=1
                    restore-on-boot=true
                    restore-interval-seconds=3600  # Restore every hour
                }
            ]
        }
    ]
}

Example 4: Silent Background Restore

# Restore with no notifications
/rr restore in silent_arena 10 NONE

mass-cloner {
    worlds=[
        {
            name="duels_world"
            pools=[
                {
                    template-name="classic_arena"
                    count=50
                    separation-chunks=10
                    restore-on-vacate=true
                }
            ]
        }
    ]
}