02:02:30 [INFO] Protected issued server command: /tc map
02:02:30 [SEVERE] java.lang.ArrayIndexOutOfBoundsException: 21
02:02:30 [SEVERE] at com.khorn.terraincontrol.bukkit.MapWriter.run(MapWriter.java:149)
02:02:30 [SEVERE] at org.bukkit.craftbukkit.v1_4_5.scheduler.CraftTask.run(CraftTask.java:53)

(need more data?)

I cannot reproduce this anymore. Has it fixed itself or am I just lucky? 😕

I can't confirm at this time that it's fixed for sure, but we just put the generator in both places like recommended and the issue hasn't bothered us since then.

Are you using a biome id > 127? I'm quite clueless what could be causing this.

I don't think so. It's your plugin generating the biomes - is there anyway I could be using a biome id > 127?

Only if you are using a custom biome in the CustomBiomes setting (WorldConfig).

No, it's all normal biomes.

Want me to try putting the access to Colors and BiomeBuffer in different lines?

I'm not sure why but it's working for me with the latest build. Did you fix anything? At first I thought it worked if I used it from the console with a world name (as opposed to within the world I wanted to map without any arguments, which is what I was using when I got the errors) but afterwards it worked that way too...

I switched from a deprecated Bukkit method to a new one, but as the deprecated one uses the new one internally, I think that this change didn't fix it.

But I'm glad that this has been solved 😃

Oh shit, I just got the error again. Apparently it happens to some worlds but not others...

If it's world-specific, could I see the WorldConfig.ini?

I can, but I don't think it would help, I just did some more testing and if I completely swap the settings for the problematic world with another one (previously shown to work) then the other world breaks and the formerly broken one starts functioning properly. I think the issue here is TerrainControl can't handle the server's DEFAULT world, and can't properly generate for it or generate maps for it, causing this error. Right?

Or maybe it's multiverse that can't handle the default world and doesn't properly set terraincontrol as the generator...

Ok, I'll TC as the generator on the default world, managed by Multiverse.

Reproduced. However, if you add TC to both bukkit.yml and Multiverse's worlds.yml, the problem is fixed. Very strange.

I'm also experiencing this issue. I only have one world using TerrainControl generator and that is "world". The map functionality worked just fine with bukkit setting, but I receive this same error with multiverse.

"/tc map world -s 500" is the command I typed for reference.

I've had issues with MVC and default worlds before, and their staff seemed to think it was expected behavior, so I believe you can put this down as MVC being stupid. I suggest you recommend to your users the bukkit.yml fix or just to not use the default world at all...

The exact same exception occurs if you try to use /tc map afer /mv regen on a world.

@Protected And is that one also fixed if you also add TC to the bukkit.yml?