Aozora Tech Blog

    News, updates and other stuff.

    Hiya all!

    What have I been up to, you ask? – I’ve been up to a lot, but a big project I’ve been working on is ‘AoRep’. AoRep is an Avatar Reputation System. It allows you to rate a persons reputation based on your opinion. If you don’t like someone because they’re rude and inconsiderate, you can give their reputation a thumbs down. If someone is very nice and considerate, you can give their reputation a thumbs up. If 50 people rate that persons reputation, someone else who doesn’t know that person and who uses AoRep can get a good idea of that persons reputation. – This is very useful if you want to find out how much the SL community likes a person before buying something from them or dealing with them. With AoRep, you can also rate a persons appearance, just like the old ratings system that SL used to have in the profile window.

    AoRep also allows you to set basic profile information that SL Profiles lack: Gender, sexuality, relationship status, avatar age and avatar type. The gender, sexuality and relationship status are indicated by their appropriate symbols on the AoRep’s scanner display for convenience.

    When will AoRep be ready? Soon! Currently it’s in an internal BETA phase and it should be ready for a public beta either this weekend or sometime next week.

    AoRep will be available in two flavors.

    AoRep Free: Allows you to view ratings, set your profile details and view other profiles. This version will not cost you anything.

    AoRep Premium: ( Otherwise just known as AoRep, ‘Premium’ usually isn’t included in the name ) Allows you to do everything AoRep Free can + the ability to rate people, change your HUD theme and have access to other future premium features. AoRep Premium will of course not be free.

     

    Q & A

    Q: Can I rate people who do not own AoRep?

    A: Yes. Anyone can be rated by AoRep, they simply need to exist in Second Life.

     

    Q: Can I opt-out of AoRep so people can’t rate me?

    A: Currently, no. There is no opt-out feature. – I will research anti-abuse systems once AoRep becomes public.

     

    Q: What about privacy! What information is stored, what information do other people have access to?

    A: No private information is stored. UUID’s, names are stored, but these are not private information. The name of the region you’re in is stored in an irreversible SHA1 hash. The ‘region name hashes’ are used to determine who’s in the same sim for the use of providing ‘scanner’ information to AoRep HUD’s and for deploying notification messages to users in only one region. – The only information that is accessible to AoRep users is the information that you apply to your profile. When you rate someone, users in the same sim or just the target if the target is not in the sim same but is online, will only receive a notification that the targets rating has changed. No one will know who placed the rating. It is completely anonymous.

     

    Q: How much will it cost for AoRep Premium?

    A: I have not decided on a price yet, but it will be around the L$500 range. There won’t be any subscription fees. ( Though that may be a payment option in the future if you don’t want to pay ~L$500 )

     

    Q: What if I have a lot of enemies that give me an over all bad rating?

    A: Currently there is no solution to this. But I will research anti-abuse systems once AoRep becomes public. – However, a good preventive measure you can take now is to not make so many enemies. :P

     

    Q: Can I use AoRep to prevent people with low reputations from entering my land?

    A: Not right now, but when it is possible, this will be a separate product. ( Note: I understand this may cause problems like other ban systems have in the past. I will take every step I can to ensure the system will be as fair as possible )

     

    Q: How efficient is the HUD?

    A: 54 prims, 3 scripts, 192KB of script memory and it idles with and average of 0.012ms of script time. ( Note: These specs may change before the official release )

     

    Q: What could I use AoRep for?

    A: AoRep can be used to spot griefers, as a factor in deciding if you want to deal with someone you don’t know well, to find out basic information about someone ( Gender, sexuality, etc. ) and it can even be used as a basic radar. It does show on the scanner display how far away the avatar is.

     

    Q: What’s the detection range for the scanner?

    A: There is no official range, but if you’re not using a TPV that supports the client radar and are the only user of an AoNS equipped device ( Such as AoRep or Phenom ), the range is 96m. – However, the more AoNS device users there are in the sim, the longer the range is. If at least one of those users is using a TPV that supports the client radar or has a built-in sim scanner, then the range is unlimited. AoNS devices share their scanner data with other AoNS devices.

     

    Q: Does it make toast and bacon?

    A: Perhaps…

     

    AoRep BETA is now for sale!

    AoRep Full Version

     

    AoRep Free Version

    Hiya all!

    The AoVend V2 upgrade has been released! This upgrade provides new features, improvements and much greater scalability and flexibility.

    This upgrade adds several improvements and new features such as…

    • Lower Prim options, lower script resource usage and better performance.
    • New redelivery options. Customers receive a URL to a page that lists all of their purchased products through AoVend and gives them the option to redeliver any of them.
    • Sales logs will be available to resellers in the near future.
    • Support for freebies
    If you were an active reseller when the upgrade was released, you should of received it already. If you were not an active reseller, you will have to purchase the upgrade here.
    New features will be released for AoVend V2 such as the above mentioned reseller sales log. Other features I have in mind are reseller rewards based on a ‘points’ system and more online tools for customers.
    WARNING: AoVend V1 vendors will no longer function as of July 31st, 2011. Make sure you upgrade or take down you AoVend V1′s ASAP.

    Hiya all!

    The AoVendors were first released just last year, June 28th and since then they’ve proved to be viable replacements for the aging Apez vendors. However, there are issues with the AoVendors and they do have a lot of room for improvement. I’ve kept these in mind and have been waiting for the technology available to me to improve until I attempt to tackle the issues.

    Recently I’ve started on the next generation of AoVendors. These will be built from the ground up and will have several improvements over the old versions.

    • Much more flexible: The new vendors can easily be customized, resized and new designs can be made.
    • Faster responses: No more pretty effects and instead a much more stream-lined and simplistic interface.
    • 1 Script and 1 Prim for most vendors: Instead of having an overly fancy interface, the main AoVendors will take on a simplistic interface which only needs 1 prim and 1 script.

    AoVend V2 will also be much more flexible feature wise. I have a few features I will experiment with in the future.

    • Reseller Control Panel: Would allow resellers to access sales information and redelivery products to their customers.
    • Reseller Directory: Would show a list of active resellers and provide SLURL’s directly to the AoVendors.
    • Promotional Coupons: Would provide customers with special discounts. Coupons would of course be distributable by resellers.
    • AoVend Public: Would be a feature in the far future that would open up AoVend for other people to sell their products through.

    AoVend V2 is currently in production and will likely be available by the end of this month. It will of course be a free upgrade for existing AoVend owners.

    Hiya all!

    The AoNS Database has grown to nearly 4.8 million records so far ( 99.9% of those are imported from existing databases, of course ) and is still growing. However, with the latest update the size of the database doesn’t matter! AoNS will now query the Second Life website for a name if it doesn’t exist in the database. This will dramatically lower the chance of not being able to target someone who’s not in the sim. This is especially useful for when dealing with new accounts. – The only drawback is that the avatar will need to have “Show my profile in search” enabled. However, that’s only if they aren’t already in the database.

     

    More on AoNS >>

     

    PS: The Phenom Evo V3.0.94 update implements the AoNS API’s. If you’re a Phenom owner, you should give the Name Searching feature a try! ( Do this by attempting to target someone not in the sim by using chat commands. IE: /9000 `intel ariu )

    Hiya all!

    Recently, I’ve been learning PHP (  Web/server code ) and PostgreSQL ( Database software ). Learning these technologies will allow me to take better advantage of the massive scalability and flexibility of  a web server and bring the power to my creations in Second Life. The first PHP + PostgreSQL project I’ve started is one I’ve had on my mind for a long time, a Name2Key service. It’s the perfect project for a PHP+SQL newb like myself, it’s simple and easy to maintain.

    The main reason I want my own Name2Key service is not for practice, but because there is one feature I really want that no other Name2Key database seems to have. That feature is partial name correction. Currently the Phenom features partial name correction, but it’s powered by LSL and due to the limitations of LSL, it isn’t very effective.  - With AoNS, partial name correction is much better. It produces much more relevant results and can easily be implemented into other products such as the AoVendors.

    The key features AoNS are…

    • Partial Name Correction and Recommendations
    • Display Name Searching ( Currently not used )
    • ‘Last Active’ which shows the time the avatar was last detected as online or by a probe
    • ‘Fast Intel’ displays various information stored by AoNS. ( Name, Display Name, Birth date, Last Active and owned Aozora Tech Products ). Much more convenient and faster compared to manually requesting each data type.
    • ‘AoNS Shared Scan’ Allows sim scanner results from AoNS Probes with other scripts in the same region. This will be very beneficial for scripts that are too small scale to host their own sim scanners. Also beneficial for those who do not use TPV’s ( Such as Phoenix ) with sim scanning abilities. ( See the bottom of the post for privacy information )

     

    AoNS will first be featured in the Phenom and will make its way into AoVendors and future products. For the time being, the AoNS API will be private. I plan on releasing the API later on, once I can ensure it’s safe and bug free.

     

    AoNS Shared Scan Privacy Information:

    AoNS Shared Scan requires region information to be stored in the database in order to sort out what keys to be sent to the requesting scripts. The information is stored in an SHA1 Hash format, which means it cannot be decoded to find out what region someone is in. This ‘Region Hash’ is compared to the ‘Region Hash’ of a script requesting AoNS Shared Scan data and if it matches, that key is added to the list that is sent to the script. This means scripts that use AoNS Shared Scan can only receive a list of keys of people who are in the same region, just like a normal sim scanner. – The ‘region hashes’ are not accessible and are only effective for a limited amount of time.

    Summary: It is impossible to use AoNS Shared Scan to stalk/track people. Not even myself, who has full access to the database can tell where you’re at without being in the same exact region.

    Hiya all!

    About 4 months ago, I upgraded from my semi-dedicated host at A2hosting to a fully dedicated X2 server at Hetzner online. The server was fairly low end. An AMD Athlon 64 3700+ ( 2.2ghz ) and 2GB DDR Memory, but it suited my needs well. I figured it would at least suit me until later this year. But with the introduction of the Attack Database System for Phenom V3 and just recently my other new database systems ( Which will make their way into the Phenom in up coming releases ), the X2 server began to show its limits. Response times were increasingly slow during peak usage and Lighttpd was randomly hiccuping ( With “500 – Internal Server Errors” ).

    In response to the X2 server meeting its limits, I decided on an early upgrade to the EQ4 server. An Intel i7 950 ( 4x 3.06ghz ) with 8GB DDR3 memory. Quite a bit more powerful than what I need right now, but at least now I’m ready for any sudden growth in traffic. The best part is I’m still paying less than I was for a semi-dedicated plan at A2!

    With this upgrade, since I have full control of both the two servers and domain name ( Unlike before ), I was able to ensure that the upgrade was seamless. Such a relief! Past server upgrades have been very hectic, mostly due to domain name issues. A2 Hosting never revealed to me ( And had no help articles saying this either ) that their domain names for their customers are hosted through a 3rd party until after several frustrating support tickets. It was too late for them though. I had already begun transferring my domain name to another registrar.

    During both of the past server upgrades, there was extended server downtime and a lot of unhappy customers. It’s a huge relief for me and I’m sure all of you are relieved as well to see that this latest upgrade went through without any major server downtime.

    Hiya all! ( Long time, no post, I know! )

    Mono is a free and Open-Source cross-platform project that is compatible with Microsoft’s closed source .NET platform. Mono was chosen as the engine for Second Life’s scripting platform. – Just recently, Novell, the company that develops Mono has cut the entire Mono team. This means that Mono will no longer be updated and most likely will have no more support from Novell. – What will Linden Labs do? Sure, LL hasn’t even updated their version of Mono ever since it was released 2 1/2 years ago, but they have been in contact with the Mono team about certain issues with Mono.

    Linden Labs is getting ready to released Mono 2 to the grid. As of this post, we’re still running on Mono 1.6 which has a few notable issues. Mainly the “Rez lag” issue which has been fairly reduced since it was uncovered. Mono 2 fixes the rez lag issue and also has many performance increases. If Mono 2 is successful, we could be using it for many years to come. But then what? Second Life will continue growing and the final version of Mono 2 won’t grow unless LL creates their own branch of Mono, which of course means they’ll have to do all the bug fixes instead of Novell.

    But there is good news. A lot of the former-Mono team members have started a new Mono-based project called “Xamarin”. From what I know, this should be compatible with existing Mono-based software. If that is so, LL should be able to switch to Xamarin. ( Read More on Xamarin >)

    Hiya all!

    If you haven’t heard, North-East Japan ( Mainly around Sendai ) was recently struck by an 8.9 – 9.1 magnitude earthquake. Japan and also several other Pacific countries were pounded by the resulting Tsunami. This was a very powerful earthquake and has reportedly caused over 600 casualties and 700 other people are reported missing. – This earthquake is the most powerful one ever recorded that hit Japan and is among the top 5 most powerful ever recorded in the world.

    Linden Labs has released new Linden Bears on the Marketplace with which the full proceeds are donated to the relief effort by the American Red Cross. There are 6 total Relief Linden Bears, 3 of them are sitting styled and the other 3 are standing. Both styles have 3 prices to choose from, L$300 (~1 USD), L$1000 (~ 3 USD) and L$3000 (~11 USD). I highly recommend that you buy a Linden Bear, even if it’s just L$300. Every bit helps the relief effort.

    Buy Relief Linden Bears here >

    Linden Labs official Relief effort donation announcement >

    Hiya all!

     

    This is a short blog post since I am busy with Phenom V3 production, but I felt this news should interest a lot of people.

    Just recently, Linden Labs has updated their ToS/Community Standards in the disclosure of private information section to include Alternate Accounts. This means systems like RedZone are now prohibited in SL. The only way the systems can be sold is if the system asks for permission from the owner of the alternate accounts. This of course makes the system useless since you’d be better off asking the resident yourself for the names of their alts. RedZone is especially useless since not only does it now ask for permission, but RedZone and similar systems base their “Alt Detections” off of unreliable data: IP Addresses, which have time-after-time been shown to be unreliable personal identification methods. This is why Linden Labs doesn’t immediately IP ban people. They only IP ban as a last resort to avoid accidentally banning innocent avatars who have/might receive the same IP address.

    Now that disclosure of alts is prohibited, will RedZone survive without it? There is no mention that the harvesting of IP addresses is prohibited. So systems that attempt to ban peoples alts, but not disclose their identities to the ban system’s owner(s) might still be able to squeak by the ToS/CS. – Oh well, at least RedZone is out of the picture now.

     

    Link to Jira Original Comment >>

    Hiya all!

    Once again a drama has stirred up in the Second Life community regarding the “Alt Detecting/Banning” systems such as RedZone. There are similar devices to this one such as CDS which supposedly bans known copy-bots. – Sounds like a good deal, right? When you ban someone from your sim/land, you want to ensure they won’t come back on an alt account and continue doing what got them banned.  Or maybe you just want to know when you’re talking to someones alt. – Too good to be true, right? Of course it’s too good to be true.

    RedZone and CDS may work to some extent and that’s because they exploit the ‘Parcel Media’ feature found in all SL viewers. – Whenever you move/teleport to a new parcel, your viewer queries the media server the land owner has set. This query includes your avatars name and UUID for multiple purposes such as traffic statistics. Of course the query also includes your IP address and that’s the key reason of how RedZone works. RedZone simply sets the parcels media URL to a server the creator of RedZone owns and stores your avatar name, UUID and your IP address. This is known as “Data Mining” which can be used for good, or for bad. – The reason why I said “RedZone and CDS may work to some extent” is because IP addresses are not a reliable way to track a person. Here are some reasons why.

    1. The most obvious reason is that most IP addresses are dynamic, meaning they’re prone to changing. Usually this happens when the user disconnects their modem for a certain amount of time.
    2. The IP address used is set to your modem, not your computer. This means any computer that is connected to the same modem has the same IP address over the internet.
    3. If you’re always on the go, but still like to log on to SL. You obviously would not be using your home internet connection, you’ll be using your wireless modem or public WiFi which of course will have different IP addresses.
    4. Proxies and VPN’s allow you to easily mask your IP address with another.
    5. Since most IP addresses are dynamic, you could end up getting an IP address of an avatar banned by CDS or RedZone.

    As portrayed above, supposed alt tracking systems are not reliable since IP addresses are not permanent and are easy to change. This doesn’t mean RedZone and CDS don’t work, it just means they’re not reliable at what they claim to do. For example, if someone griefs on your land and you ban them using RedZone, if the griefer knows what they’re doing, they’ll just change their IP address and come back on an alt. RedZone won’t work because their IP address is not the same. There’s another way to bypass RedZone and that’s to simply turn the Parcel Media feature off in your viewers preferences. ( Preferences / Audio & Video / Enable Streaming Media )

    RedZone and CDS also claim they can detect copybots. This is wrong. RedZone and CDS simply check a database of supposedly ‘Known Copybotters’ to see if the IP Address or UUID of the detected avatar exists in it. Thus they’re not detecting copybots, they’re just banning people who have the same IP address a copybot once had. Or people the creators of the system do not like. ( A competitor once did the same thing to me by having her land security devices use her ban list by default, which of course I was on since I’m such a griefer *rolls eyes* )

    Conclusion: I wouldn’t recommend anyone waste their money on RedZone, CDS or other similar devices. The core function of the devices, IP detection, completely relies on an unreliable variable: The avatar could have parcel media turned off, the griefer avatar may have changed their IP address, the avatar may be the innocent room mate of a griefer, the avatar might be your unlucky friend who received the IP address of a “known copybot”… And the list goes on! – Over all it’s more trouble than it’s worth.

    PS: Do not spend any money on “RedZone/Alt Detection Protection”, just turn off Parcel Media in your Viewers Preferences window. This is the function that the alt detection systems exploit.

    PPS: There is a Jira issue about RedZone and similar data mining systems here.

    Hiya all!

    Just today I finally got my new server ( This very one ) online after several days of dealing with iffy support at my current domain registrar ( Soon to be my old registrar ). Anywho… The new server is a low end dedicated server which is actually two times less  expensive than my previous semi-dedicated server. The only catch is that the server is slightly slower than my previous server, but that’s not an issue since most of my traffic is made up of LSL script communications. The chances of the server becoming overwhelmed are pretty low.

    If you’re wondering what host has such great deals, it’s Hetzner. It’s based in Germany, so not all of the website is in English and support might not be as easy as other US-based hosts. But the kind of technology available and the great pricing for it is definitely worth it.

    Hiya all!

    In Second Life, there doesn’t appear to be a clear line in between pure griefer weapons and actual combat/defensive weapons. Unfortunately any actual combat system not intended for griefer use like my own can be abused by residents with griefer intentions but  even things not intended for combat can be used as a griefer tool. Many times I’ve seen residents drive their vehicles into other residents intentionally to try and grief them. But what doesn’t seem to be clear to many residents, Combat system creators and users alike is the line in between Combat Systems intended for defense/combat and systems intended for griefing. – A lot of times i get asked by customers “Does your HUD have a crasher?”, which is a definite no.

    Any combat system that has an attack that is designed to disrupt the residents viewer or a simulator in anyway can be considered a griefer tool. As well as attacks that don’t target any specific resident and instead just attack random people, everyone in the sim or even the sim itself. That means attacks such as…

    • Render lagging/video crashers
    • Chat spammers ( Including variations such as debug spammers )
    • Dialog spammers ( Including variations such as map spammers )
    • Particle spammers
    • Sim laggers/crashers
    • Sound spammers
    • Nukes

    The above attacks are unfortunately featured in a lot of combat systems in SL. What’s even worst is that almost all of the griefer attacks affect the target resident and everyone near the resident. That means if you only intend to crash/lag a single person using video crasher, you may end up accidentally crashing/lagging everyone within draw distance of the attack, even including yourself!

    Real combat systems unlike griefer tools are intended to target only a single resident or a small area. The defining difference is that the attacks target the residents avatar and not their viewer or the simulator. – Real combat system creators like myself intend for our systems to be used in actual combat sims,  for pranking friends or in defense.  - IE: Someone intentionally shoots you while you’re in a building sandbox, you could first turn on your shields and then deploy a mouselook blinder on the shooter to prevent him from aiming his gun. If that doesn’t work you could use a pusher on him to move him away from you. An AR could also be filed if the resident is still persistent on shooting you and/or other sandbox patrons. – We creators don’t intend for our HUDs to be used to deploy as many attacks as possible on everyone in random non-combat sims. This is why some creators like myself have shut-off functions in our combat HUD’s that allows us to shutdown HUD’s being used to grief if the owners are uncooperative.

    Featuring griefer tools is why a lot of Combat HUD’s and their creators develop bad reputations. Though sometimes it’s even because the Combat HUD was designed so poorly that it ends up lagging the sim and irritating the residents in the sim. Whatever the case, it’s always important that you do NOT use the griefer-type attacks described above. Even if you don’t intend on using those attacks for actual griefing, the collateral/area effect of those attacks is way too high and can easily get you a ban/suspension from Second Life if you irritate people other than the target.

    Hiya all!

    We’ve had Display Names for a while now, so I thought I’d offer my opinion on them.

    When I first heard of Display Names when watching the Keynote presentation by Philip Linden ( Soon-to-be former CEO of Linden Labs ), I figured it was more of a nickname not really a cover-up name that replaces your user name. Something like a more featured group title. It was a bit disappointing seeing how much more extensive and complex Display Names really are.

    Some say Display Names are a complete mess and should be removed from SL entirely. I think they just need some re-working. Display Names are fun to play around with, but currently aren’t a very serious feature. By that I mean they don’t really serve a purpose for SL as a whole, they only benefit the RP’ers and people who don’t like their user names.

    Here are the reasons why I don’t like Display Names.

    • Obviously Display Names make recognizing people MUCH harder. Especially if the name is made up entirely of special characters like “ᾏẛﭐﺚ” instead of just “Ariu”
    • A lot of people are choosing exotic names instead of  just variations of their user names or easy to remember and recognizable names.
    • There are still issues with DN’s, mainly the “???” issue making it extremely difficult to recognize people since both their DN and UN appear as “???”.
    • It is possible to impersonate other residents by making your DN another persons UN. The 7 day waiting period after you set your DN won’t stop people who make “Throw-away” accounts.
    • All new residents are forced to use the “Resident” last name
    • In some places, only display names appear instead of DN and UN or just UN. ( Such as the Friends Online widget on the dashboard )
    • Slutty avatars can and do choose extremely ’sexual’ names and do go to PG/General regions.
    • Two people can have the same display name.

    Here are the reasons why I like Display Names

    • Obviously you can get the name you always wanted. IE: I have “Ariu Kitteh” as my Display Name now.
    • Partners can choose the same last name.
    • RP’ers can choose more story-like names. IE: “Cpl. Smith” for someone who’s in an SL military.
    • They’re much more flexible, not restricting you to just a first and last name with numbers and letters.

    Over all, I mainly dislike Display Names as they are now. I believe an option such as “Show my Display Name only to Group Members/Friends/Nearby avatars” would be something useful. That way RP’ers can still be happy without annoying everyone else since their DN is hard to recognize.

    Hiya all!

    This is another post on the ongoing issue of Script Resource hogging, why it’s bad and how to prevent it.

    If you’ve read my previous blog posts you know what I mean by “hogging script resources”, but if not continue reading this paragraph. – Every single script uses the simulators resources even if the script is turned off or isn’t performing any functions. Scripts that are running are periodically checked by the sim to see if any events need to be triggered. Both running and non-running scripts use either 16kb or 64kb of the sims memory. In normal amounts this is a trivial process for the sim, but unfortunately normal amounts of scripts are a rare sight in Second Life.

    Due to the threat of copybotting, designers started selling their products with “No-Modify” permissions. This meant that the customers were unable to in any way customize or even resize the products for their avatars shape. To counter this, the designers added “Resizer Scripts” to the products which required a script in every single prim and very easily turned into monstrous amounts of scripts. The worst part is that No-Modify doesn’t stop copybotting at all since copybots simply rebuild the products from the viewers memory and not from the inventory system. Even if copybots rebuilt the products from the inventory system, no-mod still wouldn’t stop them, no-copy would be the right choice. – Unfortunately, many designers are still selling their products as no-mod and still use resizer scripts. As a result, many sims are under a heavy script load due to the massive amount of scripts residents pile on unintentionally by wearing products with resizer scripts.

    3 Tips on How To Avoid Being A Script Hog

    1. Obviously the first tip is to not wear or buy accessories/apparel that are no-mod and include resizer scripts. It is ok if the products have mod permissions, because that means you can remove the scripts. ( Viewers like Phoenix have a function under the “Tools” menu called “Remove all scripts in selection” which does what it says and is very useful )
    2. On the Phoenix viewer, you have an option called “S.Count” when you select an attachment and click the “More>” button. Use this to track down script heavy attachments. On Viewer 2 you have a memory usage list ( World / Place Profile / About Land / (Bottom left corner ) Script Information/ My Avatar ).
    3. Detach items that you do not need. IE: If you’re not dancing, then detach your “Dance Animation HUD”. – Or – If you’re not using your weapons, then detach them or at least detach the “Drawn” versions of the weapons that are invisible. Weapons are notorious for being script heavy.

    [17:37:09]  Counted scripts in 4 objects: 982 < – A patron in my sandbox had dual hand guns + holsters that used nearly 1000 scripts altogether. He was cooperative when I asked him to detach them and never use them again due to the guns being insanely inefficient.

    [17:34:44]  Counted scripts from 21 attachments on <Anonymous> Fearguis: 2023 < – Unfortunately he also had a massive amount of resizer scripts attached alongside those guns.

    With all of those scripts he had attached, he was using over 25% (9.7ms of script time and ~50mb of script memory) of my sims script resources!

    Click to enlarge

    Only 15 avatars with around ~450 scripts each

    Only 14 avatars with less than 200 scripts each

    Benefits of not hogging script resources

    1. Sim owners like myself are less likely to get mad at your for lagging ours sims.
    2. You will teleport faster and have less failed teleports since the current and destination sim have less work to do.
    3. Your and other residents scripts may perform better since you’re causing less lag. ( Of course it also does depend on if other people are hogging scripts )
    4. Whenever you teleport, your current and destination sim won’t lock up for 10 seconds due to Mono’s rez/unrez lag.
    5. You will look less like a noob to experienced residents. :P
    6. In the future, there will be a cap on how much script memory all of your attachments together use. It’s best to be in the habit of regulating your script usage now instead of being inconvenienced when it happens.
    7. It’s totally super duper cool. :D

    Before you complain about sim lag, perhaps you and your friends should detach your hundreds of scripts and then see if you have anything to complain about.

    Hello world!

    In the world of Second Life exists an option that you can apply to any kind of prim, this option is known as “Full-Bright”. What Full-Bright does is it makes the prim fully illuminated, meaning it looks as if there’s a light shining on each side of the prim. This option is ideal for things like light bulbs and buttons, though many people misuse this option not knowing what the option really does. This is most commonly done to things such as hair and jewelery.

    When it’s daylight, Full Bright objects don’t appear much more brighter than other objects around it. During nighttime, full bright objects standout much-much more than other objects, this makes full bright hair look incredibly silly. The avatar being mostly dark and the hair sticking out like a sore thumb.

    So… When you buy some new hair or jewelery, or any accessory really, make sure the Full-Bright option for all of the prims is disabled. Otherwise your avatar could look really silly in the dark. :P