WORLDGUARD-3334 - Reported by Telbaru

If you set fire on a burnable block (wood or something like this) it turns off in multiverse-worlds (it takes a few seconds to turn off, as you can see on the screenshotnames). The mainworld works perfectly with all worldguard-configs but in other worlds it turns off. It looks like that the fire spreeding out, worldguard blocks this and removed the fire completely. this happend to netherrocks too if there is a burnable block near by. but if the netherrack stands alone its all correct.
Using plugins:
Multiverse-Core v2.5-b688
Multiverse Portal
Worldedit 6.0
WorldGuard v6.0.0-beta-05.1569
system: Spigot-b1e6da1-1092acb.

Is it a problem with the worldconfigs for each multiverseworld or maybe a problem directly with mutiverse? If it is a problem with multiverse, why it takes the other worldguard flags and configpoints and only this doesen't works?

Comment by wizjany

Can't reproduce with a clean install of WE 6, WG 6beta5 and MV 2.5-b692. Another thing just came to me...check your spigot world settings?

Comment by sk89q

Are there regions nearby?

Comment by Telbaru

no there are only global flags build: deny, pvp: deny, mob-spawning: deny, snow-fall: Deny, snow-melt Deny, ice-form: deny and ice-melt: deny.

Comment by wizjany

If it's working in your main world but not others, there is probably something either in your worldguard config/regions or in multiverse's. Check for differences between the worlds. Also check for things like difficulty, which is how minecraft controls fire spread levels.

Comment by Telbaru

i cleared the worldconfigs and copy the main configs for each world, all worlds are difficulty normal and they have the same flags and only the multiverse-world are delete the fire in the same way. So the configuration isn't the problem. Have you testet it by yourself? can you reproduce the problem?