Just downloaded the latest version. The protector wand is undefined...
In the logs...
Code: Select all
ERROR[Server]: Item "protector:stick" not defined
Code: Select all
ERROR[Server]: Item "protector:stick" not defined
Is protector_radius greater than 40?KzoneDD wrote:Hiya; any idea why the server crashes with ... init.lua:159:find_nodes_in_area(): area volume exceeds allowed value of 551368?
What was the crash message at 30?KzoneDD wrote:It was. Then tried 30, still crashes. Then tried 16... no crash so far.
TenPlus1 wrote:Notice:
- protector.drop feature has been disabled, can easily be exploited using lag.
OK, It's what I do in the first server I put inline. So, we try to prepare a spawn-zone to put it after with Worldedit.TenPlus1 wrote:Typically the server owner builds spawn first (with help) before using spawn protection...
OK, thanks fot those explanations.TenPlus1 wrote:The 'delprotect' priv was deprecated and replaced with 'protection_bypass' which does the same, and protector_drop mode was removed as players misused it to cheat in duplicate items on occasion.
Code: Select all
if minetest.is_protected(pos, hitter:get_player_name()) then
Code: Select all
if not minetest.is_protected(pos, hitter:get_player_name()) then
It would probably need to be an admin/mod only feature because a large area might need to add numerous forceloaders, find all protectors in that area and then remove the forceloaders. Iterating over the list of found protectors and adding players is easy at this point.Sokomine wrote:Add a command that takes a volume (i.e. as defined by WorldEdit), lists the positions of protectors that are either in this volume or at least active there, and that allows to add or remove a player from all your protectors that affect that volume.
This requires the same code as above but each protector cuts away at the volume in something like an octree, the report the uncut regions. A little bit more intensive than the first feature.Sokomine wrote:A command to check if all inside the marked volume is actually protected by the player.
You're right - even a smaller area might need forceloading. The volume the command is able to check could depend on weather it's a normal player (-> only check a small volume) or someone with an appropriate priv.auouymous wrote: It would probably need to be an admin/mod only feature because a large area might need to add numerous forceloaders, find all protectors in that area and then remove the forceloaders. Iterating over the list of found protectors and adding players is easy at this point.
Users browsing this forum: Google [Bot] and 18 guests