In the past couple of days the code for '/' and ';' to examine objects was changed to handle ROCK_CLASS differently (as part of revising looking at map spots showing the engraving symbol). It could potentially set up a static buffer in the object classes loop and then overwrite that when processing another class. I couldn't trigger any feedback anomalies, even when changing bouldersym to various values including class characters both before and after '`', but this redoes the suspect code to make it more robust. Also, refine the test for whether a screen symbol matches an object symbol.
106 KiB
106 KiB