00:15:10 Unstable branch on cbro.berotato.org updated to: 0.30-a0-778-g2ef04afb54 (34) 00:54:15 Monster database of master branch on crawl.develz.org updated to: 0.30-a0-778-g2ef04afb54 01:32:23 Fork (bcrawl) on crawl.kelbi.org updated to: 0.23-a0-4884-gcf1f1e11f7 01:59:13 Fork (bcadrencrawl) on crawl.kelbi.org updated to: 0.03-1516-gf74c4cb60f 02:29:31 -!- Voxel is now known as Artfaith 04:23:06 Experimental (bcrawl) branch on underhound.eu updated to: 0.23-a0-4884-gcf1f1e11f7 05:06:41 Unstable branch on crawl.akrasiac.org updated to: 0.30-a0-778-g2ef04af (34) 08:10:23 <09g​ammafunk> Yeah numerically the proposed sub is reasonable starting point, but it's possible that they're strong enough that it would need to be mixed in with the higher tier threat list so it's a "at most one or two ever spawn" situation. Can look more carefully at subst in that vault and try some playtest fights etc 19:52:23 <09g​ammafunk> hrm 19:56:04 <09g​ammafunk> lua doc of travel.feature_is_traversable() says: > Can we get across this without swimming or flying? This isn't accurate, since it uses feat_is_traversable_now(), which does consider player properties like amphibiousness and permanent flight, since the global ignore_player_traversability is not true unless we're doing a special type of runmode 19:59:02 <09g​ammafunk> I'm not sure the function would be very useful for general lua situations if it did ignore player props, and I actually need it to consider those, so I don't want to change its logic, but I should probably change the doc 23:52:41 kuniqs (L26 MeGl) ASSERT(!monster_at(p) || monster_at(p)->submerged() || fedhas_passthrough(monster_at(p)) || mons_is_player_shadow(*monster_at(p)) || mons_is_wrath_avatar(*monster_at(p))) in 'player.cc' at line 613 failed. (Slime:5)