Blocks per player

[Shane Cassell]

Hey,

I cant seem to find anything about this but how would I got about limiting a certain amount of blocks per player, so I want to make it so each player can only place 1 quarry and 2 spot loaders, so is there a plugin that does this, because I seen this in tekkit servers before, limiting the amount of energy condersors and so on. I am needing a bukkit plugin for unleashed 1.5.2, so not sure if its a plugin or config.

Thanks in advance.

 

[KnightOwl]

We tried to find something like this a week or two ago without luck..

 

[Connor Gavitt]

This may not be possible as that would require a large database and a plugin/mod to constantly check that every second to check if a player has placed too many of certain blocks. However it seems to me you want to limit chunk loading so your in luck in the chickenchunks config you can set the max amount of chunks a player can load and the max a op can load. And even the max amount of chunks a loader can load.

 

[KnightOwl]

Plugins like Prism already do something similar without causing massive amounts of lag. It is technically possible.. but would require some clever work to keep it from affecting performance.

 

[Connor Gavitt]

Plugins like Prism already do something similar without causing massive amounts of lag. It is technically possible.. but would require some clever work to keep it from affecting performance.

Prism records events (the database is still large mine is almost 30GB in size after 3 months) and when you do a large search it can cause extreme lag or even crash the server depending on what you are doing and checking every second or every time a player places a block will be extremely intensive to the point of 99% of servers not able to handle that. Unless there is another way of checking the events I don't think it can be done.

 

[KnightOwl]

You only care about specific X/Y/Z coordinates.. and really you only care when someone is placing a block.. For non-mobile blocks it could potentially be as simple as..

When someone places a block that we care about check the locations you have recorded for the last blocks they placed of that type. Count how many are still where they should be and use that # to compare against.

For things like Turtles it would get more tricky obviously but most servers either ban those outright or limit them to a specific world.

 

[Connor Gavitt]

You only care about specific X/Y/Z coordinates.. and really you only care when someone is placing a block.. For non-mobile blocks it could potentially be as simple as..

When someone places a block that we care about check the locations you have recorded for the last blocks they placed of that type. Count how many are still where they should be and use that # to compare against.

For things like Turtles it would get more tricky obviously but most servers either ban those outright or limit them to a specific world.

Still your method would have to check the block every placement of a block to see it's id then check the list of banned id's count and then it can allow/deny a placement. Also I don't see why you would ban turtles.... Out of thousands of people I have yet to see one grief with it.