Skip to main content
Hubbly allows you to disable its features in specific worlds. This is useful for multi-world servers where you only want hub features active in certain worlds.

​
Configuration

The disabled worlds feature is configured in config.yml:
​
disabled-worlds
array
default:"[]"
List of world names where Hubbly features should be disabled.
disabled-worlds:
  - 'world_nether'
  - 'world_the_end'
  - 'survival'
​
invert
boolean
default:"false"
When set to true, inverts the behavior - Hubbly will only work in the listed worlds.
disabled-worlds:
  - 'hub'
  - 'lobby'
invert: true  # Features only work in hub and lobby

​
How It Works

When a world is in the disabled list:
  • Player visibility toggle
  • Movement items (trident, grappling hook, AOTE, enderbow)
  • Double jump
  • Launchpads
  • Force inventory
  • Custom experience bar
  • Boss bar
  • Join/leave messages (unless announcements.global is true)
  • Event cancellation (blocks, items, damage, etc.)
  • Chat filters
  • Commands (like /spawn, /fly)
  • Database connections
  • Anti-world-download (if configured globally)
  • Announcements (if announcements.global is true)

​
Usage Examples

​
Example 1: Standard Hub Setup

Disable Hubbly in survival and creative worlds: 
disabled-worlds:
  - 'world'
  - 'world_nether'
  - 'world_the_end'
  - 'creative'
  - 'survival'

invert: false
Result: Hubbly features only work in worlds NOT listed (e.g., your hub world).

​
Example 2: Multi-Hub Setup

Enable Hubbly only in specific hub worlds: 
disabled-worlds:
  - 'hub'
  - 'lobby'
  - 'hub_event'

invert: true
Result: Hubbly features ONLY work in hub, lobby, and hub_event worlds.

​
Example 3: Disable in Nether/End

Keep hub features in overworld but disable in nether/end: 
disabled-worlds:
  - 'world_nether'
  - 'world_the_end'

invert: false
Result: Hub features work everywhere except nether and end dimensions.

​
World Names

World names are case-sensitive and must match exactly as they appear in your server files.
To find your world names:
Run this command as an operator:
/hubbly debug
Then check the console for the current world name.

​
Invert Mode

The invert option changes how the list behaves:
Disabled-worlds list = BlacklistFeatures are disabled in listed worlds, enabled everywhere else.
disabled-worlds:
  - 'survival'
  - 'creative'
invert: false
Hub features work in: hub, lobby, minigames, etc.Hub features DON’T work in: survival, creative

​
Global Announcements

By default, features are disabled in listed worlds. However, announcements can be made global: 
announcements:
  enabled: true
  interval: 30
  global: true  # Announcements work even in disabled worlds
  messages:
    message1:
      - 'Welcome to the server!'
​
announcements.global
boolean
default:"true"
When true, announcements will be sent to players even if they’re in a disabled world.

​
Testing Configuration

1

Set debug mode

Enable debug logging in config.yml:
debug: true
2

Add test world

Add a world to the disabled list:
disabled-worlds:
  - 'world_nether'
3

Reload config

Reload the plugin:
/hubbly reload
4

Test in-game

  • Go to the disabled world
  • Try to use hub features (double jump, items, etc.)
  • Features should not work
  • Check console for debug messages
5

Verify other worlds

  • Go to a world NOT in the list
  • Hub features should work normally

​
Common Scenarios

​
Scenario 1: Dedicated Hub Server

You have a BungeeCord network with a dedicated hub server: 
disabled-worlds: []
invert: false
Why: All worlds on this server are hub worlds, so no need to disable anything.

​
Scenario 2: Shared Hub + Survival

Your server has both hub and survival worlds: 
disabled-worlds:
  - 'survival'
  - 'survival_nether'
  - 'survival_the_end'
invert: false
Why: Hub features should only work in the hub world, not survival.

​
Scenario 3: Multiple Hub Lobbies

You have multiple hub worlds but other game worlds: 
disabled-worlds:
  - 'hub_main'
  - 'hub_event'
  - 'lobby'
invert: true
Why: Using invert mode, you explicitly define which worlds are hub worlds.

​
Scenario 4: Event World

Temporarily enable hub features in an event world: 
disabled-worlds:
  - 'hub'
  - 'event_pvp'  # Add event world
invert: true
Why: Easy to add/remove worlds from the whitelist for special events.

​
Troubleshooting

Check:
  1. Is invert set to true with an empty list? 
    disabled-worlds: []
invert: true  # This disables features everywhere!
  2. Are you in the correct world?
  3. Do you have the required permissions?
  4. Is debug mode enabled to see console messages?
Check:
  1. World name spelling (case-sensitive)
  2. Reload the config with /hubbly reload
  3. Check if announcements.global is affecting behavior
  4. Some features (commands) still work in disabled worlds
Add all three dimensions:
disabled-worlds:
  - 'survival'          # Overworld
  - 'survival_nether'   # Nether
  - 'survival_the_end'  # The End
If you use invert: true with an empty list, Hubbly will be disabled in ALL worlds:
disabled-worlds: []
invert: true  # DON'T DO THIS unless intentional!

​
Best Practices

If you have more game worlds than hub worlds, use invert mode:
disabled-worlds:
  - 'hub'
invert: true
This is easier than listing every non-hub world.
If you have more hub worlds than game worlds, use normal mode:
disabled-worlds:
  - 'survival'
  - 'creative'
invert: false
Add comments to your config:
# Hub features only work in 'hub' and 'lobby' worlds
disabled-worlds:
  - 'hub'
  - 'lobby'
invert: true

Build docs developers (and LLMs) love

Get started for freeTalk to us