Jump to content

BlckCobra Shikami

  • Content Count

  • Joined

  • Last visited

Everything posted by BlckCobra Shikami

  1. TY Kelly for the info and clarification. But code complexity should not be an argument for choosing a solution which breaks content and removes functionality. I understand the request for more privacy in Second Life, but affecting the user experience by removing such an important functionality for all others does not really make sense. What will be next? llSensor? llGetObjectDetails? This way it will be made sure scripts can not even detect people in the sim ... Why not remove scripting completely? No more script griefers, reduced code complexity, better sim performance, ... This would be
  2. I won't repeat what I already stated in the jira the post refers to, but I find it extremely odd that a vital function like that will be removed because a few people want to hide in a game which lives from the interaction between its residents. Privacy is surely an important good and should be respected, but removing such a function breaks a bunch of scripted content which makes Second Life so special. People should have the opportunity to hide their status, but not by removing a valuable function for all others. A server side status flag, activated via the profile for example, should allow p
  3. yes, definately a phishing attempt. Do NOT reply! LindenLab will never ask you for your password. This mail is malicious and someone is trying to get your account data to steal your SL account. Cobra
  4. Attention: the following Phishing mail is cycling again. The origin seems to be a mail account in Kasachstan (.kz). The form results are apparently send to a hacked server in switzerland (.ch) Please, note, LindenLab will never ask you for your password. Below is a copy of the mail (text only for safety reasons) -------- copy of mail -------- Dear Second Life user, Due our latest IP Security upgrades we have limited access to sensitive Second Life account features. Protecting the security of your account is our primary concern We understand that this may be an inconvenience. Please understa
  5. You have 2 listen handlers in the same script - that will not work (probably not even compile without an error message) If you want to listen to 2 channels at the same time open 2 llListen(...) and in the listen event handler check on which channel it was received to forward it to the appropriate channel. Example: listen(integer channel, ...) { if (chan == 0) llSay(bChan,message) else if chan == iChan) llSay(cChan,message); : }
  6. Usually not. The only thing that may take some time and cause a tiny bit of lag lag is when you clear your inventory cache and relog. Afterwards your inventory needs some time to reload. The more items, the longer it takes. Hope this helps, Cobra
  7. I don't think you can find out if omeone muted you unless they do not respond to your IMs (which does not mean they muted you, maybe they just don't feel like answering you). In some cases people may not get your IMs because they got too many and they got capped. In this case it may be a good idea to send a notecard. Hope this helps, Cobra
  8. I like to use SciTE-LSL a derivat of SciTE-ez. It's very fast because it's light-weight, you can modify/adapt the templates for several languages and ... did I mention it already?: It's fast ... :smileyhappy: Cobra
  9. Hello Mik, sometimes it's a good idea to start the viewer, select "Preferences" from the menu before you log in and clear your SL cache. Close the viewer and start it again and try to login. Sometimes corrupted content in the cache may cause sucha crash on login. Hope this helps, Cobra
  10. Hello Lisbete/Gloria if the automatic limit settings do not fit your requirements you can also file a support ticket with LL support (Second Life Support) under "Billing" / "LindeX Billing and Trading Review Request" to have your account reviewed and a new limit set. Cobra
  11. llGetkey() retrieves the UUID of the object, not the texture ... you may want to use llGetTexture(...). For details please see the LSL wiki at http://wiki.secondlife.com/wiki/LlGetTexture Cobra
  12. Try turning off "Vertex Buffers" in Preferences - Graphics - Advanced. You will eventually need to activate "Custom Settings" before you can access the Advanced settings in that dialog. Eventually also try a Rebake - See Advanced Menu on your SL menu bar (You might need to activate it first by pressing Ctrl-D on your keyboard) Cobra
  13. No, a parcel owner is not able to see IMs between other persons - only public chat. You should anyway be aware that there is no thing like "privacy" on the net. Regarding main account and alt ... usually people tell on themself by a lot of things: typos, typical grammar, selection of words, things they have in their profile etc.
  14. Me too Actually I was logged out very rudely without prior notice (yeah, I know - it was announced in the status blog)... the scripts/notecards I edited during the past hour are off to /dev/nul now ... At least I know what I can do when I can log in again Cobra
  15. Hello Clint, LindenLab is providing a forum for feedback on Beta 2.0 where you can leave your feedback (https://blogs.secondlife.com/community/forums/v2). Additionally you can file bugs and issues to pJIRA (http://jira.secondlife.com) as Irene stated earlier. Make sure you select the proper category (Second Life Viewer) and version when filing issues. Cobra
  16. BlckCobra Shikami

    Join land

    Very good point, Irene ...
  17. BlckCobra Shikami

    Join land

    The following articles (http://wiki.secondlife.com/wiki/Help:Deeding_land_to_groups) from the wiki show in detail how this works: Please also see this article: "How does group-owned land work?": http://wiki.secondlife.com/wiki/How_does_group-owned_land_work%3F Deeding land to groups Join or Create a Group If you haven't already, you need to join the group you want to deed land to, or create a group. Note: You will need 2 people to create a group. Set Land Contribution Select Edit/Groups from the menubar. A list of the groups you belong to appears. Highlight the group you want t
  18. : too bad that the lindens didnt informed anyone Well, they did - about two years ago - if I recall it correctly
  19. Yep, if your scripts rely on the deprecated functions like llMakeSmoke() llMakeFire() llMakeFountain() llMakeExplosion() you're busted and you will have to replace them. But the were already deprecated a long time ago. Cobra
  20. yup, looks like Second Life Server messed up certain type of particles ... not sure yet which ones, but I found 2 which are not behaving as before ... I am trying to find out what they have in common and what makes them special from the others ... Cobra Message was edited by: BlckCobra Shikami Looks like there was actually fixed what was broken before. But I can not verify at the moment if it was fixed with 1.36 or before (silently) and I just did not notice. Maybe we have to check in the beta grid.
  21. Hello Naerose, this happened to me a while ago aswell. I found everything when I checked closer. I noticed it was not land I dragged it onto but a piece of the floor.. All things from the folder were in the object contents I dragged the folder onto. Cobra
  22. SL hat derzeit Probleme. Logins funktionieren nicht und es scheint Probleme zu geben, wenn Du versuchst etwas zu rezzen - das kann verloren gehen, wenn Du nicht gerade "Copy"-Berechtigung hast. Auch wohl Probleme beim Transfer von L$. Aktuelle Infos dazu findest Du im Status Blog unter: http://status.secondlifegrid.net/2010/02/02/post885/ Erfahrungsgemäss dauert es von 30 Minuten bis zu mehreren Stunden bis wieder ein verlässliches "All Clear" gegeben wird. Cobra Edited: oder wie Ansariel richtig sagte: Lies mal was da steht! ... Notfalls, wenn man kein Englisch kann, dann hilft http:/
  23. LL just posted an inworld warning as of 5:30am PST Quote: "Second Life: Please refrain from transferring no-copy objects or L$ until we give an ALL CLEAR at http:///status.secondlifegrid.net. We're working on restoring services ASAP." Also see the status blog: http://status.secondlifegrid.net/2010/02/02/post885/
  24. This effect results from the way alpha channels work. They mask out parts of the image by a alpha mask/alpha channel. That does not mean the image has to be blank at those masked areas. It can be fully white or black or whatever. The Alpha Channel decided which area will be transparent or not. So you may see it in Photoshop as solid background, but actually there is an alpha channel. Select the channels tab in PS and go into "Mask Mode" and you will see that alpha areas marked with a reddish layer when you switch back to the layer view. Hope this helps, Cobra
  25. Hello Aries, you are not overlooking anything. It's a "problem" which is kind of known for a long time ... "the-owner-after-the-next-owner-permissions". The only way around this "problem" is to use a giver which does not contain the item itself, but contacts a server you own, which will give the item to the person requesting the object. This way you can set the next owner permissions as you wish to and you don't have to pass it on as copy + transfer. This is also the way most affiliate basically vendors work. Cobra
  • Create New...