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

18 lines
453 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 _boss
[Reverse-engineering] [th04/th05] Remaining generic boss variables … yeah, I don't really like these ambiguous "mode" and "mode change" variable names either, but what's the alternative? Something something "sub-phase", to distinguish them from regular phases? Feels way too early to decide on something more specific. And pretty much nothing I could come up with right now would have made their inconsistent use any clearer. But I need to decide on *something* before moving on, so… eh, let's just go with what uth05win chose. Also, yeah, dealing with those 0xFE and 0xFD boss_phase constants some other time 😛 Also, today in "Weird TASM crashes": Trailing commas at the end of `public` lines… Completes P0028, funded by zorg.
2019-09-11 20:05:49 +00:00
public _boss_pos, _boss_hp, _boss_sprite, _boss_phase, _boss_phase_frame
public _boss_damage_this_frame, _boss_mode, _boss_angle, _boss_mode_change
public _boss_phase_end_hp
[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 _boss byte
[Reverse-engineering] [th04/th05] Remaining generic boss variables … yeah, I don't really like these ambiguous "mode" and "mode change" variable names either, but what's the alternative? Something something "sub-phase", to distinguish them from regular phases? Feels way too early to decide on something more specific. And pretty much nothing I could come up with right now would have made their inconsistent use any clearer. But I need to decide on *something* before moving on, so… eh, let's just go with what uth05win chose. Also, yeah, dealing with those 0xFE and 0xFD boss_phase constants some other time 😛 Also, today in "Weird TASM crashes": Trailing commas at the end of `public` lines… Completes P0028, funded by zorg.
2019-09-11 20:05:49 +00:00
_boss_pos motion_t <?>
_boss_hp dw ?
_boss_sprite db ?
_boss_phase db ?
_boss_phase_frame dw ?
_boss_damage_this_frame db ?
_boss_mode db ?
; Used for both movement and bullet angles.
_boss_angle db ?
_boss_mode_change db ?
_boss_phase_end_hp dw ?