@adrientd Since we can document a lot of events using this, how should we describe the parameters?
```JSON
"events": [
{
"id": "0C02-0C04",
"name": "Switch to hero"
"parameter": "Hero index (0: Asterix, 1: Obelix, 2: Idefix)"
"parameter_type": "int"
"parameter_values": "0-2"
}
]
```
What we could do is consider the parameter as if it is a member/property of a class, and reuse the same description methods used to describe class members.
Since class member types are taken from the editor code, the type of the parameter also needs to be specified, like in your example.
Simple example:
```JSON
{
"id": "266B",
"name": "Display message box",
"parameterType": "int",
"parameter": "Text ID"
},
```
Same but with indication what the parameter contains:
```JSON
{
"id": "266B",
"name": "Display message box",
"parameterType": "int",
"parameter": {
"name": "Text ID",
"type": "textId"
}
},
```
"parameterType" here in the example above would be confusing because there is already "type" in "parameter", so might need a better name.
The benefit of having "parameter" be the same structure as a member property definition can make it possible to reuse things like bitFlags (if ever there is going to be a need for it):
```JSON
{
"id": "6242",
"name": "Set some settings (imaginary)",
"parameterType": "int",
"parameter": {
"name": "Flags",
"bitFlags": {
"0": "Disabled",
"1-3": "Count 1",
"4-10": "Count 2"
}
}
},
```
Ah yes, good idea on reusing that
So uh, how long did it take you guys to have ghidra analyse XXL2 with DWARF lol
Quite long... like 15 mins...? Ida was done after like a minute or two...
I have to say though... great fucking find!!!
Surely there's one for XXL1 too

For me it took an hour or maybe even more
Loading the DWARF takes the lognest
It's been going for like 2 hours for me

this is likely why, but idk why it's using so much