Bukkit

Example code for getting the Border data for a specific world:

import com.wimbli.WorldBorder.BorderData;
import com.wimbli.WorldBorder.Config;

//...

// example code with example world name
String worldName = "world";
BorderData border = Config.Border(worldName);
// if border isn't set for world, it returns null; need to check for that
if (border != null)
{
    // can use border.getX() and border.getZ() to get the center position,
    // border.getRadiusX() and border.getRadiusZ() to get the radius values,
    // border.insideBorder(...) for checking if a location is inside the border,
    // along with everything else that's available through BorderData
}

@mrchasez

Yeah, as always seems to be the case in such crashes, the fault is not with WorldBorder. Based on the stack trace, it looks most likely to me to be a bug in Spigot's world generation code (quite possibly passed on from the vanilla Minecraft server code, as is often the case), but TerrainControl is also indicated in there as a possible cultprit as well.

@andrewkm

The root command is still /wborder, so you can use that. /wb is actually added as an alias since it's more likely to conflict with another plugin.

@Max633

Doesn't look like it, no.

@Daunay

Wrong version of WorldBorder, then. In the file list for this project, look to the "Game version" column for the list of Bukkit/CraftBukkit versions officially supported by each version of WorldBorder:
http://dev.bukkit.org/bukkit-plugins/worldborder/files/

As you can see there, WorldBorder 1.7.2b is what you'd want for version 1.5.2 of Bukkit.

@Daunay

Are you using a version of WorldBorder compatible with the version of Bukkit you're running? Post your full server startup log with the CraftBukkit version/offshoot and WorldBorder version listed.

WorldBorder 1.8.3 is now available as a quick fix with the /worldborder command alias now removed from the plugin, so that the newer vanilla /worldborder command isn't overridden. That leaves /wb and /wborder pointing to this plugin.

@Sonickyle27

Hmm, good point, I see I hadn't removed that command alias from the plugin. Quick fix if you're able to open and modify the contents of JAR files (I use 7-Zip) is to open worldborder.jar and edit the plugin.yml file. Find this line:

    aliases: [worldborder, wb]

and change it to:

    aliases: [wb]

I'll see about releasing a quick update for that later today. Though, there probably is some command alias available to run the vanilla /worldborder command as well.

@Karoom123

I'm not sure how you're getting a "red screen" from anything, especially not from this plugin. Maybe that's something from being outside the vanilla worldborder rather than this plugin? You'd need to be a lot more specific about what's happening.

@Relicum

The main thing I'd be interested in would be manipulating the new visible vanilla border walls to conform to custom shapes (rectangle, round/elliptic even if with jaggy block-following edges); I doubt that's really feasible, but I don't currently have time to look into it.

Separating out the Fill and Trim is one thing I'd considered, though more likely for Sponge as a bit of a rewrite would be needed there anyway.

@zizitt

Fill generates any chunks inside the border which don't exist yet or aren't fully generated (from loading adjacent chunks, to create snow and strongholds and various final details). If all chunks inside the border are already fully generated, the process naturally finishes very quickly.

If you want to generate the map in Dynmap, that's something to do within Dynmap.