01:21:15 <Lantell> Experimental (bcrawl) branch on underhound.eu updated to: 0.23-a0-2893-g14d70eb493
02:49:11 <Gretell> Monster database of master branch on crawl.develz.org updated to: 0.24-a0-443-g80245de
03:27:32 <Cheibriados> 03gammafunk02 07* 0.25-a0-421-g1657e52: Restore cloud/conduct changes and fix a crash 10(70 minutes ago, 5 files, 101+ 35-) 13https://github.com/crawl/crawl/commit/1657e5263c32
03:27:32 <Cheibriados> 03gammafunk02 07* 0.25-a0-422-g1567df3: Refactor a player spell damage function 10(2 hours ago, 1 file, 11+ 10-) 13https://github.com/crawl/crawl/commit/1567df330579
03:27:32 <Cheibriados> 03gammafunk02 07* 0.25-a0-423-gc46a48d: Remove a redundant application of god conducts 10(86 minutes ago, 1 file, 0+ 3-) 13https://github.com/crawl/crawl/commit/c46a48dface0
03:27:32 <Cheibriados> 03gammafunk02 07* 0.25-a0-424-g80bd347: Add an aliveness check for LRDing a monster 10(84 minutes ago, 1 file, 5+ 3-) 13https://github.com/crawl/crawl/commit/80bd347ae0f1
03:33:12 <Kelbell> Unstable branch on crawl.kelbi.org updated to: 0.25-a0-424-g80bd347ae0 (34)
03:33:43 <Kelbell> Fork (bcrawl) on crawl.kelbi.org updated to: 0.23-a0-2893-g14d70eb493
07:20:42 -!- amalloy is now known as amalloy_
09:23:06 <Lantell> Stable (0.22) branch on underhound.eu updated to: 0.22.1-59-ge965b3aba3
11:24:26 <Lantell> Stable (0.23) branch on underhound.eu updated to: 0.23.1-91-gf373564dc4
17:29:55 -!- amalloy_ is now known as amalloy
18:22:13 <Lantell> Unstable branch on underhound.eu updated to: 0.25-a0-424-g80bd347ae0 (34)
19:33:04 <Bcadren> Where's the code that decides where to initially place monsters? Got this crash report on my fork: https://crawl.kelbi.org/crawl/morgue/artagas/crash-artagas-20200119-200742.txt (A monster tried to shout while out of bounds); there are protections to prevent moving out of bounds so something had to have spawned there...but IDK where that chunk is
19:33:05 <Bcadren> to try to fix.
19:45:53 <Bcadren> hmm _valid_monster_generation_location() in mon-place has a bounds check...but find_habitable_spot_near does not...(that's used for summons and hell effects, I think from a quick grep)...I'll add a bounds check to that one (maybe mainline should too? though the issue may not exist without rock worms) and hope if fixes it (we'll see if it ever
19:45:54 <Bcadren> happens again after pushed).
20:13:40 <Bcadren> OK. this other bug report is a mainline bug. Rare circumstance bug: A summoned creature threw a large rock, which destroyed a ball lightning and killed its summoner. The game crashed because at line 60 in throw, it tried to check if the missile should penetrate based on the stats of a monster that no longer existed. (It showed up as an error caused
20:13:41 <Bcadren> by looking up MONS_PROGRAM_BUG's mon_info file, but that looks like the actual cause from the stack trace).