01:42:23 <Lantell> pelladn (L23 FoHu) Crash caused by signal #6: Aborted (Temple)
01:44:31 <Lantell> pelladn (L23 FoHu) Crash caused by signal #11: Segmentation fault (Temple)
02:51:28 <Discord|> <11O​dds> I hope this is the bug that caused the crashed above, though it's hard to be sure.
02:51:51 <NotCheibriados> 03CrawlOdds02 07* 0.35-a0-703-g80f85d7f28: Fix spurious reset of transiting daction monsters 10(31 minutes ago, 3 files, 10+ 0-) 13https://github.com/crawl/crawl/commit/80f85d7f2857
03:33:37 <Lantell> Experimental (bcrawl) branch on underhound.eu updated to: 0.23-a0-5261-gd9800d219b
11:43:33 <Henzell> quixfox (L16 DsAr) ERROR in 'mon-util.cc' at line 655: bogus mc (no monster data): invalid monster_type 1000 (1000) (Spider:3)
11:44:10 <Henzell> quixfox (L16 DsAr) ERROR in 'mon-util.cc' at line 655: bogus mc (no monster data): invalid monster_type 1000 (1000) (Spider:3)
12:55:02 <Discord|> <11O​dds> ^ Somewhat satisfyingly, I think this is already fixed by the recent changes to defer monster resets (it's about adding an echantment to a dead monster while wearing the Swamp Witch Scales)
12:59:34 <Discord|> <04d​racoomega> Nice
13:00:19 <Discord|> <04d​racoomega> (There's probably quite a lot of places that specifically guard against dead monsters that no longer have to, once this change is tested to be reliable)
13:00:54 <Discord|> <04d​racoomega> I recall finding and patching a bunch of individual cases where a chain-reaction causes something on a target list to become invalid partway through (often by killing a summoner, while its summons were in the target list)
13:04:59 <Discord|> <11O​dds> I think in many cases we do ideally guard against dead monsters in this way (we probably don't want messages that the summoner died, the summons poofed, and then the thing hit them)
14:10:19 <NotCheibriados> 03CrawlOdds02 07* 0.35-a0-704-g041f4b8945: Fix bestial takedown autotargetting 10(2 minutes ago, 1 file, 3+ 0-) 13https://github.com/crawl/crawl/commit/041f4b89454c
15:42:49 <Lantell> Unstable branch on underhound.eu updated to: 0.35-a0-704-g041f4b8945 (34)
16:17:09 <Lantell> Name63 (L17 MDFw) Crash caused by signal #11: Segmentation fault (Shoals:2)
16:18:20 <geekosaur> !crashlog Name63 xl=17 MDFw place=shoals:2
16:18:21 <Mnoleg> No milestones for Name63 (xl=17 MDFw place=shoals:2 crash).
16:21:01 <geekosaur> !crashlog Name63 xl=17 MDFw place=shoals:2
16:21:03 <Mnoleg> 1. Name63, XL17 MDFw, T:32166 (milestone): https://underhound.eu/crawl/morgue/Name63/crash-Name63-20260713-231708.txt
16:22:37 <geekosaur> was this just fixed?
17:12:54 <Discord|> <04d​racoomega> @wizardike There seems to be an issue with your recent commits about uncancellables. If you try to abort a blink from an unidentified ?blinking, the game will keep prompting you to blink on every action afterward, until you actually use it.  You can even drop the scrolls in question, at which point you get a prompt about a bad item if you actually accept the blink (but it still lets you do it without even identifying the scroll, so
17:12:55 <Discord|> you can pick it up and do it again)
19:59:12 <Discord|> <06r​egret-⸸nde※> A less urgent bug, but still mysterious, and one I don't know if it's linked to Odds's recent connectivity efforts or WizardIke's tile flavour pickings- adding FTILE:   .1234556S = floor_pebble_brown to st_orc_open crashes on wizmode &P placement.
21:11:43 <NotCheibriados> 03WizardIke02 07* 0.35-a0-705-g1582941bcf: Fix aborting unidentified blink scroll 10(2 hours ago, 2 files, 24+ 15-) 13https://github.com/crawl/crawl/commit/1582941bcfcd
21:37:00 <Discord|> <07w​izardike> That does sound like something I might have broken. I tried adding that line to the vault and placing it and it put the tile under the shops but didn't crash
21:37:01 <Discord|> <07w​izardike> https://cdn.discordapp.com/attachments/747522859361894521/1526447400842170378/Screenshot_2026-07-14_162343.png?ex=6a570e6c&is=6a55bcec&hm=b23c86ea1e87e6f0299c6dedf94e4db10c7d87d86197c68b3382c18d8db05612&
21:41:26 <Discord|> <07w​izardike> Actually after placing it lots of times it is always crashing now due to not being able to find a layout for the vault but removing the FTILE line from the vault definition doesn't help (and neither does marking all vaults as unused)
21:53:16 <Discord|> <06r​egret-⸸nde※> Even with a fresh save and a rebasing ontop of master I'm getting ASSERT(layout) in 'dungeon.cc' at line 4955 failed crashes, though I can also evidently confirm that this will happen with the vault placed enough times regardless of anything else. Huh.
22:36:08 <Gretell> Unstable branch on crawl.develz.org updated to: 0.35-a0-705-g1582941bcf (34)
22:59:58 <Gretell> Windows builds of master branch on crawl.develz.org updated to: 0.35-a0-705-g1582941bcf
23:00:49 <Discord|> <07w​izardike> It looks like it is running out of layouts for the portal branches off of the level. Which makes sense as we are only reclaiming the vaults for the current level before remaking it.
23:20:28 <Cbrotell> Unstable branch on cbro.berotato.org updated to: 0.35-a0-705-g1582941bcf (34)
23:30:20 <Discord|> <08o​____0> Seems known Identify scrolls are getting eaten when you cancel them now
23:30:52 <Discord|> <08o​____0> pisaster mentioned it in the roguelikes discord
23:56:10 <Gretell> Monster database of master branch on crawl.develz.org updated to: 0.35-a0-705-g1582941bcf
23:58:09 <NotCheibriados> 03WizardIke02 07* 0.35-a0-706-gde7a14e033: Fix aborting reading a scroll incorrectly wasting it (pisaster) 10(8 minutes ago, 1 file, 1+ 1-) 13https://github.com/crawl/crawl/commit/de7a14e0336b