Quote:
Originally Posted by Noopy Infinoopy
Why is that when I change the current pokemon appearing in the grass(or water/fishing) it reverts back to normal or change a few but not all i changed?  It's quite annoying. Especially when I'm working on my new map. 
|
It's a bug in AdvanceMap.
The workaround I use is to only change the species in the list one entry at a time. AFAIK you can change multiple level fields at a time, but you must change the species one at a time, like so:
- Open Map A, the one you're editing.
- Change one of the Wild Pokemon species.
- Save.
- Switch to Map B, which can be any other map.
- If you are asked if you want to save your changes, then it means that some of the edits you made to the wild data were lost.
- Switch back to Map A.
- Repeat until you've changed all of the Pokemon species that you want to change.
Unfortunately, that's the only workaround
that I know of, and we'll need it until the next version of AdvanceMap comes out. You can try reporting the bug
in AdvanceMap's thread, though someone else may have already done so.
* * *
Quote:
Originally Posted by WillUsesUU's
It occurs when I sort a map, attempt to open a city, and create a new map.
|
Wait. When you "sort a map"? I wasn't aware that AdvanceMap had a sorting function... You
are using version 1.95, right?
Quote:
Originally Posted by WillUsesUU's
So, the map is likely corrupt. How could I fix this?
|
That depends very much on what specifically got corrupted, but in my experience, some amount of hex editing will always be needed to fix map corruption.
There are two general ways to do it, depending on how the data got corrupted.
- If the data was overwritten by data from another map, then you will need to find some free space in the ROM. Build some "dummy" data with the proper format in that free space, and then change your map's header to point to the new data.
- If the data was just randomly corrupted and was not overwritten by data from another map, then you can simply copy the valid data from an older version of your hack (if you keep backups).
First way is always the safest. The second should only ever be used if you make the mistake of trying to remove a map's wild list(s) in AMap.