tmewett
commented
4 years ago I think the issue arises from Architect.c:796, in the function spawnHorde, which makes the call
randomMatchingLocation(&(loc[0]), &(loc[1]), FLOOR, NOTHING, (hordeCatalog[hordeID].spawnsIn ? hordeCatalog[hordeID].spawnsIn : -1)This function is defined at Architect.c:3732:
// fills (*x, *y) with the coordinates of a random cell with
// no creatures, items or stairs and with either a matching liquid and dungeon type
// or at least one layer of type terrainType.
// A dungeon, liquid type of -1 will match anything.
boolean randomMatchingLocation(short *x, short *y, short dungeonType, short liquidType, short terrainType) {Because the bog monster horde definition has a spawnsIn entry of MUD, randomMatchingLocation only looks for a cell with MUD on one of its layers; it disregards the condition that dungeon layer should be FLOOR, which would be used if spawnsIn were 0. This means the marble statue is a matching location as it has MUD on the liquid layer, despite it having STATUE_INERT on the dungeon layer.
Adding an extra condition that monsters cannot spawn on obstructing tiles wouldn't work, as turrets are specified to spawn in WALL, dormant monster spawn in STATUE_DORMANT, etc.
withinwheels
SanatMishra
Seed 739002545, depth 11. The bog monster is fully visible and shows on the sidebar as hunting.
Any monster that spawns in a statue should be dormant and activated when the player is near. I'm fairly sure it's impossible for a creature to coincidentally be generated inside an inert statue, but this needs to be checked. Perhaps this is an edge case of a creature statue being generated in a bog.