View changes for revision:
By Hiccup on 03-30-15, 07:45 pm |
Category 'Event controllers', known, fully documented |
(no description) |
Data files: none |
Sprite fields: • Triggering Event ID 1: value at nybble 0-1 • Target Event ID: value at nybble 2-3. This sprite allows up to 4 inputs to trigger the same output ID. All input IDs must be set to relevant values. Do not leave any IDs as 0 - if you have less than four, you can enter the same ID into several spaces. • Triggering Event ID 2: value at nybble 4-5 • Triggering Event ID 3: value at nybble 6-7 • Triggering Event ID 4: value at nybble 8-9 • Three options?: list at nybble 10: 0=Single Use,1=Multi-Use - Hiccup doesn't understand this one,2=Only while All Events are Active (this can be used again and again- also might need better wording. This sprite recieves an Input ID. This selects how it will start when an input ID is received. • Two options?: list at nybble 11: 0=Activates Target,1=Deactivates Target |
|
⇨
|
By Hiccup on 03-30-15, 07:45 pm |
Category 'Event controllers', known, fully documented |
(no description) |
Data files: none |
Sprite fields: • Triggering Event ID 1: value at nybble 0-1 • Target Event ID: value at nybble 2-3. This sprite allows up to 4 inputs to trigger the same output ID. All input IDs must be set to relevant values. Do not leave any IDs as 0 - if you have less than four, you can enter the same ID into several spaces. • Triggering Event ID 2: value at nybble 4-5 • Triggering Event ID 3: value at nybble 6-7 • Triggering Event ID 4: value at nybble 8-9 • Three options?: list at nybble 10: 0=Single Use,1=Multi-Use - Hiccup doesn't understand this one,2=Only while All Events are Active (this can be used again and again- also might need better wording. This sprite recieves an Input ID. This selects how it will start when an input ID is received. • Two options?: list at nybble 11: 0=Activates Target (Switches Event State),1=Deactivates Target (Switches Event State) |
|