00:00:26 Unstable branch on CRAWL.XTAHUA.COM updated to: 0.21-a0-270-g8204059 (34) 01:03:22 -!- amalloy_ is now known as amalloy 01:03:44 I need to get a proper debug environment set up at some point 01:04:12 hunting through source, adding mprfs, waiting for a recompile, then blindly trying things in-game isn't really very efficient 01:34:31 !bug 10710 01:34:32 https://crawl.develz.org/mantis/view.php?id=10710 01:35:04 having trouble reproducing this. boggarts were moving around too much so I'm using a deep elf demonologist and a hallway 01:36:10 and just waiting till it summons things that should be able to use beams and putting the demonologist between me and that summoned monster 01:37:16 I gave the demonologist 10 hp so it could die easier, but looks like the summons aren't hurting it (my debug messages with tracers show the summoned monsters are actually seeing the DED). maybe it's only certain kinds of beams 01:39:32 hm. must just be bolts since switching to a boggart and x-m'ing to keep it next to me finally got it killed by a deep elf knight's orb of energy. 01:59:18 johnstein: instead of repeated xm you can put it in a cage with grates, and take away blink 02:01:28 is that wizardry documented anywhere? 02:01:41 I didn't see anything about wizmode in docs/develop 02:02:03 what do you mean? how to change its spells? 02:03:01 I know how to set hp via &m boggart hp:10 02:03:22 but yea, I don't know how to edit the spell sets or enchantments 02:03:53 it's written somewhere, in docs/develop/levels i think, but i don't see it just yet 02:04:25 ok. I'll keep searching. 02:04:44 johnstein: https://github.com/crawl/crawl/blob/master/crawl-ref/docs/develop/levels/syntax.txt#L937 02:05:12 oh. it's just vault syntax? 02:05:15 yes 02:05:26 &m takes vault syntax just like &% takes item syntax etc 02:05:27 ok. that makes it much less mysterious and arcane 02:05:48 says you. i never remember the vault syntax either 02:06:01 heh. but I can find plenty of examples though 02:06:26 that's unfortunately my primary mode of operation 02:46:32 Monster database of master branch on crawl.develz.org updated to: 0.21-a0-270-g8204059 03:07:43 @??boggart 03:07:43 boggart (06g) | Spd: 12 | HD: 4 | HP: 16-23 | AC/EV: 0/12 | Dam: 5 | 10weapons, 10items, 10doors, spellcaster, see invisible | Res: 06magic(40) | XP: 117 | Sp: shadow creatures, invisibility, blink | Sz: little | Int: human. 03:11:30 Unstable branch on crawl.beRotato.org updated to: 0.21-a0-270-g8204059 (34) 03:30:46 -!- amalloy is now known as amalloy_ 03:32:13 -!- amalloy_ is now known as amalloy 04:24:25 -!- amalloy is now known as amalloy_ 04:40:43 New branch created: pull/613 (1 commit) 13https://github.com/crawl/crawl/pull/613 04:40:43 03johnstein02 07https://github.com/crawl/crawl/pull/613 * 0.21-a0-271-g7c7bb01: Discourage summoned creatures from Bolting their summoners (jwoodward48ss) 10(51 minutes ago, 1 file, 6+ 2-) 13https://github.com/crawl/crawl/commit/7c7bb011eefb 09:04:11 -!- yesno_ is now known as yesno 09:41:57 !source monster_shout 09:41:57 1/1. https://github.com/crawl/crawl/blob/master/crawl-ref/source/shout.cc#L149 10:39:41 hmm, this tavern poster is a pain but their questioning has revealed that the logic for choosing between ME_DISTURB and ME_ALERT is extremely weird 10:40:34 basically, a monster will shout only if the fuzzed location for a noise source is within 3 tiles of your actual location, regardless of how far away the monster is or what it can see 10:44:14 changing this may lead to some balance issues but the current behavior is just so incoherent I want to do something...most obvious change is that monsters shout on both ME_DISTURB and ME_ALERT even if they don't have a foe set 10:45:03 (it is setting a foe on an ME_ALERT that really mediates this) 10:46:33 although, maybe they don't even move towards noise if they don't have a foe set 10:48:10 basically, monsters only shout if you are their foe, and on loud noises only set you as their foe if their perception of the noise source is within a few tiles of your actual location (which they somehow know), otherwise foe stays as MHITNOT 10:52:47 advil: would changing this cause issues with chain-shouting across the level? 10:52:57 yeah, quite possibly 10:53:05 I don't understand monster code very well but it sounds like chain-shouting is what this is trying to prevent 10:53:28 and IMO we already have plenty of shouting in crawl (it's up quite a bit over old versions I think) 10:54:03 I agree that chain shouting is to be avoided 10:54:17 I'm not sure if that's really intentional here? because the mechanism is very indirect 10:56:54 another weird effect: if a monster shouts within 3 squares grid distance of your perceived location, that'll trigger other monsters setting you as their foe, but at 4 squares, it won't 10:57:00 crucial code: https://github.com/crawl/crawl/blob/master/crawl-ref/source/shout.cc#L1387 10:57:21 the comment suggests that that effect is really only intended for monsters in los 11:13:25 at the very least, this fireball mechanism is insane: it's secretly way, way better to cast fireball 4+ tiles from your location 11:14:39 afaict (maybe wrong) disturbed monsters without a foe set don't even seek 13:04:40 Unstable branch on crawl.akrasiac.org updated to: 0.21-a0-270-g8204059 (34) 18:01:12 -!- amalloy_ is now known as amalloy 18:02:19 Unstable branch on underhound.eu updated to: 0.21-a0-270-g8204059 (34) 18:59:51 -!- amalloy is now known as amalloy_ 19:00:16 -!- amalloy_ is now known as amalloy 20:46:47 -!- amalloy is now known as amalloy_ 20:51:56 -!- amalloy_ is now known as amalloy 22:35:04 Initial worship via faded altar gives wrong welcome message 13https://crawl.develz.org/mantis/view.php?id=11220 by johnnyzero 22:44:37 <|amethyst> Napkin: someone on reddit points out that http://crawl.develz.org/trunk/changes.txt hasn't updated in three or four weeks... not sure what script is supposed to update that, though 22:48:30 is it intentional that netted slimes get the web effect when they split while being netted? 22:49:07 <|amethyst> johnstein: I doubt it, but I see why that would happen 22:49:10 also seems weird that you can even net a slime but I'm assuming either it's not a big deal or that's been discussed before 22:49:15 <|amethyst> johnstein: it used to be that they'd just eat the net 22:49:20 ah ok 22:49:30 that answers my second comment 22:49:57 <|amethyst> johnstein: webbed and netted use the same ENCH_HELD 22:50:05 so when eating items went, this new behavior probably showed up 22:50:07 ah ok 22:50:22 sounds like maybe a "simple" one to fix 22:50:43 <|amethyst> whether it displays as "webbed" or "caught" depends on whether there is a trapping net at their position 22:51:04 <|amethyst> yeah, I think the fix is to not duplicate (or to remove) that enchantment 22:51:17 <|amethyst> good catch 22:51:49 someone reported it in ##crawl 22:51:59 but I couldn't verify till now 22:53:20 ty