Jump to content

Void Singer

Resident
  • Posts

    7,967
  • Joined

  • Last visited

Everything posted by Void Singer

  1. not bad, still doesn't compile though =) the type change on "Target" is one of the subtle (but not harmful) errors... I still count two compile errors
  2. but you're here, and it's only fair... if it'd been someone else would you have answered it? of course you would have. besides I'm betting no one gets a few of the non-obvious errors.
  3. no... don't nuke it, post the solution if you've got it... there is a point to all this rigamarole... as it stands, if I make the corrections posted here the script won't even compile... think of the poor non-compiling script!!!
  4. 1TBS to rule them all =) and in this tiny viewing space? it's an absolute blessing compared to the alternatives... so nobody? really? :: sigh ::
  5. Thanks for the clarification bob.
  6. heh, guess I shouldn't be so nice as to keep posting and putting it back on top... but I have another related REAL question... at what point does a question get marked "possibly answered" ? is that in other peoples reply feedback, a matter of having awarded points for helpful, or is it just a matter of number of replies? ETA: well I know that posting back with not answered definitely changes it back... does any post to it push it into the "possibly" category? that seems kind stupid if you ask me...
  7. Actually that part is valid, although some software writers would cry bad form depending on their style guide. you can also get away with llDetectedKey( Sensed -= Sensed ); or even llDetectedKey( Sensed = Sensed - 1 ); but I say why waste compile space =) although to give it a subtle error I could have gone with llDetectedKey( Sensed-- ); part of the experiment of this post is to see how much attention it recieves, how quickly, and at what level of expertise. it's not perfect though, since some will obviously ignore since I said I know...
  8. Ricky gets a cookie, but not the prize, it should indeed be "==" instead of "=" there... good eye , but there's still more wrong here ETA: @Cherise: actually I've been here awhile in disguise, compiling a list of all the things that really need fixing... to make it actually useful... now I'm in "me" mode for reasons of documentation. PS you deserve a cookie to as spotting the code highlighting being enabled greatly ups the tolerability of this place.
  9. I already know, this is just a test post to check various methods of posting code. But feel free to speak up if you know the answer integer  Range     = 40; float    Arc       = 2 * PI; float    Frequency = 10.0; list     Previous; integer  Search; string   Target; default{      state_entry(){           llSensorRepeat( "", "", AGENT, Range, Arc, Frequency );      }            sensor( integer Sensed ){           do{                Target = llDetectedKey( --Sensed );                Search = llListFindList( Previous, Target );                if (Search = -1){                     Previous = Target + llList2List( Previous, 0, 78 ); llDialog( Target, "Message ", [], -42 );                }           }while (Sensed)      } }
×
×
  • Create New...