Random Behaviour from 'int onSaveMapPic()'

[Saffith]

Hard to say, but I wouldn't be surprised. loadscr does a lot of stuff, and there's no telling what might result from changing out data while other parts of the program are using it.
The easiest thing to do would be to increase the size of tmpscr by one and load to tmpscr[2] instead.

[ZoriaRPG]

Hard to say, but I wouldn't be surprised. loadscr does a lot of stuff, and there's no telling what might result from changing out data while other parts of the program are using it.
The easiest thing to do would be to increase the size of tmpscr by one and load to tmpscr[2] instead.

I ended up rewriting it based on ViewMap(), which seems to be good, although only time will tell if it still has some issues that I missed. Adding the third index and using that failed to properly update the screen on the map, and continually blitted one screen to every space that Link visited, but I did try it. In the end, I went with my what was my first thought...

I believe that loadscr2() is safer, too, as it was designed to display maps and not do a number of other random things, as so...

https://github.com/ArmageddonGames/Z...ea8f711ab407cb