Jump to content

Jordguitar Flasheart

  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Jordguitar Flasheart

  • Rank
  1. Except people are dumb and they will just grab it and throw it in. Putting in code that destroys itself without warning not only causes people to file bug reports (that do take time to manually tell people to read the instructions or pointing them off to somewhere where it tells them where to fix it), it also REALLY pisses them off. It makes much more sense to code that in when you are able because it resolves the issues instantly and all you really had to do was take another minute or two typing it out. These are also not false statements, Wendy has linked to the repo that holds these fa
  2. The problem that I have with the failsafe in the repo that Wendy posted is that it may or may not tell you that you did something wrong. It will just delete itself without saying anything. If you do not know what you are doing and trying to just make a collar with those scripts with default permissions, you are going to end up with an empty object. The OpenCollarTeam repo has these failsafes as well but they do not delete the script and each one states what is wrong with the script and does this every time it is rezzed or worn. This is why I am suggesting using THEIR repo as it will guide the
  3. If you don't like the no mod scripts in the Peanut version, just go to the OpenCollarTeam's repo. In the src folder, it has all the scripts that are open source and you can easily replace the no modify scripts with those (they are named differently but the naming is about the same for the most part). Collar continues to work happily without issue (even with Peanut's Strippy plugin (for now)). You get the same collar, but now you know what is in it and what it is talking to and what it is sending off. With these no mod scripts, you can't do that and you are not sure what site it is connecting t
  4. Looks like any custom color profile that is not "nomal" will cause the viewer to throw visual garbage and prevent the video driver from recovering. Setting the color profile back to default should do the trick. http://answers.microsoft.com/en-us/windows/forum/windows_7-desktop/restore-default-display-color/7553a387-0965-4639-94c0-b21af6ab1e8c
  • Create New...