Adrien, you just introduced a new bug in the latest commits!
adrientd
Lol
adrientd
Thanks for reporting!
pegperegogaucho
This is an AABB
adrientd
Maybe I should take the compiler warnings more seriously, as there was a warning about that bug.
pegperegogaucho
It's smart to just turn on all warnings, even the most miniscule ones and to read them closely
pegperegogaucho
Because bugs like that are very nasty do debug, same with swapping == and =
hesopesomeso
Events 0x4E00-0x4E19 in CKGrpTrio are all slide related- those could be used for scripting, no?
hesopesomeso
I think 0x4E0F/0x4E10 Disables/Enables slide input. 6/7 do something similar?
pegperegogaucho
I just checked:
0x4E00 looks like disable autopilot
0x4E01 looks like enable autopilot
0x4E04 disconnects the camera?
0x4E05 makes the camera follow again
0x4E0F disables input
0x4E10 enables input
0x4E11 is to make Obelix jump
0x4E12 is to make Obelix play the landing animation
0x4E13 looks like another autopilot except Obelix will fly way above the slide instead of on it
Not sure what the others do
pegperegogaucho
We already have a way to enable the "autopilot" but you need to send the event to the CKAsterixSlideFP
pegperegogaucho
I guess it could be useful to add the ones that do something observable?
pegperegogaucho
Also looks like I've made a mistake, the event 0996 doesn't actually exist for the CKHkBumper, it's actually 5196
pegperegogaucho
Also, I wonder where these numbers come from? Looks like 0900-..., 0996-... and 5196-... seem to be used for most objects, but why these numbers?
hesopesomeso
Yeah the event types are so random
pegperegogaucho
Maybe the programmers each had their event namespaces or something?
hesopesomeso
Also I believe CKHearth 0x5128 could be useful- it lights up an extinguished hearth.
hesopesomeso
It also calls an event.
hesopesomeso
There's so many repeating flags, I wouldn't be surprised