View changes for revision:                                                                                                                           
Event Controller - Chainer (If X, Do Y) (167, rev. 5)
By  Hiccup on 10-19-12, 04:48 pm
Category 'Event controllers', known, fully documented
This sprite does not count through IDs like the 268 does. It only uses the input ID to activate the output ID. From there you can have the output activate when the input is activated, and then output again the opposite on/off after the timer. Or you can set it so the output will not activate at the same time as the input, it waits the set time, and then activates the output . I guess this is used for sprites like the 168 where they ran out of nybbles to set a time function. Or for when you want to activate two sprites by only hitting one switch...Or simply to delay an ID from being sent out.
Data files: none
Sprite fields:
Target ID: value at nybble 2-3. 0=disable
Triggering ID: value at nybble 0-1. 0=disable
usage Mode: list at nybble 10: 0=Single Use,1=Multi Use,2=Unknown???
Input activation: list at nybble 7: 0=Input activates Output ID,1=Disable. Don't get this either??? Why create a sprite and then disable it???
Input/Output Mode: list at nybble 6: 0=Input/Timer/output,1=In+Out/ Timer/ Out
Switch Mode: checkbox at nybble 11 with mask 1
Activation Delay: value at nybble 4-5
Event Controller - Chainer (If X, Do Y) (167, rev. 6)
By  Hiccup on 10-19-12, 04:49 pm
Category 'Event controllers', known, fully documented
This sprite does not count through IDs like the 268 does. It only uses the input ID to activate the output ID. From there you can have the output activate when the input is activated, and then output again the opposite on/off after the timer. Or you can set it so the output will not activate at the same time as the input, it waits the set time, and then activates the output . I guess this is used for sprites like the 168 where they ran out of nybbles to set a time function. Or for when you want to activate two sprites by only hitting one switch...Or simply to delay an ID from being sent out.
Data files: none
Sprite fields:
Target ID: value at nybble 2-3. 0=disable
Triggering ID: value at nybble 0-1. 0=disable
usage Mode: list at nybble 10: 0=Single Use,1=Multi Use,2=Unknown???
Input activation: list at nybble 7: 0=Input activates Output ID,1=Disable. Don't get this either??? Why create a sprite and then disable it???
Input/Output Mode: list at nybble 6: 0=Input/Timer/output,1=In+Out/ Timer/ Out
Switch Mode: list at nybble 11: 0=Off; then On after Delay,1=On then off after Delay
Activation Delay: value at nybble 4-5