Land Visitor Prim Limits

Currently, you can toggle the ability for visitors to your land to be able to rez prims.

Suggestion:

Instead of a blunt on/off switch, change it to a numerical value. Also, have at least two categories, members of the land's tagged group and all other visitors. (For group owned land, the group members would be considered owners, and therefore would not be restricted.) With a value set to 50 for all visitors, no one player could use more than 50 of the land's prims. This would allow land owners to prevent random people from using up all the prims.

The auto-return system works well for transitory objects, but not for permanent ones.

Example: A mall.

Mall owner limits group members to 100 prims, and visitors to 32. The auto return for group members is disabled and the visitor delay is set to 1 hour.

This way, each shop in the mall is permitted 100 permanent prims of allocation (a limit that is use ALL THE TIME in Second Life for shops and rental homes, but has to be done manually and without good tools to do so) and the system itself does the policing of the limit. Visitors have leeway to rez a vehicle or such, but nothing permanent.

EDIT: More advanced functionality could add limits on a per-person basis, and script functions to set them.

I really like this idea Tiger, and would love to hear from others how they feel about it. I'm not sure whether we can easily implement such a feature, but we can certainly look at it when we revisit group land tools.

I'm going to copy this post to the feature suggestions forum for further discussion.

I think this is a good idea and fully endorse it.

More user controlls over land like this would be great.

Yeah, I agree with this idea. It would save a lot of time.

-Adam

This would be a very helpful feature, as would a number of related land settings that would also be nice to see. Of course, there are user interface and programming considerations, but I suspect this sort of flexibility would be worth the effort.

Other things that might be set per-visitor on land include whether or not scripts are allowed, or even something like memory or other resource limitations on visitors' scripts. For example, being able to set the processing priority of visitors' or tentants' scripts might help land owners deal with lag issues.

I think this is a great idea and fully endorse it.

I love controls, the more the better, especially for group and group owned land. I really hate having to let everyone build on the land just go group members can build on group owned land.

I would love to see this idea in the next version of Second Life, it would greatly enhance the ease of which people could create shops and apartments, in fact it would be a huge boost to many walks of life in SL.

I'd like to see a more thorough "Levels of trust" feature for land and personal permissions. No matter how flexible the defaults are made by the lindens, the residents will always find new ways that they WANT to manage their land privs, situations that the defaults do not cover.

As far as I can see, land privs are basically a dynamic database, but one with fairly simple privilege sets so far. I'd like to see a way that people can easily define new privilege sets, and drop them down onto individuals as easily as a calling card. I'd like the system to be dynamic, for example:

John Q Avatar comes to my land, and has no scripting or building permissions based on his status as a member of the general public.

He activates his title as a group member of Avatars Anonymous and suddenly has build, but not scripting permissions, and a 25-prim limit.

He activates his title as a Group Officer of Avatars in Repose and now has build, script and terraform permissions.

He acts in a manner that I don't approve of, and so I demote his permissions back down to No-build, no-script, and this will not change, no matter what title he is currently wearing.

I concur, these are great ideas, I'd love to see something like that.

if it's strictly for group owned land, it can incorporated into the vast overhauled group code when it's released. that'll have multiple levels of membership that can be assigned discreet land permission settings. the code will just need to include an "others" level that actually represent people not in the group at all. of course that would effectively replace the land settings feature in about land.

you know, there's another idea. the about land interface could have multiple land settings tabs for the group that owns the land, if any, other groups listed in a window, and everybody else. but that needs more thinking through. i'm typing off the top of my head.

this is not a totally foreign idea for the hosts. they thought to include a "none" group that has everybody in it so that we have a group to activate when we don't want a user-defined active group.