Asterix Gaming Guild Logo GeneralXXLXXL 2XXL 3XXXLOlympic GamesXXL EditorToolsOff-TopicXXL RomasteredXXL 2 RemasteredOther GamesModsCaesar's ChallengeUnfair XXLPatchesFan ArtPersonal ArtSpeedrunningMediaRandomizerBETA RomeHSKALPresence AdrienPresence SPQRSupport Bot Helpdesk

#editor

adrientd
"Bonjour! Est-ce que les évènements 5128 de la CKHkTorch et du CKHkPowderKeg coïncident? Meilleures salutations."
hesopesomeso
Either way, more events: 0x512A: returns whether it's active => useless. 0x512E: If fire grab not disabled (0x4 is set), trigger event 0x42. 0x512F: If fire grab not disabled (0x4 is set), trigger start fire event (the same event as triggered by 0x5128).
hesopesomeso
Alright, in that case, it is not.
hesopesomeso
:Obelul:
hesopesomeso
I wasn't aware :KEKW:
pegperegogaucho
0x4 actually doesn't affect being able to grab fire, it just controls whether to trigger the first event node (0x3C) upon igniting
pegperegogaucho
But those events could be cool to manually trigger the event nodes inside the hearth for some reason
pegperegogaucho
But maybe too confusing for scripting? :FrogThinking:
hesopesomeso
I just went from what was written. Definitely confusing. :KEKW:
pegperegogaucho
Do you know the difference between Event 0x3C and 0x42?
hesopesomeso
In GrpTrio?
pegperegogaucho
I mean the event nodes inside the hearth class
hesopesomeso
I thought 0x42 was `light_up_extinguished_hearth_event`, but haven't researched too much into it yet.
hesopesomeso
And 0x3C is `start_fire_event`
pegperegogaucho
Okay, but starting the fire != light up extinguished hearth? :FrogThinking:
hesopesomeso
I mean... that one case where the hearth is lit up? :Obelul:
hesopesomeso
Yeah the event 0x512E only gets triggered if the hearth is dead.
pegperegogaucho
Okay, so it looks like 0x5128 triggers only event @0x3C, whereas lighting the hearth manually will also trigger event @0x42
deathhound246
How does the hex view read the bytes to be displayed? I'm noticing in Alice, it's crashing when trying to view hex for CKInput (id `0,4`). I would've though all it has to do is read the bytes indicating struct size, read that many bytes, then spit that out? It seems like it's maybe doing more than it should be?
pegperegogaucho
It might be crashing since CKInput is usually empty in the serialization