5 Commits

Author	SHA1	Message	Date
nmlgc	f33a3ef220	[Maintenance] [th04/th05] Separate constant for the player↔option distance ... Used in pretty much all shot type control functions. Part of P0036, funded by zorg.	2019-10-14 23:41:57 +02:00
nmlgc	a533b5d3ea	[Reverse-engineering] [th04/th05] Player sprite area invalidation ... And once again, the TH05 version is un-decompilable. :/ It was pretty close this time, though, as the entire block between PUSH DI and POP DI kind of resembles a separate inlined function, in accordance with Turbo C++'s automatic backup of the DI register, as researched in 7f971a0. Except that it contains a loop, and Turbo C++ refuses to inline any function with `do`, `while`, `for`, or `goto`. If it didn't, it would have totally worked. Also, yes, C++ class methods are treated identically in this regard. Oh well. Shot type control functions next, finally! Completes P0035, funded by zorg.	2019-09-24 22:04:26 +02:00
nmlgc	290935fe3e	[Reverse-engineering] [th04/th05] Player character display ... Including options and the death explosions. Part of P0035, funded by zorg.	2019-09-24 21:58:09 +02:00
nmlgc	6f1f36722f	[Reverse-engineering] [th01/th02/th04/th05] Player invincibility frames ... Completes P0034, funded by zorg.	2019-09-24 21:57:53 +02:00
nmlgc	c77a9276d3	[Reverse-engineering] [th04/th05] Death-related variables ... Including the confirmation that both games have an 8-frame deathbomb window. The placement of the variables is all over the place though, what the hell? Part of P0034, funded by zorg.	2019-09-24 21:57:46 +02:00