@SmoothNanners

Yes, all regions that get scanned get a region post. But those which don't have any resources (deserts, fields, oceans) will be passed over, so that no new players are spawned there.

3.1 Updates!

• Totally eliminated notification messages about players teleporting from region to region. Because there are usually MANY ways to travel on servers including the obvious walking, this doesn't really add a lot of value because it doesn't give you an accurate idea of who's in the area. Also, it was surprisingly complicated code, and undermined some other plugins like SimplyVanish and VanishNoPacket.

• Posts will no longer "stack" in snowy biomes.

@Suprem20

It should be that you run out of world border only very rarely, after being online for a long time with lots of players. For those rare cases, a quick manual world border adjustment shouldn't be a big deal. Sorry, I just don't want to code for something that I believe happens very infrequently, I hope you understand. :) I'd probably spend more time coding, testing, and maintaining that new code than admins would ever collectively spend making the manual adjustments.

Also you may not be aware of this, but PD "spirals" out from the center, which minimizes world expansion. It doesn't just pick a direction and take off at high speed. So as long as you have circular or square borders centered as 0x0, PD will very efficiently use all of that space before trying to go out of your borders.

@bigscary

I want to stop players from venturing out thousands of blocks too far, some could go to -464545, 67, 5951. It could be problematic... Maybe talking about compatibility would be better? Perhaps WorldBorder compatibility, for example, stop players from going out too far but if the plugin cannot create more regions, extend the world border? Would be a very nice feature to be honest.

@Devil0s

Yes, you can use it with multiverse. That's actually why there are two different config settings for managed world and city world.

@Suprem20

If PD makes your world very big, that's because your world isn't big enough for the number of players you've had in it. Setting a max # of regions will guarantee that eventually, new players will not have the space and resources they need to get started, which would undermine the most important feature of the plugin.

I'm leaving leaves on purpose, because otherwise trees get sheared in half sometimes. :) Rarely, a post might need a small manual adjustment. Nothing I do programmatically will guarantee that a post is never, ever in a bad spot.

@Feaelin

Any area-claiming plugin could potentially cause this problem. I don't think there's any avoiding it - no matter how big you make the no-claim area, there will always be a border that players could abuse with enough patience. The server you and I play on has this problem on some occassions, but despite having 40+ unique players on every day for many months, I've only had to delete a claim around a region post twice.

@Kaesnoww

You probably haven't set the managed world in your config. That's the only required setup step. Check your logs during boot, you'll probably see an error message to that effect.

I've seen a situation a couple of times now where someone has built a "box" around the region post preventing access from/to it. If there's a property owning system (Grief Prevention, Residence, etc.) in use and the builder claims the wall, the wall can't be demolished by a normal player.

I'm not sure I like players doing that. Seems overly obstructionistic. Unfortunately, I also don't see an automatic way of preventing it except:

If GriefPrevention, Residence, etc. were 'PopulationDensity aware' and denied claims that encompassed the Region Post's protected zone. This wouldn't fully prevent it--but it'd mean that the builder would have to make several claims to achieve the effect--and at least, with GP, this would require a more significant investment of claim blocks due to the 10x10 minimum there. Probably this is a good candidate for a secondary plugin(s): PopulationDensity-GriefPrevention, PopulationDensity-Residence, etc.

@bigscary

If you are too far from a region and try to teleport home, you will get these messages:

1. "You're not close enough to the spawn to teleport home."
2. "You're not close enough to the region post to teleport."
3. "On the surface, look for a glowing yellow post on a stone platform."

This spams a bit an is pretty annoying. I think it's related to my configuration disabling the teleportation from anywhere combined to the small teleportation radius.

One last thing, when creating a glowstone post, I would recommend adding air to the platform, otherwise, it will be invaded by leaves.

Little screen to show what happens exactly:

Also, could you add a region limitation? I don't want my world to be 50 000 x 50 000 block big...

Is it possible to use it on different worlds? Multiverse compatible??

3.0 Updates!

• The "new region spam" is gone. There will be no new region announcements at all, since players don't really need to know, anyway. You'll still see all the details about new regions and all resource scans in the logs and console.

• Added a config option to stop regrowing grass. Basically anytime an animal spawns naturally, some tall grass spawns around it to ensure there's grass seed available for new players. If you don't want this, now you have a way to turn it off.

• Performance enhancement to release memory earlier (thanks Stylez!).

@Feaelin

Good catch, fixed the comment. No, that's the only player command which has an optional permission node. Other administrative commands require various permissions (usually populationdensity.addregion), while some player commands get a boost from admin permissions, like for example using /visitregion from any location.

<<reply 714158="">>

"Config option to require permission griefprevention.newestregion for the /newestregion command."

Shouldn't that be populationdensity.newestregion? tests...yeppers. :)

Do any of the other player commands have permission nodes?

@SkyderEfterLyde

I originally had features like this, but it was extremely awkward, because players didn't understand where they could build and where they couldn't, and this created lots of conflict with other plugins.

May I recommend GriefPrevention in addition to PopulationDensity? It's what I run on my server. Two plugins for my two biggest challenges.

2.9 Updates!

• Config option to NOT build region posts. Spawn areas are still protected, but no post will be built. This does not remove posts already built.

• Config option to require permission populationdensity.newestregion for the /newestregion command. I added a config option for this because when the permission is required, the slash command will not be advertised on new region posts. Also, you can restrict access to that slash command without installing a permissions plugin.

• Performance improvement. 100% eliminated ALL player movement tracking.

@Feaelin

Glad it's working for you. I've noticed that rarely, a new-to-server player will fall out of the world the very first time he joins the server, but never again after that. I haven't been able to pin down the reason for that, but it's mostly harmless.