- Name
- Description
- Owner
- Group
- Area
There are also various other tools for finding parcel or region information, and while the above are all helpful, there is more information readily available that could be provided through LSL, as well as other ways it could be used to retrieve various data.
I've read that all parcels have a local (region-specific) integer ID as well as a global UUID. I'd like to see the following things created:
- integer llGetParcelID(vector position) should return the local ID of a parcel at position.
- key llGetParcelUUID(vector position) should return the global UUID of a parcel at position.
- integer llParcelForSale(vector position) should return true if the parcel is marked for sale. Maybe more integer tags could be added to list whether it's to anyone, or to a specific person.
- integer llParcelSalePrice(vector position) should return how much the parcel is set for sale.
- Any or all of the above should probably rather be added to llGetParcelDetails.
- key llRequestParcelInfo(key parcel, integer info) should return a request ID and trigger a dataserver event. The info argument should specify which specific parcel detail you're interested in. Valid possibilities should include all of the types returned by llGetParcelDetails as well as the local ID, sale price if for sale, and whether it's set for sale to a specific person. It should, at the very least, verify whether a parcel exists. EDIT: Looking back on this, the function should probably have a string region argument as well, since I imagine that would take a large load off searching for the parcel key in the database. Also, regardless of how this uses the database, it should have a pretty strong cap per owner and/or per region for the scripts using it, as it would almost certainly be reamed otherwise.
Any further ideas, clarifications, or otherwise are welcomed.
