TTLG|Thief|Bioshock|System Shock|Deus Ex|Mobile
Results 1 to 5 of 5

Thread: TrapRequireAll Does Not Honor Script Trap Control Flags

  1. #1
    Member
    Registered: Aug 2007
    Location: LosAngeles: Between Amusements

    TrapRequireAll Does Not Honor Script Trap Control Flags

    New to me. 1st time I tried "Once" and the trap stopped working. It treats it like "Never" instead. My guess this is a bug with TrapRequirement, the base.

    And I assume that all the flags don't work. It could be a "one off" bug in the script and just "Once" doesn't work. I don't know. In any event, I don't see this documented anywhere, so I thought I would mention it.

  2. #2
    Member
    Registered: Jan 2001
    Location: Formby, NW England
    I think Once means 'process the first script message only', so the first TurnOn message will handled (result: do nothing), and further TurnOn messages will be ignored. In a way it's working exactly as described, but it's useless.

  3. #3
    Desperately dodgy geezer
    Registered: Nov 2001
    Location: The Wailing Keep
    I always put an NVRelayTrap with design note configured to the equivalent of Once, NoOff immediately between the RAT and whatever it is to trigger in order to achieve what I assume you're trying to do here. I've never tried setting flags on the RAT itself.

  4. #4
    Member
    Registered: Aug 2007
    Location: LosAngeles: Between Amusements
    That's what I ended up doing. I just didn't see a discussion of this before and there was no mention in the script description, so I thought I would ask.

    Somehow I think of "Once" as being on the sending side not the receiving, and for a RAT I never thought it would apply to just receiving the first TurnOn. Now that's been said, I guess it makes some kind of sense. Not a useful interpretation, but maybe an understandable one if all the RAT does is inherit the default behavior.

  5. #5
    Member
    Registered: Jan 2012
    Location: Gèrmany
    Quote Originally Posted by LarryG View Post
    My guess this is a bug with TrapRequirement, the base.
    Nearly exactly as you say, as soon as StdTrap receives a message and Once is set it will get locked (expect NoOff/NoOn is set then only a 'correct' message will lock it). I think there is also another exception if the Object sent the message to itself but it will also not forward it.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •