Jump to content

Ami Marchant

  • Posts

  • Joined

  • Last visited


0 Neutral
  1. Using names when filtering wasn't much of a problem until Display Names came along. In fact there are now three names for each avatar: 1. Legacy Name (the traditional firstname lastname) 2. Display Name - that you can choose or change (great for greeters but not recommended for security scripts) 3. User Name (firstname.lastname format that so far isn't used for much of anything I've seen in-world) If you are going to use 'Name' as a means of filtering 1. read up on Legacy Names v. DIsplay Names http://wiki.secondlife.com/wiki/Display_Names/LSL 2. check the type of "Agent" sensor call.used http://wiki.secondlife.com/wiki/LlSensorRepeat All 1-name newer folks are actually "avName Resident" to the llSensor() function specifying simply AGENT. I belive this may be a contributing factor to your issue here.
  2. ... like has been noted, you could change the 'and' to an 'or' ( || instead of && ) another suggestion... instead of two tests in a single if(), like here: if( llListFindList(accessList, [avatar]) < 0 && llDetectedKey(num) != llGetOwner()) ... use a "suito" combined list for a single test like this: if( llListFindList(accessList + [owner], [avatar]) < 0 ) so long as: string owner is the equivalent of llKey2Name( llGetOwner() ) (assigned at rez or state_entry() with you in the region) (not for you, but for new scripters following along ...) Scipt flow is a learned and personal experience. I usually start by thinking how I would do it in person by hand. In the case here, having the sensor event work down from whom to ignore to whom to notice via nested if() conditions in order to efficiently deal with each agent detected. #1. agents already noticed this period (hour, day, week, etc) #2. anyone on a Pass or Ignore list #3 - agents not geopraphically eligible. i.e. not on my land or a targeted parcel or bounding box then finally #4 - doing whatever for agents detected this event who are "none of the above". if you will be filtering agents within the sensor() event - useful llDetected*() functions are at your disposal like: llDetectedName(num_detected) in lieu of llKey2Name() llDetectedPos(num_detected) (were they walking along the parcel boundary or in my house?) GL
  3. ... also, somthing to consider for a "security" script, including a test for llOverMyLand() as to not affect agents not on/over your property. http://wiki.secondlife.com/wiki/LlOverMyLand If you are developing a script to market, use of llOverMayLand() can can be tricky, but for a personal script for use with a personally owned parcel your neighbors will appreciate it.
  4. We see questions such as this from time to time and my primary advice is to spend some time in the realm. I mean immersion kind of time. Rent some land, build or buy a house.Make or buy some furniture. Explore, a lot. 'Live" in this virtual environment for a while and you may end up reframing your question to be more along the lines of "What could the corporeal world learn from a virtual world like Second Life?" As has been noted, SL is already governed by its Terms of Service and Community Standards.The OP's follow up post about IP infringement is indeed an area of concern in SL just as it is in our physical world. The main difference being that in Second Life, ALL things endure with the permission of the almighty Asset Server. Meaning that even though 'copying' occurs and some is never detected, the blatent cases can litterally be wiped from the face of the virtural world. (Enough from me on that for now, back to my original message.) In Second Life, the residents (with a few excepts) do pretty well governing themselves considering the WIDE diversity of inhabitants. Age, race, gender, religion, physical limitations are practically meaningless here. Education, in the terms of ability to communicate, and social grace play a much greater role in Residents' experience in a virtual world. Taking into consideration each "player's" real-life socital background and the differences thereof of all the players from all around the physical world one may readily obsserve that at a basic level people are very adept at taking care of themselves and exist quite well in an environment which is focused on "Protecting Rights" rather than one driven by "Enforcing Limitiations." Spend some time here and you too may see how the "Real World" could learn a few things from a virtual one like Second Life.
  5. Hi Staralien, welcome to SL! From how you described that event I bet you were using the official SL viewer (2.8 or 3.0), and yup, I too don't care for the way IMs and notices are too easy not to notice with that browser. There are some really cool third party viewers for SL you might want to explore as well http://wiki.secondlife.com/wiki/Third_Party_Viewer_Directory Hats off to ya for jumping in and wanting to build right away, lots of resources for you for creating in SL from in-world tutorials to wiki's, forums, and YouTube videos galore. Happy Trails and maybe see you around the grid. :matte-motes-bashful-cute-2:
  6. You are your best insurance when entering into a lease/rental. 1. Don't pay in advance too far ahead (i.e. pay your tier/rent 1 week at a time) until your landlord has earned your trust like if there's a multi-week discount and even then don't pay ahead more than you could lose if the unthinkable or unexpected occures. 2. Get an idea of how long the landlord has been operating that property by viewing information in the "About Land" dialog box. On a private estate I look at the Covenant tab for the date the covy was last modified. 3. Look at the profile of the landlord... does it look like someone you want to do business with? Also see if they operate other properties, regions, estates, etc... If they do, look over their Tier Collection Center: Are there a high number of vacancies? Are other tenants comfortable paying ahead very far? Are the other tenants in arrears? If you get bad vibes about a place move along. 4. Google the landlord or company name. Not a guarantee, but with all the non-SL resident blogs and forums out there if someone has a history of poor business practices a vent or rant about them may surface. 5. Have an idea about what reasonable market rates are. If a rental deal looks too good to be true, it probably is and don't expect it to last forever.
  7. // Make an access list to check against. Also note subtle difference of using --nd vrs nd-- in the argument. // list of keys for access: list listAccess = [ "a2e76fcd-9360-4f6d-a924-000000000003", // guest Philip "0e346d8b-4433-4d66-a6b0-fd37083abc4c" // guest Kelly ]; default { state_entry() { listAccess += llGetOwner(); // Owner is auto added at reset. No need to screen for later. llSetStatus(STATUS_PHANTOM, FALSE); // Set the object solid. } // Triggered when objects (including avatars) collide with the object containing this script collision_start(integer nd) { while(nd) { // Cycle through the detected keys of those objects that collided this time checking if each is on the list. if(llListFindList(listAccess, [(string)llDetectedKey(--nd)]) >= 0 ) llSetStatus(STATUS_PHANTOM, TRUE); // Become un-solid } } collision_end(integer nd) { if(llGetStatus(STATUS_PHANTOM)) // If the object is un-solid llSetStatus(STATUS_PHANTOM, FALSE); // Set the object solid. } }
  • Create New...