Development Forum |
|
|
Malkin Manager
|
12/22/2009 | |
Does anyone have a fuller list of message numbers than the one in the CAOS Language Guide?
The CDN has some, and looking in the V2 Bootstrap suggests that 301 is flower death and 303 is flower fertilisation, but are there any more that people are aware of?
My TCR Norns |
AquaShee
|
12/23/2009 | |
Other than the ones described in the CAOS Language Guide, message numbers don't have any meaning at all. Quoted from the CDN:
Beyond this you can define your own event scripts - simply by creating an event script with the number you desire, and then triggering it. Certain commands require you to enter an event number, creation of a button (PAT: BUTT) for example requires this so that an event is triggered whenever the button is pressed. This event number specification can be either an existing event such as those listed in the CAOS Language Guide, or a new one specific to the object created. |
So events 301 and 303 were created so the flowers can tell the plant they died, but when you make your own plant you can just as well use message number 258 or something.
It could be useful to know if the C3 butterflies send message 303 to all flowers or just the C3 ones. If they send it to all flowers, you can put in a script with number 303 to make your flower react to the butterflies.
The Community Scribble: make (y)our own metaroom! |
Malkin
Manager
|
12/23/2009 | |
Thanks AquaShee! The balloon bugs send message 303 to all flowers when they fertilise/eat from them, as do the C3 butterflies.
My TCR Norns |
AquaShee
|
12/23/2009 | |
Yes, the C3 agents have a few shared variables and message numbers, but so many 3rd party agents don't that it's useless to start with it now.
It's useful for metaroom ecosystems though.
The Community Scribble: make (y)our own metaroom! |
Malkin
Manager
|
12/23/2009 | |
The more we know, the more we have to argue about?
My TCR Norns |
|