1) Variable dungeon size (potential problem -- feature currently disabled in the source)
For my variant, I removed the line in cave_gen() that forces dungeon size to max (size_percent = 100) and used the admin character to generate a lot of cave levels. After 1000 levels or so, the code triggered a failed assertion in try_door(). This is caused by tunnels being generated outside of the cave bounds, due to calls to in_bounds_fully() instead of cave_in_bounds_fully()
2) Monster recall
Some colors for monster spells have not been updated after the change regarding the new protections: plasma, force... still refer to sound resistance.
3) Monster races
With the new parsing system, monster races that are not defined in monster.txt get an empty entry in r_info. Some functions use the "name" or "text" fields (pointers) without checking that they're not NULL. This could lead to potential crashes.
For my variant, I removed the line in cave_gen() that forces dungeon size to max (size_percent = 100) and used the admin character to generate a lot of cave levels. After 1000 levels or so, the code triggered a failed assertion in try_door(). This is caused by tunnels being generated outside of the cave bounds, due to calls to in_bounds_fully() instead of cave_in_bounds_fully()
2) Monster recall
Some colors for monster spells have not been updated after the change regarding the new protections: plasma, force... still refer to sound resistance.
3) Monster races
With the new parsing system, monster races that are not defined in monster.txt get an empty entry in r_info. Some functions use the "name" or "text" fields (pointers) without checking that they're not NULL. This could lead to potential crashes.
Comment