World Names

[Staxed]

Ok...I'm driving myself crazy at the moment. I'm working on some permissions, but I don't now what I should be naming my folders in GroupManager because the world names that worldedit/worldguard see are different than what dynmap sees for some reason.

Right now I have this set in Dynmap, and it is working...so these are the world names that Dynmap is seeing as correct...

  - name: world
    title: "Overworld"
  - name: DIM-1_nether
    title: "Nether"
  - name: DIM1_the_end
    title: "The End"
  - name: DIM7_7
    title: "Twilight Forest"
  - name: DIM20_20
    title: "The Promised Land"

Now, when I try to do a simple command, say "/set time day world" it works. Also, "/set time day DIM-1" that works...so it works like that for world and nether...but, when I try to do the end, tf, pl...it gets weird

If I try "/set time day DIM1" it says invalid world. I've also tried DIM1_the_end, end, the_end, theend, DIM1_1...nothing seems to work. How do I figure out what worldguard/worldedit are seeing as my world names...so I can actually set permissions for them?

 

[pherce]

The worlds are probably unloaded, it seems only the main world and nether stay permanently loaded by default. Toss a chunk loader in their respective spawns and test again (or just warp there and try the command). If you use multiverse, issue '/mvlist' and you'll see if they're unloaded or not.

 

[Staxed]

The worlds are probably unloaded, it seems only the main world and nether stay permanently loaded by default. Toss a chunk loader in their respective spawns and test again (or just warp there and try the command). If you use multiverse, issue '/mvlist' and you'll see if they're unloaded or not.

(MV works for ftb/mc 1.5.2?)

I've tried this, and I can only TP (using /world) to DIM-1, DIM7, and world. DIM1 and DIM20 don't work...this is so strange. I was thinking maybe it's because no one has visited them, but that doesn't fit because DIM-1 has been visted, and DIM7 hadn't...

 

[pherce]

Yes, we run MV through mcpc+. While running MV, you'll see something in your server.log (after all plugins have loaded) 'dim20 has been unloaded' & 'dim7 has been unloaded'. You can't '/mvtp dim20', '/warp', '/home', or '/time' to those worlds, however, we fixed this by tossing a chunk loader on those worlds' spawn and everything works fine.

I've also seen users on these forums complaining that GriefPrevention cannot load MystCraft or MV worlds for protection because the plugin loads before the worlds do. I have no idea if the chunk loader trick fixes this because we only allow claims in the main world. MV is also notorious for appearing to rotate ic2 blocks, but it's just a visual glitch.

 

[Staxed]

I'll give the chunk loaders a try.

What version of MV do you use? I was going to use it, but see that it was never updated for 1.5.2 so wasn't sure if it would work.

 

[pherce]

2013-09-09 22:01:39 [INFO] Multiverse-Core version 2.5-b675

Edit: If you are unsure if a plugin will work, read www.bukkit.org and they'll tell you what breaks from 1.4.x to 1.5.x to 1.6.x. For example: http://forums.bukkit.org/threads/cr...-2-development-build-is-now-available.158669/

Lots of things for 1.6 will run fine on 1.5 and vice versa, unless noted in their update.

 

[pherce]

By the way Staxed, I just realized MCPC adds world loading options into the bukkit.yml. Enabling each world keeps it loaded and can probably unload MV.

 

[Staxed]

By the way Staxed, I just realized MCPC adds world loading options into the bukkit.yml. Enabling each world keeps it loaded and can probably unload MV.

I've already added admin anchors to the world, but I'll look into that as well! thanks.