Rooba
/
ReC98
mirror of https://github.com/nmlgc/ReC98.git
1
1
Fork 0
Code Issues Packages Projects Releases Wiki Activity
ReC98/th04/midboss/vars[bss].asm

16 lines
421 B
NASM
Raw Normal View History

[Decompilation] [th05] Stage setup "Yeah, let's do this real quick, how can this possibly be hard, it's just MOVs and a few function calls"… …except that these MOVs access quite a lot of data, which we now all have to declare in the C world, hooray. Once it came to midbosses and bosses, I just turned them into C structs after all. Despite what I said in 260edd8… after all, the ASM world doesn't care about the representation in the C world, so they don't necessarily have to be the same. Since these structs can't contain everything related to midbosses and bosses (really, why did all those variables have to be spread out like this, ZUN?), it also made for a nice occasion to continue the "stuff" naming scheme, describing "an obviously incomplete collection of variables related to a thing", first seen in 160d4eb. Also, PROCDESC apparently is the only syntactically correct option to declare an extern near proc? Also, that `boss_phase_timed_out` variable only needs to be here already because TCC enforces word alignment for the .data segment… yeah, it's technically not related to this commit, but why waste time working around it if we can just include that one variable. Completes P0030, funded by zorg.
2019-09-15 18:14:00 +00:00
public _midboss
[Reverse-engineering] [th04/th05] Remaining generic midboss variables Turning these into a struct will be very painful with all the collisions. Not going to do that until we decompiled every single reference to those. Part of P0028, funded by zorg.
2019-09-09 16:52:16 +00:00
public _midboss_pos, _midboss_frames_until, _midboss_hp, _midboss_sprite
public _midboss_phase, _midboss_phase_frame, _midboss_damage_this_frame
public _midboss_angle
[Decompilation] [th05] Stage setup "Yeah, let's do this real quick, how can this possibly be hard, it's just MOVs and a few function calls"… …except that these MOVs access quite a lot of data, which we now all have to declare in the C world, hooray. Once it came to midbosses and bosses, I just turned them into C structs after all. Despite what I said in 260edd8… after all, the ASM world doesn't care about the representation in the C world, so they don't necessarily have to be the same. Since these structs can't contain everything related to midbosses and bosses (really, why did all those variables have to be spread out like this, ZUN?), it also made for a nice occasion to continue the "stuff" naming scheme, describing "an obviously incomplete collection of variables related to a thing", first seen in 160d4eb. Also, PROCDESC apparently is the only syntactically correct option to declare an extern near proc? Also, that `boss_phase_timed_out` variable only needs to be here already because TCC enforces word alignment for the .data segment… yeah, it's technically not related to this commit, but why waste time working around it if we can just include that one variable. Completes P0030, funded by zorg.
2019-09-15 18:14:00 +00:00
label _midboss byte
[Reverse-engineering] [th04/th05] Remaining generic midboss variables Turning these into a struct will be very painful with all the collisions. Not going to do that until we decompiled every single reference to those. Part of P0028, funded by zorg.
2019-09-09 16:52:16 +00:00
_midboss_pos motion_t <?>
_midboss_frames_until dw ?
_midboss_hp dw ?
_midboss_sprite db ?
_midboss_phase db ?
_midboss_phase_frame dw ?
; Treated as a bool in TH04
_midboss_damage_this_frame db ?
_midboss_angle db ?