This doesn't solve the <0,0> problem but it does prevent mnexto() from using uninitialized coordinates if enexto() fails. It also adds several debugging messages. enexto() was ignoring map row #0 (unlike column #0, row #0 contains valid map locations). Fixing that doesn't matter for Plane of Water though since that row is stone there--that's probably a bug. It was also repeatedly re-testing the top+1 and bottom rows and left and right columns after they had already failed to be acceptable. It still does some of that, but less.
18 KiB
18 KiB