Bukkit

@Baba43

Sorry, not planned.

@GokouZWAR

The amount it waits for is 500 MB, so I can see that would be a problem in your case. I can hardly imagine trying to run a Minecraft server with only 512 MB memory in the first place.
I could allow the memory limits to be changed for the Fill process, but doing so would make it very likely that you'd end up with an OutOfMemory crash if you set the limits to be more permissive like you want.

I have an unfortunate announcement: since I've just closed down my own Minecraft server for various reasons (mostly boiling down to me not having enough time to devote to it), most of my motivation for working on Bukkit plugins is now gone. I most likely will not be actively developing any plugins I'm involved in from this point on. However, I still plan to maintain all plugins as needed for new Bukkit releases and minor bugfixes and such, I just probably won't be adding any major new features or answering much in the way of support questions.

The source will remain available for all plugins, and I'd welcome anyone to take up active development. For Factions, Cayorion / Olof (the original author and still constant contributor for the plugin) will of course remain to develop the plugin and will continue to run the Massivecraft server.

If anyone really wants a particular feature added to one of the plugins I've worked on, I will still consider doing sponsored feature requests; no promises, of course.

Also, for Factions, I plan to try to make sure the 1.7 branch is ready before halting active development on it. There will also be at least one more 1.6.x release before then, probably quite soon. So, this announcement is a bit in advance of me ceasing active development on Factions.

Sorry, guys. Again, I will at least try to bugfix and maintain my plugins for Bukkit updates, but that's about it.

@ccman972

I know of no reason unless something else killed the border checking task or you're running a custom server implementation (maybe Tekkit or similar) that isn't handling server-synchronized thread execution properly or something like that.
A couple of others have reported a similar problem, though I've had no luck in figuring out what other plugin or custom server or whatever might be causing it.

Is the problem consistent? If so, please use /wb debug on and then have someone cross the border and check the server console/log to see what if anything is output. If nothing is output, that in itself would be useful to know as it would indicate the border checking task is indeed not running on your server.
Either way, please post your CraftBukkit build or custom server you're using, and the list of plugins you run on your server.

For reference, someone else having that problem intermittently:
http://dev.bukkit.org/server-mods/worldborder/?comment=205

@cal_97g

It might be when it's generating strongholds and/or abandoned mines or something like that. I don't know for sure since I haven't looked into how the Minecraft world generation code actually works or what the bottlenecks and memory hogs would be.

@piousminion

You can pause/unpause the fill process whenever you want, like it tells you when you run the command. I don't really have time to add in any automatic system to try to detect when your system is busy or whatever.

@cal_97g

Yes, it is. Generating new world chunks requires a substantial amount of memory. Blame Notch if anything since it's his world generation code; he seems to make a good target for blame, anyway.

@JoneKone

What do you mean? People lingering near the edge of a round border shouldn't be stressing your system. The methods and algorithms used are quite efficient.
As I've mentioned before a few times, back when I did some efficiency testing to compare WorldBorder and BorderGuard (finding WorldBorder to be more efficient, of course), I found that a round border took only slightly more time to handle than a square one. This included testing where I moved around near the edge (mainly tested using a player in a minecart on a track with boosters to move them around, but also tested in other situations like constantly trying to cross the border and simply standing still near the center and near the edge). That's why I changed the default border shape to round instead of square, since there was only minimal overhead in processing time.

@Gravemind2401

That would require monitoring every block change event and checking to see whether each one is inside the border. That would add a fair bit of overhead and potentially contribute to lag. So, not planned, sorry.

@CosmicVoyager

That's a possibility which is still on the table, but it would potentially be confusing to players and CraftBukkit doesn't (or didn't?) handle such long-range teleports into unloaded chunks very well.

@thedazs

If there are no errors reported in your server log, it shouldn't be the fault of WorldBorder.

@hawkfalcon

The fill process uses Bukkit's built-in methods for loading and generating chunks. If there is a problem with the generated chunks, look to CraftBukkit or whatever custom server you're using (Tekkit/CraftBukkit/whatever).