8 Commits

Author	SHA1	Message	Date
GearsProgress	0577a450da	Formatting (again)	2026-10-22 15:04:58 -04:00
GearsProgress	f1e2b62e4a	Applying formatting and moving libraries into specific folders	2026-10-18 11:07:35 -04:00
GearsProgress	503478d665	Adding global compression header	2026-09-28 16:15:09 -04:00
GearsProgress	f4696d7009	Adding error message for mixing JPN and Latin	2026-09-25 14:43:02 -04:00
Philippe Symons	0e5cf21010	Merge remote-tracking branch 'upstream/release-candidate' into isolate_mystery_gift_builder	2026-09-22 14:15:58 +02:00
GearsProgress	6db80329b3	Fixing tutorial button crash	2026-09-14 13:21:48 -04:00
Philippe Symons	e67cfec61f	Stop referencing the RSEFRLG table in PTGB, because we no longer need it there.	2026-08-11 14:30:58 +02:00
Philippe Symons	1d57c10333	Replace text_data_table with FileContainerReader ... text_data_table was very similar in concept to FileContainerReader. But FileContainerReader is generally more flexible, as it allows you to split up your table into several chunks. This takes away the worry of these files getting too big to compress. However, we now have a maintenance duty for the text_tables file, which maps a table index to the list of chunks. We also need to be careful about every use of FileContainerReader::getPointerToFileInDecompressionBuffer(). Using it is fine when you're dealing with a single chunk or if you're sure the file doesn't span multiple chunks. But the moment you seek to a different chunk, any pointer obtained from getPointerToFileInDecompressionBuffer() becomes stale as the decompression buffer gets overwritten. Still, this function is necessary for high memory pressure situations, such as mystery_gift_builder, because we can't maintain multiple lineBuffers there.	2026-05-20 13:31:28 +02:00