- 7
- Posts
- 10
- Years
- Seen Mar 25, 2023
Does anyone know if A-Map actually looks for free space? Does anyone have any information about how A-Map actually writes to the ROM?
Just feels like I get header/footer and invalid pointer errors way too often. I've noticed my data structure changes as well, it feels like A-Map just writes after the end of the table and overwrites any data there, and when nearly doubling the size of the world it starts to destroy ROMs.
Is there something I'm missing about making mapfiles larger in dimensions or making more connections than in vanilla? Is it simply not possible with the tools we have?
Is A-Map really just THAT buggy? If it messes up, simply retrying the same thing from my backup will make it work without error EVENTUALLY?
ANY and ALL information you have about A-Map's save/table structure and how it writes to ROMs is appreciated, Thanks.
Just feels like I get header/footer and invalid pointer errors way too often. I've noticed my data structure changes as well, it feels like A-Map just writes after the end of the table and overwrites any data there, and when nearly doubling the size of the world it starts to destroy ROMs.
Is there something I'm missing about making mapfiles larger in dimensions or making more connections than in vanilla? Is it simply not possible with the tools we have?
Is A-Map really just THAT buggy? If it messes up, simply retrying the same thing from my backup will make it work without error EVENTUALLY?
ANY and ALL information you have about A-Map's save/table structure and how it writes to ROMs is appreciated, Thanks.