Spigot Spider Nest + 1.5

Excellent!

Feature requests:

• Per-world configuration, including blacklist/whitelist. Use case: We would like to expose SpiderNest only in ExtraHardMode worlds.
• Localization of all messages, including those sent to console/log and in-game, and plugin prefix (default: "[SpiderNest] "). Use cases: (1) languages other than English, (2) removal of formatting codes.

 

Nice! Thanks for the 1.2 update.

More feature requests:

• Naming consistency, plan A -- SpiderNest (preferred):
  • Download filename: SpiderNest-*.jar (current)
  • plugin.yml: SpiderNest
  • Directory name: plugins/SpiderNest/
  • Default prefix: SpiderNest (rather than SpiderNests)
• Naming consistency, plan B -- spiderNest:
  • Download filename: spiderNest-*.jar
  • plugin.yml: spiderNest
  • Directory name: plugins/spiderNest/
  • Default prefix: spiderNest (rather than SpiderNests)

• Implement spidernest reload command
  • so configurations can be easily tested
• Retain comments in config.yml when rewritten by plugin (why is rewriting necessary?)
• Change default_config.yml -> config.yml in JAR
• Use standard entity names in configuration:
  • SPIDER rather than normal_spider
  • CAVE_SPIDER
• Enable configuration difference between surface and underground. Use case: I would like to configuration only SPIDER on surface, but a combination underground.
• Consider adding status effects to entities, with small probabilities.
• Consider a debug mode that posts console messages when these relatively rare events fire, so we can monitor how our configuration is working in the game. Include datetime, world name, location, how many entities were produced.

 

SpiderNest 1.2

Bug:

Worlds are found in ./UNIVERSE/ per start-up command: java ... -jar spigot.jar ... --universe ./UNIVERSE

And the WARN messages should be tagged with the appropriate plugin prefix.

 

Thanks for all that, and the speed with which it was accomplished.

Correction:

• renamed 'default_config.yml' to 'config.yml'

 

SpiderNest 1.2.1

I still get the world-not-found WARN messages. Config contains:

Code (Text):

worlds:
- world_whitedog
- world_whitedog_nether
- world_whitedog_the_end
- world_yellowdog
- world_yellowdog_nether
- world_yellowdog_the_end
world_policy: whitelist

 

Of course. It is baked into the start script. The main worlds were not found on server start-up. They were found a few minutes later if I reload the plugin. The plugin appears to be enabling before these worlds were loaded (we have a LOT of worlds).

The nether and end worlds have not been built yet, so quite reasonably were not found.

Since this is a test server, I am waiting for Spigot 1.16 to rebuild the nether.

 

Exactly the case. You might want to add both Multiverse-Core and MultiWorld as soft dependencies. That's what we do on our world-specific plugins.