World Sets

World Sets Guide

SpectatorPlusPlus includes advanced world set detection and management to help you organize and navigate between related worlds (Overworld, Nether, End dimensions). This feature automatically groups worlds for easier navigation in spectator mode.

---

🎯 What Are World Sets?

World sets are groups of related worlds that share a thematic or dimensional connection. For example:

• Overworld: world, survival_world, creative_world
• Nether: world_nether, survival_nether, creative_nether
• End: world_the_end, survival_end, creative_end

SpectatorPlusPlus can automatically detect these relationships and organize them for intuitive navigation.

---

⚙️ Configuration

World Sets Settings

world-sets:
  auto-detect: true
  suffix-nethers: "_nether"
  suffix-ends: "_the_end"
  ignore-worlds:
    - "spectator_lobby"
    - "lobby"
    - "hub"
    - "minigame_arena"
    - "event_world"

Settings Explained:

auto-detect: true

• Enabled: Automatically detects and groups related worlds
• Disabled: Manual world grouping required

suffix-nethers: "_nether"

• Pattern to identify Nether worlds
• Matches worlds ending with _nether
• Examples: world_nether, survival_nether, creative_nether

suffix-ends: "_the_end"

• Pattern to identify End worlds
• Matches worlds ending with _the_end
• Examples: world_the_end, survival_the_end, creative_the_end

ignore-worlds

• Worlds excluded from auto-detection
• Typically includes non-gameplay worlds
• Common additions:
  • Lobby/hub worlds
  • Spectator areas
  • Minigame arenas
  • Event worlds

🔍 Auto-Detection Logic

How It Works

1. Base World Identification: Worlds without Nether/End suffixes are considered base worlds
2. Nether Matching: Finds worlds with matching base name + _nether suffix
3. End Matching: Finds worlds with matching base name + _the_end suffix
4. Group Creation: Creates sets of 1-3 related worlds

Example Detection

Base World: "survival"
Detected Nether: "survival_nether"
Detected End: "survival_the_end"
Result: World Set "survival" with 3 dimensions

🗺️ World Set Examples Standard Setup

# Single world set
world-sets:
  - name: "Main World"
    worlds:
      - "world"
      - "world_nether"
      - "world_the_end"

Multiple World Sets

# Multiple world sets for different gamemodes
world-sets:
  - name: "Survival"
    worlds:
      - "survival"
      - "survival_nether"
      - "survival_the_end"
  
  - name: "Creative"
    worlds:
      - "creative"
      - "creative_nether"
      - "creative_the_end"
  
  - name: "Resource World"
    worlds:
      - "resource"
      # No nether/end versions

Complex Server Setup

# Server with multiple game modes and special worlds
world-sets:
  auto-detect: true
  suffix-nethers: "_nether"
  suffix-ends: "_the_end"
  ignore-worlds:
    - "hub"                    # Main lobby
    - "spectator_lobby"        # Spectator area
    - "pvp_arena"             # PvP minigame
    - "parkour_course"        # Parkour world
    - "event_2024"            # Temporary event
    - "admin_build"           # Staff build world

🎮 Player Experience

Navigation Benefits

1. Compass GUI Organization: Worlds grouped by set in compass interface
2. Quick Dimension Switching: Easily move between Overworld/Nether/End
3. Logical Grouping: Related worlds appear together
4. Reduced Clutter: Non-gameplay worlds hidden from navigation

In-Game Behavior

• World sets appear as expandable categories in compass GUI
• Click category to see all worlds in that set
• Direct teleportation between dimensions of same set
• Visual indicators showing world relationships

⚙️ Manual Configuration Disabling Auto-Detect

world-sets:
  auto-detect: false
  custom-sets:
    survival:
      - "survival_world"
      - "survival_nether"
      - "survival_end_dimension"
    
    creative:
      - "creative_overworld"
      - "creative_hell"
      - "creative_ender"

Custom Suffix Patterns

# Alternative naming conventions
world-sets:
  auto-detect: true
  suffix-nethers: "-nether"      # world-nether
  suffix-ends: "-end"           # world-end
  ignore-worlds: []

Mixed Auto & Manual

# Auto-detect most, manually specify others
world-sets:
  auto-detect: true
  suffix-nethers: "_nether"
  suffix-ends: "_the_end"
  custom-sets:
    special_event:
      - "event_main"
      - "event_nether_realm"
      - "event_end_zone"
    
    tutorial:
      - "tutorial_world"
      # Only one world in this set

