The Problem

A friend and I are working on a plugin where it creates a new world for each game played. Our plugin handles all features that WorldGuard would in these worlds, however not in the spawn world where it's needed.

We use SlimeWorldManager to manage these worlds and WorldGuard seems to have issues with intializing/reading the world configurations sometimes. ("Region data for WorldGuard failed to load for this world, so everything has been protected as a precaution.")

In addition, we use SlimeWorldManager to store these worlds in RAM only to minimize our I/O footprint, so when WorldGuard correctly initializes it still defeats the goal we're trying to reach.

A Solution

A config option to blacklist/whitelist worlds (preferably with regex) to let WorldGuard ignore these worlds and not generate individual configurations for them.

Alternatives

• Patch the issue appearing when using SlimeWorldManager - Neither WorldGuard or SlimeWorldManager log errors, in addition to the I/O footprint issue I mentioned above. (However this issue might want to be documented seperately in one of the plugins).

Anything Else?

The issue specified is irrelevent in this discussion, however was provided as reasoning for this feature.

The problem with SlimeWorldManager is that it’s broken and doesn’t inform plugins of anything that’s happening. WorldGuard doesn’t know what’s going on, which is why it has unexpected behaviour.

You can’t add an exclusion to something that WorldGuard can’t even know happened due to bugs in the world plugin

if the bukkit api ever supports the concept of deleting (not unloading) a world (with an event), it would be nice for regions etc to be deleted along with it. the issue with SWM not loading worlds properly is unrelated, they need to fix that on their end.