Jump to content

Garvin Twine

  • Content Count

  • Joined

  • Last visited

Community Reputation

9 Neutral

About Garvin Twine

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. then you simply take what is in the touch_start() event earlier posted and replace the if(llDetectedLinkNumber(0)==rightButton) with listen(integer channel, string name, key id, string message) { message = llToLower(message); if (message == "next") { //same code to change your texture as before } else if (message == "previous") { //same code to change your texture as before } } (where "previous" and "next" are the commands you choose to switch to the next or previous texture) Side comments: I would not remove the listener if you want to use this command more than once (I think you did that already). If you already reset the script on_rez event, no need to also reset it on changed for owner change as it has already reset before the change event occurred. I don't see a reset reason on every rez though, so I would keep the changed event reset (but lets not try to confuse you now more than needed but one of these is surely enough).
  2. I am not sure you are aware that these RLV strip commands are for the default's SL Avatar layers. They won't detach anything nor change / remove an applied layer on any mesh body (where this is anyway another challenge) . You might only notice so called "shoe bases" to be removed as these are still used to move the avatar up a bit to match the shoes heels height. That's correct for llOwnerSay RLV commands but as quoted above not for relay commands (because the relay should check every single issued command and if it doesnt start with an @ it will be ignored) so the syntax used seems pretty accurate to me.
  3. Obviously you do not want to understand what I write. So I do not see any sense in any further discussion at this point. I do not take any demand from nobody how I shall do my code when someone gets pissed because they make mistakes, sorry, that is just ridiculous. But advising people to mix scripts from different repos is bad advice and nothing else. It may work now and today but latest when you want to update something things will go rather crazy. So yeah, go ahead mix everything together how you think it is best and be sure some time in 2019 people who use your collars will be very unhappy and... come to us for help.
  4. You still mix up the old repo with the current one which does not have these failsafes anymore. So again your statement and "advice" is simply false! Wendy refers explicit to her Peanut 9 repo at the end of her post as current repo,. And again, it is your job to obey the license and not the code's job to tell you every little mistake. All the other references are about work done before but not recent. I get that you have an issue here, not sure why and I would not care as long you stay away from false statements and bad advice. Thank you
  5. You do not get the same thing if you replace parts of it, the result will be different. (But you are free to try and do what you like, just do not blame anyone if it does not work the way you like it) Strippy is designed and made for Peanut 9 Collars, it may or may not work in other things, it is not meant to. About failsafe: (which was removed in Peanut 9 collars so it is actually irrelevant here as it is no more deployed, so the statement "Wendy's script contain" is simply false, all script deployed these days do not even have a oc_ prefix anymore, part of what Wendy explained in her post about diverting from that) : The reason there was a failsafe, was user protection, this function was meant to ensure that the items made with the scripts are a) functional b) update-able c) following the license agreement Which would simply ensure that collars distributed with the scripts would satisfy the end-user, which is our main concern. So we implemented something that ensures open source stays open source and update able and for that we get blamed now... The irony of this would be funny if it wasn't really saddening me and well, as people hated the good thing, we removed it though I believe it was the right thing to do. There is no obligation to inform the one who violates license agreements for every of their mistakes, but their obligation to read and follow the license agreement upon using the scripts. So failsafe protected everyone, even the one who made the mistake from violating the license agreement. I simply fail to see how this can be seen in any way as a bad thing specially as this protected what you all find so important modify-able content.
  6. Very well said!👍 And I believe many still use Lumiya, and this is how they appear most of the time to the rest of the virtual world (yes I had to censor the picture): You can get your IMs (and group notices) sent to your email, you miss nothing. You can reply to IMs by email without being logged in. And all that perfectly from your phone, any phone! But seeing quite a lot of Zombies standing (or running on the spot) around while using some mobile app is really nothing I think is great to have.
  7. I do not understand what these key words even have to do with any anti-man/white man feel. I find it way more concerning how many results clear hate words against women in general SL-search delivers. But to feed the color with the thread:
  8. I think this pretty much sums it up, this is not discussion at all anymore but reasons and insults are thrown at participants if they even are allowed to discuss here. Many I read here reminds me of the method of bulverism which makes useful discussions impossible. I was accused to argue for something that helps my business... where if you look closer it is the opposite but we always believe that consensual, kinky role play without hate, sexism and racism is possible. So point is this "argument" against me makes my arguments illegal because, I am not allowed to argue...
  9. Who ever it was it was not me, I was not in SL at all that time, but took a break. Interesting what you all know what I did :). You still did not read my post it seems, I never asked for anything to be banned but for certain phrases and group that go beyond any role play to be removed nor do I make money of a ban list, what nonsense is that? But normal discussions do not seem to be possible here as there will be always someone who has to make things personal where I just wanted to add a slightly wider point of view be seen here, too. So... bye, no point in discussing here when it all goes to personal attacks.
  10. First of all, the scripts are free so I do not make money of them. Second, this is no "rape" equipment, what ever that might be. Obviously you did not read my whole post :). Then you might see the distinct difference in play and no play I try to point out here.
  11. I did multiple times without result. It is that simple indeed! And I do believe the Lab does have a responsibility to filter at least for certain things and act on that.
  12. UUFFFF This is some heavy thread and at parts I am really shocked how much more people put their "right to do what they like" above other peoples feelings, concerns and actual pain. In general, I really do not like to ban stuff from SL it is a fantasy world to live out fantasies, but at some points, aren't there just natural red lines? I heard that beast play is banned, but still finding groups and places for ***** role play. So LL rather sees these stuff loose and not like said before in this thread this will lead to ban spankers and stuff... When I type in SL Search "rape" I get 1553 results! I believe that in consensual RP everything is fine even in non-consensual-consensual, but finding groups, places and profiles all over SL who use rape as keyword, makes me serious frightened what this world has become. Misogyne clubs and parcels. Here some other group examples . I miss the role play factor here and I just cannot understand why such groups are not removed instantly. I do not think it really could be banned but I would like to see that LL takes a bit more care about what groups and places are about and ban at least some of the keywords to be used. But see, so for one this is just to play out some real weird fantasy in a safe virtual environment but things go simply to far and over the fantasy and play range here for my taste.
  13. Correct. I should have said, the command can do both, where the role part is optional. In the documentation (sl wiki rlv api) it is (at least right now) not even mentioned to have the option for the role.
  14. Actually the rlv command does both, and there is only this one command that does it. (Either it never was there or it has been removed from the sl wiki where all other rlv commands are documented). It sets the current active group and the group role in one command and was meant as one time thing, to set this and lock it with another command. This can be also troublesome in other ways, I talked to someone who abandoned by accident their own group when trying to leave another one, because the timed script did set the active one back to the one set there and so they had to file a support ticket to get back their own group again.
  15. This is for sure something you should know and can always do. But in most cases it is much easier to get out of unwanted "trapped" situations: The safe word: RED By default (and in Peanut 9 Collars this is always an option, we added that when we tried to make the safe word in general more known by adding FLÜGGÅӘNKб€ČHIŒßØLĮÊN as default safe word to draw attention there ) So if you say in local RED or in case you got chat restricted (( RED )) this will release you from RLV restrictions and you should be able to TP away to safety.
  • Create New...