🔧 Troubleshooting

Problem: Worlds Not Grouping

Checklist:

1. Verify auto-detect: true
2. Check suffix patterns match your world names
3. Ensure worlds aren't in ignore-worlds list
4. Confirm world names follow pattern: base_suffix

Problem: Wrong World Groupings

Solutions:

1. Adjust suffix patterns to be more specific
2. Add problematic worlds to ignore-worlds
3. Use manual configuration instead

Problem: Missing Dimensions

Causes:

1. World doesn't exist or isn't loaded
2. Suffix doesn't match exactly
3. World name contains extra characters

Problem: Performance Issues

Optimizations:

1. Add non-essential worlds to ignore-worlds
2. Reduce number of auto-detected sets
3. Use manual configuration for large servers

🎯 Best Practices Naming Conventions

✅ Recommended:
- survival_world
- survival_nether
- survival_the_end

✅ Also works:
- creative
- creative_nether
- creative_end

❌ Avoid:
- world1, world2, world3 (no clear relationships)
- nether_survival (suffix at beginning)
- survival-nether-world (multiple underscores/hyphens)

Server Organization

1. Consistent Naming: Use same patterns across all worlds
2. Minimal Ignore List: Only exclude truly non-gameplay worlds
3. Regular Review: Update configuration when adding/removing worlds
4. Player Feedback: Adjust based on player navigation patterns

Performance Tips

1. Limit Active Worlds: Keep only necessary worlds loaded
2. Group Similar Worlds: Players navigate related worlds together
3. Cache Results: World detection runs at server start
4. Monitor Impact: Check console for detection time on large servers

🔄 Advanced Features World Set Metadata

world-sets:
  auto-detect: true
  set-metadata:
    survival:
      display-name: "&aSurvival World"
      icon: "GRASS_BLOCK"
      required-permission: "world.survival"
    
    creative:
      display-name: "&bCreative Builds"
      icon: "DIAMOND_BLOCK"
      required-permission: "world.creative"

Dimension-Specific Settings

# Different spectator settings per dimension
world-sets:
  nether-settings:
    can-fly: true
    fly-speed: 0.15
    invisible-to-others: true
  
  end-settings:
    can-fly: true
    fly-speed: 0.2
    can-see-other-spectators: false

Integration with Other Plugins

• Multiverse-Core: Respects MV world properties
• WorldGuard: Region-based spectator restrictions
• PermissionsEx: World-specific permissions
• Essentials: /world command compatibility

📊 Example Server Configurations Small Survival Server

world-sets:
  auto-detect: true
  suffix-nethers: "_nether"
  suffix-ends: "_the_end"
  ignore-worlds:
    - "lobby"
    - "spectator_hub"

Large Network Server

world-sets:
  auto-detect: false
  custom-sets:
    survival_1:
      - "survival1"
      - "survival1_nether"
      - "survival1_end"
    
    survival_2:
      - "survival2"
      - "survival2_nether"
      - "survival2_end"
    
    creative:
      - "creative_build"
      # No additional dimensions
    
    minigames:
      - "bedwars"
      - "skywars"
      - "parkour"

Modded Server

world-sets:
  auto-detect: true
  suffix-nethers: "_nether"
  suffix-ends: "_end"
  suffix-other: "_twilight"  # Custom dimension
  ignore-worlds:
    - "minecraft:overworld"
    - "minecraft:the_nether"
    - "minecraft:the_end"
    - "twilightforest:twilight_forest"

❓ Frequently Asked Questions

Q: Can I disable world sets entirely?

A: Yes, set auto-detect: false and don't define any custom sets.

Q: How do I handle worlds without Nether/End versions?

A: They'll appear as standalone worlds in the compass GUI.

Q: Can players bypass world set grouping?

A: No, grouping is for navigation only. Players can still access individual worlds.

Q: Does this affect world permissions?

A: No, world sets are purely for organization. Permissions still apply per-world.

Q: How are newly created worlds handled?

A: They'll be detected on next server restart or config reload.

🚀 Pro Tips

1. Start Simple: Use auto-detect for standard setups
2. Test Thoroughly: Check all world groupings before going live
3. Player Labels: Consider how world sets appear to players
4. Regular Updates: Review config when adding/removing worlds
5. Backup Config: Always backup before making changes

For additional configuration options, see the main Configuration Guide.