Okay, so lets name the events "5196: Use speed 2" and "5197: Use speed 1"
pegperegogaucho
And by default it seems to use speed 2 as 0x20 is set (first member)
adrientd
That's why I would prefer to call 5196 speed 1 and 5197 speed 2
pegperegogaucho
But then in the editor it would display speed 2 first
pegperegogaucho
Doesn't really matter though
adrientd
Here it shows 15 the default speed and 5 the second speed. So the order seems correct here.
adrientd
a bit confusing since bit = 1 = first speed, and bit = 0 = second speed
hesopesomeso
Enum time.
pegperegogaucho
Oh you are right
pegperegogaucho
Also, on the topic of enums, is there a way to describe an enum in the json?
pegperegogaucho
Because for the bonusspitter it is useful to use an enum for the bonus type.
adrientd
You can have enums using bitflags.
For example in CKHkActivator:
```JSON
{
"name": "CKHkActivator",
"category": 2,
"id": 52,
"hookFlags": {
"5-6": {
"name": "Behavior",
"0": "Push once, never pop",
"2": "Keep pushed, pop by event",
"3": "Pop at animation end"
}
},
"properties": {
"actEvtSeq1": "On push",
"actEvtSeq2": "On anim end"
}
},
```
Same can be done with properties, like this:
```JSON
{
"name": "CKHkSomething",
"properties": {
"property": {
"name": "Bonus type",
"bitFlags": {
"0-2": {
"name": "Bonus type (again)"
"0": "Helmet",
"1": "Golden Helmet",
"2": "Potion",
"3": "etc."
}
}
}
}
},
```
But maybe a way to define an enum without bitflags could be a good idea (avoids having to put two names)