ReC98/th02/th02.h

/* ReC98
 * -----
 * Include file for TH02
 */

#include "ReC98.h"
#include "th01/ranks.h"

#undef grcg_off

// Hardware
// -------
#include "th01/hardware/grppsafx.h"
// -------

// Music Room
#define MUSIC_CMT_FILE "MUSIC.TXT"
#define MUSIC_CMT_LINE_LEN 42
#define MUSIC_CMT_LINE_COUNT 20

extern char unused_op_2_3; // Maybe debug mode?
extern char rank;
extern char lives;
extern char bombs;

#define SHOTTYPE_COUNT 3
[C decompilation] [th02/op] Title screen flashing animation 2015-02-21 13:13:58 +00:00			`/* ReC98`
			`* -----`
			`* Include file for TH02`
			`*/`

Add some useful increment and decrement macros Which we'd really like to have for the highscore entering screen. 2015-03-01 21:52:25 +00:00			`#include "ReC98.h"`
[Maintenance] Consistently use forward slashes in #include paths Completes P0087, funded by -Tom-. 2020-04-15 15:48:40 +00:00			`#include "th01/ranks.h"`
[C decompilation] [th02/op] Title screen flashing animation 2015-02-21 13:13:58 +00:00
[Maintenance] Don't modify master.h to #undef grcg_off() for TH02 Because TH04 and TH05 actually do use this macro. Part of P0089, funded by [Anonymous] and Blue Bolt. 2020-04-24 18:30:24 +00:00			`#undef grcg_off`

[C decompilation] [th02/op] Title screen flashing animation 2015-02-21 13:13:58 +00:00			`// Hardware`
[C decompilation] [th02] Code segment #2 of all three executables Only one code segment left in both OP and FUUIN! its-happening.gif Yeah, that commit is way larger than I'm comfortable with, but none of these functions is particularly large or difficult to decompile (with the exception of graph_putsa_fx(), which I actually did weeks ago), and OP and MAIN have their own unique functions in between the shared ones, so… 2015-03-14 22:25:50 +00:00			`// -------`
[Maintenance] [th01/th02] Split graph_putsa_fx() into its shared parts I did consider not doing this, because "well, can't anyone who's actually interested just diff the TH01 and TH02 implementations to figure out the differences themselves", but that duplication ended up feeling too filthy after all. And hey, it's a nice excuse to update TH02's version to current naming standards! 😛 Part of P0068, funded by Yanga. 2020-01-13 21:52:19 +00:00			`#include "th01/hardware/grppsafx.h"`
[C decompilation] [th02] Code segment #2 of all three executables Only one code segment left in both OP and FUUIN! its-happening.gif Yeah, that commit is way larger than I'm comfortable with, but none of these functions is particularly large or difficult to decompile (with the exception of graph_putsa_fx(), which I actually did weeks ago), and OP and MAIN have their own unique functions in between the shared ones, so… 2015-03-14 22:25:50 +00:00			`// -------`
[C decompilation] [th02/op] Music Room Yes, all of it. Including the bouncing polygons, of course. And since it's placed at the end of ZUN's code inside the executable, the code's already position-independent and fully hackable. 2015-02-24 14:45:38 +00:00
			`// Music Room`
			`#define MUSIC_CMT_FILE "MUSIC.TXT"`
			`#define MUSIC_CMT_LINE_LEN 42`
			`#define MUSIC_CMT_LINE_COUNT 20`
[C decompilation] [th02/op] Shot type selection Oh, OK, so this is what the PC-98 GRCG is all about. You call grcg_setcolor(), and that puts the PC-98 hardware in some sort of "monochromatic mode". Then, you just write your pixels into any single one of the 4 VRAM bitplanes. This causes the hardware to automatically write to all bitplanes in such a way that the final palette index for each of the 8, 16, or 32 pixels you just wrote a 1 value to will actually end up to match the color you set earlier. Don't forget to call grcg_off() at the end though, or you can't draw any non-monochromatic graphics, heh. 2015-02-25 22:05:20 +00:00
[Maintenance] [th02] Move remaining OP.EXE variables from ASM land to C land 2020-01-10 11:19:21 +00:00			`extern char unused_op_2_3; // Maybe debug mode?`
[C decompilation] Finish TH02's OP.EXE 2015-03-16 21:35:52 +00:00			`extern char rank;`
			`extern char lives;`
[Maintenance] [th02] Move remaining OP.EXE variables from ASM land to C land 2020-01-10 11:19:21 +00:00			`extern char bombs;`
[C decompilation] Finish TH02's OP.EXE 2015-03-16 21:35:52 +00:00
[C decompilation] [th02/op] Shot type selection Oh, OK, so this is what the PC-98 GRCG is all about. You call grcg_setcolor(), and that puts the PC-98 hardware in some sort of "monochromatic mode". Then, you just write your pixels into any single one of the 4 VRAM bitplanes. This causes the hardware to automatically write to all bitplanes in such a way that the final palette index for each of the 8, 16, or 32 pixels you just wrote a 1 value to will actually end up to match the color you set earlier. Don't forget to call grcg_off() at the end though, or you can't draw any non-monochromatic graphics, heh. 2015-02-25 22:05:20 +00:00			`#define SHOTTYPE_COUNT 3`