The 'O' handling for bouldersym was updating the display value for boulder even if the value had been rejected, and if it still had the default of '\0', the map would end up with <NUL> characters. (When examined via '//' or ';', those matched dummy monster class #0 and led to the impossible "Alphabet soup: 'an("")'" that was suppressed yesterday.) Attempting to set bouldersym to ^@ or \0 would also be rejected as duplicating a monster symbol. That is now accepted and used to reset the boulder symbol to default. However, other control characters are also accepted--not due to this patch, they already are, and from a config file in addition to via 'O'--so bouldersym can still disrupt the map. But that's no different from putting control characters into a symbol set or setting them from config file via S_foo:^C.
18 KiB
18 KiB