M
M
Liblcf distributions should install the csv files, probably in `PREFIX/share/liblcf/*.csv` This will allow external tools to process lcf data using only the csvs.
RPG_RT contains routines to serialize and de-serialize every object to lcf format. Verify all of our lcf chunks are correct and that we aren't missing any. Check the following versions...
Once DBString and DBArray are used everywhere, refactor fields.csv to better document exactly what chunk types are used by RPG_RT. This will allow us to extend the type system for...
Depends on #379 This PR adds C++20 compatible `lcf::Span` and a new `DBArray` array class, which has a similar storage policy and small memory footprint like `DBString`. It also adds...
One way we could save on memory usage is by switching `EventCommand::parameters` back to `uint8_t` at runtime. This would mean we have to interpret multi-byte integers on the fly in...
The following behaviors don't load correctly in rm2k3: - [ ] No chunk for flash screen period, needed for continuous flashing - [ ] No chunk for waited number of...
There are many different kinds of patches out there. Some of them overlap in behavior. For example I think there are several that do additive blending in pictures. Some of...
liblcf uses a lot of memory. I wrote a program that reads `RPG_RT.ldb` and then exits. I measured it's memory usage with valgrind massif. Here are some quick stats: |...
EventCommands are pervasive and take up a good portion of total memory usage. Event commands have a dynamic list of parameters but most of them use few (< 10?) parameters....