00:08:45 <06p​leasingfungus> further devchat: big confusing discussion about foe_ratio 00:09:10 <06p​leasingfungus> my take on this is that the ideal state probably involves three changes: 00:09:44 <06p​leasingfungus> 1. making allies much more conservative about hitting the player than they are about hitting other mons (rip sgd) 00:10:07 <06p​leasingfungus> 2. simplifying foe ratio special cases (rip sgd) 00:10:39 <06p​leasingfungus> think the first one would address ‘lindwurm vaporizes dilly’ 00:10:55 <06r​egret-⸸nde※> I mean, that particular case can be handled rather seperately 00:10:57 <04d​racoomega> I mean, taking out the wierd charm special-case already fixes #1 00:11:12 <06r​egret-⸸nde※> they're already very conservative about it by default 00:11:26 <04d​racoomega> For the lindwurm to have otherwise shot him, there would have somehow had to be 60 HD of enemies in that line 00:11:52 <06p​leasingfungus> !source beam.cc 00:11:54 <04C​erebot> https://github.com/crawl/crawl/blob/master/crawl-ref/source/beam.cc 00:11:59 <06p​leasingfungus> ^ scary to type 00:12:24 <06r​egret-⸸nde※> (was just about to push the change when I saw this coming up >_>) 00:12:32 <06r​egret-⸸nde※> (shall I just go do so?) 00:12:49 <04d​racoomega> I can agree with the general sentiment that it would be nice for allies to consider the player more valuable than other allies, but I'm also not sure I want to outright ban any allies from risking harming the player at all, since there are situations where you effectively take trivial damage in order for them to inflict meaningful damage on multiple targets 00:13:00 Unstable branch on cbro.berotato.org updated to: 0.31-a0-1529-g7bd419a0e5 (34) 00:13:00 <04d​racoomega> Or, at least, I hesitate on this 00:13:44 <06p​leasingfungus> i’m perfectly happy to ban that 🙂 00:13:49 <06p​leasingfungus> zero hesitation 00:14:05 <06p​leasingfungus> think it’s quite intuitive 00:14:24 <06r​egret-⸸nde※> * sighs * 00:14:29 <06p​leasingfungus> haha 00:15:32 03regret-index02 07* 0.31-a0-1530-g330b8c2b23: Reduce charmed / bribed allies' reckless disregard for collateral damage 10(54 seconds ago, 1 file, 0+ 8-) 13https://github.com/crawl/crawl/commit/330b8c2b23d3 00:19:24 <06r​egret-⸸nde※> (the two intents of "allies never hit the player" and "reduce as many special cases as possible" feel very at cross-purposes with each other, because we've got so many different effects that don't have reliable results, and because they frequently don't scale well across the game. makhleb's blizzard demons are the most obvious example that comes to mind- the clouds made after freezing cloud hits both spread out messily rather 00:19:24 Unstable branch on crawl.kelbi.org updated to: 0.31-a0-1530-g330b8c2b23 (34) 00:19:24 than using a specific explosion tracer, and also are pretty harmless to players with rC+ and any AC by midgame if not later.) 00:20:33 <06r​egret-⸸nde※> would also weirdly effect grsu by making the lightning spire never fire past an innately rElec, high-ac player 00:25:17 <06r​egret-⸸nde※> (also would probably have people complain about iood servitors being exempted, since there's no way to anticipate how everything will move afterwards) 00:31:52 <06r​egret-⸸nde※> oh, makhleb servants include green deaths too, and I forgot about nemelex l3 pentagram making either cloud demon. 00:32:22 <06p​leasingfungus> think it’s very reasonable to make makh cloud demons very reluctant to blast non resistant players 00:32:47 <06p​leasingfungus> lightning spire is presumably already very reluctant to shoot past even gargoyle players 00:33:47 <06p​leasingfungus> afaik they count full for friend info purposes 00:34:36 <06r​egret-⸸nde※> also phantom mirroring nikola 00:34:41 <06p​leasingfungus> i’m fine with hypothetical iood complaints 00:35:27 <06r​egret-⸸nde※> (and cerebov) 00:35:45 <06p​leasingfungus> nikola is a beautiful prince. it’s very funny that he is a disaster to eg yred enslave at present, but i’m not convinced much hinges on his behavior 00:35:57 <06p​leasingfungus> he’s one unique and he’s rarely friendly 00:36:26 <06p​leasingfungus> cerebov even moreso, and cerebov has plenty of worthwhile non fstorm things to do 00:38:32 <06r​egret-⸸nde※> it is a late hour after a long month of work relatively close to release and it is unlikely anybody's going to find indefinitely more potential cases in advance (especially since almost anything could be involved due to gozag) 00:39:45 <06p​leasingfungus> certainly not requesting urgent changes 00:39:49 <06p​leasingfungus> nothing urgent here 00:39:59 <06p​leasingfungus> just setting out a personal manifesto 🙂 00:40:13 <06p​leasingfungus> in the fullness of time… 00:42:15 <06r​egret-⸸nde※> if this is started early in a future version, by somebody other than Draco or I ,with the energy and time to address indefinite concerns as they come up over an indefinite period of time, then I have far less resistance. just saying it's going to be a mess. 00:42:33 <06r​egret-⸸nde※> I guess crawl is a perpetual mess. 00:54:21 Monster database of master branch on crawl.develz.org updated to: 0.31-a0-1530-g330b8c2b23 01:33:17 Fork (bcrawl) on crawl.kelbi.org updated to: 0.23-a0-5140-g5775ae71e1 02:17:19 <04d​racoomega> So, some of this code actually works less well than I thought it did. Essentially, tracers account for resists against monsters when calculating beam goodness, but not the player. So allies will always assume the player is fully non-resistant to their damage, even when this is very obviously not the case. ie: monsters will never consider it safe to fire bolt of draining through undead players 02:17:53 <04d​racoomega> Even though it would be objectively helpful if they would (and we see monsters do this to each other regularly) 02:19:06 <04d​racoomega> Like, to some degree, this may be a result of shared tracer code for hostile monsters not wanting to take into account player gear and such, which is reasonable. But I know there is code elsewhere to consider things like bolt of draining useless against undead players. It's just that the 'usefulness against target' code doesn't come into play here, since you aren't what they're shooting at 02:19:43 <06r​egret-⸸nde※> (hmm. there's laughing skulls and eidola in yred's gift set, there's shadow dragons in dragon's call, there's scroll of summoning in crypt...) 02:19:59 <04d​racoomega> Presumably green deaths won't venom bolt through gargoyles either 02:20:11 <04d​racoomega> (Or djinn + undead) 02:20:42 <04d​racoomega> Apparently I'd only assumed a situation where they would be more likely to fireball a player djinn than other people, but in practice I don't think the code would let them account for this 02:21:16 <04d​racoomega> (I might have assumed this behavior since it's pretty easy enough to see from just playing the game that they will account for this with other monsters) 02:21:27 <04d​racoomega> Fire giants being more free with fireballs around other fire giants than they are around other things, for instance 02:21:50 <06r​egret-⸸nde※> necromancers and their bands 02:22:16 <04d​racoomega> I mean, immune it even more obvious, but you can still notice high resists being enough to let monsters feel more free with collatoral damage to other monsters 04:23:11 Experimental (bcrawl) branch on underhound.eu updated to: 0.23-a0-5140-g5775ae71e1 05:07:16 Unstable branch on crawl.akrasiac.org updated to: 0.31-a0-1530-g330b8c2 (34) 09:46:49 New branch created: pull/3447 (1 commit) 13https://github.com/crawl/crawl/pull/3447 09:46:49 03dolorous02 07https://github.com/crawl/crawl/pull/3447 * 0.31-a0-1531-ge9b0c1dc58: Give EEs Conjurations instead of Alchemy (#3444). 10(12 minutes ago, 1 file, 1+ 1-) 13https://github.com/crawl/crawl/commit/e9b0c1dc58d2 11:19:52 <09h​ellmonk> discussion about uskayaw piety and toxic radiance has revealed that currently you get two ticks of otr on cast before uskayaw piety is calculated, leading to very large amounts of piety gained at once. Unsure what the best way to handle this is; it seems weird that otr is so good at generating uskayaw piety relative to other things (the comparison we were using was max power shatter) 11:20:23 <09h​ellmonk> (should note this is for situations with lots of targets to hit at once) 12:01:29 03DracoOmega02 07* 0.31-a0-1531-gcae8a03998: Adjust some monster tracer behavior to be friendlier to the player 10(76 seconds ago, 1 file, 15+ 4-) 13https://github.com/crawl/crawl/commit/cae8a039988b 12:06:11 04Build failed for 08master @ cae8a039 06https://github.com/crawl/crawl/actions/runs/7372220303 12:06:42 03nlavsky02 07* 0.31-a0-1532-ge6ad0bb64a: feat: darken non-present monster resists on webtiles 10(2 minutes ago, 1 file, 8+ 6-) 13https://github.com/crawl/crawl/commit/e6ad0bb64ade 12:10:59 04Build failed for 08master @ e6ad0bb6 06https://github.com/crawl/crawl/actions/runs/7372253008 12:13:08 <04d​racoomega> Hrmmm 12:19:39 Unstable branch on crawl.kelbi.org updated to: 0.31-a0-1532-ge6ad0bb64a (34) 12:24:28 03DracoOmega02 07* 0.31-a0-1533-gcc20369e73: Fix Vehumet not supporting Sticky Flame (Oneirical) 10(48 seconds ago, 1 file, 1+ 1-) 13https://github.com/crawl/crawl/commit/cc20369e7321 12:27:53 <04d​racoomega> So far have been unable to reproduce this crash in running tests locally 12:28:26 <06p​leasingfungus> oh, that beam.cc piercing beam ally change is very scary to me 12:28:39 <06p​leasingfungus> it might be fine but i’m frightened 12:28:44 <06p​leasingfungus> fingers crossed………. 12:29:03 04Build failed for 08master @ cc20369e 06https://github.com/crawl/crawl/actions/runs/7372328579 12:29:37 <04d​racoomega> Yeah, it scares me a bit, too, but I did test a number of scenarios with it and it always seemed to work 12:29:43 <04d​racoomega> Though these test failures concern me 12:29:52 <04d​racoomega> (But again, I cannot reproduce them myself) 12:30:44 03dolorous02 07* 0.31-a0-1534-g8c38f09004: Give EEs Conjurations instead of Alchemy (#3444). 10(3 hours ago, 1 file, 1+ 1-) 13https://github.com/crawl/crawl/commit/8c38f090047c 12:30:50 <06p​leasingfungus> nice change re making friend mons check player resists, btw! 12:31:25 <04d​racoomega> If you'd asked me 24 hours ago, I would have said that they already did. Like, I was convinced that they did. 12:31:32 <04d​racoomega> But apparently not! 12:32:19 <06p​leasingfungus> crawl is just such a comically complex game 12:32:36 <04d​racoomega> I really, really wish it was possible to see the crash logs from failed github actions 12:32:51 <06p​leasingfungus> and even if one understood it at some point, someone else has probably changed things since… 12:33:08 <04d​racoomega> I think it's because this is a behavior that we see monsters do with each other all the time 12:33:39 04Build failed for 08master @ 8c38f090 06https://github.com/crawl/crawl/actions/runs/7372345983 12:33:40 <04d​racoomega> So it becomes 'how you expect a monster to act' regarding allied resists 12:34:15 Unstable branch on crawl.kelbi.org updated to: 0.31-a0-1534-g8c38f09004 (34) 12:36:08 <04d​racoomega> Like, the timing of these failures strongly points to it being my fault, but I still have no idea what the problem is >.> 12:37:03 <04d​racoomega> (I don't suppose you have any idea how it could be possible to get up the github action to save the crash dump? I know that it's supposed to be theoretically possible for github actions to save 'artifacts' that people can look at afterward) 12:37:51 <04d​racoomega> The multi-cored running of tests makes it impossible to even know which test is failing, a lot of the time currently 12:41:09 <06p​leasingfungus> never touched em, sorry… 12:42:15 <06p​leasingfungus> i wonder if better test failure messages would help 12:42:24 <06p​leasingfungus> seems like we could print the case that failed..? 12:45:56 <04d​racoomega> I mean, just saving the morgue directory temporarily in an accessible way would be great. (I am trying to see if I can figure out how to do this, but most of this is Greek to me at present) 12:48:00 <04d​racoomega> Don't suppose you know who set this github action stuff up for us in the first place, do you? 12:48:25 jesster (L8 OnFE) Crash caused by signal #11: Segmentation fault (D:5) 12:48:45 …or you can get it that way 🙂 12:49:01 !crashlog jesster 12:49:02 1. jesster, XL8 OnFE, T:4623 (milestone): https://crawl.kelbi.org/crawl/morgue/jesster/crash-jesster-20231231-194808.txt 12:51:16 <04d​racoomega> Looks like it's crashing at is_monster() here: C++ if (agent()->is_monster() && mons_att_wont_attack(attitude) && !harmless_to_player() && pierce && !is_explosion) 12:51:29 <04d​racoomega> ....I guess it's possible for agent to be null?? 12:51:34 <04d​racoomega> Maybe? 12:51:49 <06p​leasingfungus> it is yeah 12:52:10 <04d​racoomega> I wonder in what situations (and why the local tests weren't causing them) 12:52:15 <06p​leasingfungus> if you look at other checks to agent, most guard against that 12:52:22 <06p​leasingfungus> good qs 12:53:44 03DracoOmega02 07* 0.31-a0-1535-gf4f160f642: Fix a crash (hopefully) 10(64 seconds ago, 1 file, 1+ 1-) 13https://github.com/crawl/crawl/commit/f4f160f6427a 12:55:00 jesster (L9 OnFE) Crash caused by signal #11: Segmentation fault (D:7) 12:56:11 <04d​racoomega> A little googling later at some people discussing this, I am wondering if tossing this bit of code into the test actions would actually save anything created in the morgue directory for a bit. ...not that I have any way of testing this myself, either >.> - uses: actions/upload-artifact@v3 if: always() with: name: morgue path: | crawl-ref/source/morgue/ retention-days: 15 12:56:35 <04d​racoomega> And touching the actions is scary ^^; 13:02:15 GoSagan (L9 MfGl) Crash caused by signal #11: Segmentation fault (D:6) 13:04:02 GoSagan (L8 MfGl) Crash caused by signal #11: Segmentation fault (D:6) 13:05:42 GoSagan (L9 MfGl) Crash caused by signal #11: Segmentation fault (D:6) 13:05:44 ghawar (L5 GrIE) Crash caused by signal #11: Segmentation fault (D (Sprint)) 13:05:46 Unstable branch on crawl.kelbi.org updated to: 0.31-a0-1535-gf4f160f642 (34) 13:06:06 <04d​racoomega> Let's hope that makes them stop >.> 13:14:22 !crashlog GoSagan 13:14:22 3. GoSagan, XL9 MfGl, T:5956 (milestone): https://crawl.kelbi.org/crawl/morgue/GoSagan/crash-GoSagan-20231231-200459.txt 13:14:28 it shouldn't have repeated 13:15:29 but I guess it did… 13:20:00 <05i​coson> there's a lot of scenarios (perhaps especially including tracers) where there's no agent 13:20:27 <05i​coson> in this last case swooping for whatever reason uses a tracer with a coordinate source but no agent 13:21:50 <05i​coson> re why this wouldn't be caught locally, it looks like that test failure is during abyss_short_run, so either you weren't running the full test suite (e.g. running crawl -test instead of make test, or running tests not on a debug build), or the randomness inherent in that particular test means it's not guaranteed 13:22:28 <05i​coson> also, the best way to test CI changes is to try it out in a branch of one's own crawl fork 13:28:50 <05i​coson> (it does print it, but the tests are running on multiple cores, so the outputs for the crawl -test suite and the stress tests are interleaved and you have to interpolate back) 13:31:46 <04d​racoomega> This is the first time I realized they were two separate things 13:32:12 <04d​racoomega> All this time, I just thought different numbered tests were running in independent threads 13:32:56 <05i​coson> ah, the numbered ones run in sequence 13:33:25 <05i​coson> possibly it'd be better to disable multi cores there but I think until recently github runners didn't support that at all, so it only mattered locally 13:34:14 <04d​racoomega> (Also did not realize that crawl -test did not run all of them, even if perhaps I should have noticed from output >.>) 13:34:35 <05i​coson> yeah, that's just the builtin ones and the lua scripts from the test/ directory 13:36:28 <04d​racoomega> (Is there any reason that doesn't run all of them?) 13:36:39 <05i​coson> it can't 13:37:03 <05i​coson> the other tests involve rc scripting 13:38:23 <05i​coson> so are a completely different setup and infrastructure from the lua tests 13:38:39 <05i​coson> more like qw or something 13:39:22 <05i​coson> e.g. this is the one that did trigger that crash: https://github.com/crawl/crawl/blob/master/crawl-ref/source/test/stress/abyss_short_run.rc 13:41:34 <04d​racoomega> Oh boy 13:44:07 <05i​coson> the abyss ones tend to trigger all sorts of stuff, I'm guessing it was some misc abyss monster with a weird tracer 15:01:49 -!- Loggers_VIIIj is now known as Loggers_VIII 15:34:35 03PleasingFungus02 07* 0.31-a0-1536-gad166cc88d: Describe monster explosion damage (regret-index) 10(66 seconds ago, 3 files, 99+ 13-) 13https://github.com/crawl/crawl/commit/ad166cc88d85 15:37:44 03PleasingFungus02 07* 0.31-a0-1537-g69dc257577: DELETEME 10(42 seconds ago, 1 file, 0+ 5-) 13https://github.com/crawl/crawl/commit/69dc25757739 15:38:23 <04d​racoomega> I'd really rather like to rename quicksilver oozes. They don't do the one iconic thing that every other thing named 'quicksilver' in the game does (ie: dispel magical effects) and that feels wrong at this point. But I'm not sure what they should be called instead. It's not like we have some well-known 'metal that is antimagic' thing going on. (Lead is sometimes used for this purpose in fiction, but 'leaden' is not a word to 15:38:24 describe something that moves very quickly) 15:38:40 mercurial? 15:40:25 <06p​leasingfungus> heh 15:40:52 <06p​leasingfungus> boring answer is to call them an 'engulfing ooze' and unmetallize them 15:41:04 <06p​leasingfungus> (i like their current name, but i'm very biased) 15:41:19 <04d​racoomega> I like the word but also: I do kind of feel it's misleading? 15:41:29 <04d​racoomega> Since we're so consistent about it everywhere else 15:41:35 <04d​racoomega> Dragons, breath, wands, elementals 15:41:44 <06p​leasingfungus> they share a mission statement with other quicksilver things, which is to poop on casters 😛 (not very serious here) 15:41:51 <06p​leasingfungus> (but a little serious) 15:42:05 <06p​leasingfungus> so unfair, qs oozes predate half of those things... 15:42:11 <04d​racoomega> Do they? 15:42:22 <04d​racoomega> I wonder if this feels weirder having skipped that part of history to arrive at the present 15:43:35 <06r​egret-⸸nde※> combine them with [so-under-performing-they-spawn-pre-lair] azure jellies and call them cold iron oozes 15:43:56 <04d​racoomega> Cold iron oozes also sound petty slow 15:43:57 <06p​leasingfungus> ordering is (dragon / breath), ooze, elemental, wand, iirc 15:44:21 <04d​racoomega> My brain originally went for stuff like 'gallium ooze' or 'platinum ooze', but I'm not exactly sold on these either 15:44:34 <06p​leasingfungus> advantage of moving them to something more watery is that the messages work right 15:44:42 <04d​racoomega> Oh, for engulfing? 15:44:45 <06p​leasingfungus> yeah 15:44:52 <06p​leasingfungus> iirc i did some special casing for them, but it'd be nice to cut that, and also 15:44:57 <04d​racoomega> (What's wrong with the messages now?) 15:45:03 <06p​leasingfungus> iirc amphib creatures are immune to water hold 15:45:06 <04d​racoomega> Oh, hmm 15:45:09 <06p​leasingfungus> which also includes qs ooze hold because i never got around to special casing it 15:45:14 <04d​racoomega> Probably fish not happy to breathe in liquid metal, in theory 15:45:17 <06p​leasingfungus> yes. 15:45:29 <06p​leasingfungus> anyway just making them fast super water elemental jellies would solve that 15:45:38 <06p​leasingfungus> not like they're particularly metallic in general 15:46:01 <06p​leasingfungus> but if you want liquid metal idk what you really get other than mercury/qs. that is the metal de jure! 15:46:19 <04d​racoomega> The watery thing does make sense 15:46:20 <06p​leasingfungus> might have better luck changing literally all the other quicksilver things 15:46:34 <04d​racoomega> That sounds much less good to me 😛 15:46:45 <06r​egret-⸸nde※> it... is a weird initial association we first were handed 15:46:45 <06p​leasingfungus> ok, bad pitch: rename qs oozes to giant amoebas 15:46:49 <06r​egret-⸸nde※> ha 15:46:50 <04d​racoomega> Ahahaha 15:47:04 <06p​leasingfungus> ??nostalgia[3 15:47:05 <04C​erebot> nostalgia[3/4]: Nostalgia is a feeling that one should shake off, not wallow in. 15:47:10 <06p​leasingfungus> ^ never gonna be me 15:47:14 <04d​racoomega> Pfff 15:47:59 <09h​ellmonk> gallium elemental imo 15:48:28 <09h​ellmonk> dis is slightly hotter than normal because of all the people there (it is a big city) 15:48:48 <06p​leasingfungus> https://discord.com/channels/735056636644687913/747522859361894521/1191149873739874367 15:48:49 <09h​ellmonk> I'm so full of gallium yum 15:48:54 <04d​racoomega> (I mean, I think elementals can regular their own temperature to some degree, considering fire elementals are just fine being on fire all te time) 15:49:02 <06p​leasingfungus> we're talking about renaming the ooze, not the elemental, tho 15:49:09 <09h​ellmonk> oh 15:49:15 <04d​racoomega> Yes, the elemental still quicksilvers you! 15:49:16 <09h​ellmonk> hmmm 15:49:23 <04d​racoomega> The ooze is the odd one out 15:49:24 <06r​egret-⸸nde※> (aside from them being so frail they fit into the pre-lair ice caves, which is a weird place for them in general, it doesn't look like any vaults use quicksilver oozes in a metallic theme quality, just for Is A Mid-Tier Slime qualities) 15:49:26 <09h​ellmonk> bromine slime 15:49:26 <06p​leasingfungus> (would also be nice to get more thematic space between those two) 15:49:32 <09h​ellmonk> it can just be less metallic 15:49:35 <06p​leasingfungus> (qs ooze and qs elemental are just. it's the same thing.) 15:49:38 <06p​leasingfungus> (thematically) 15:49:41 <04d​racoomega> That too, yes 15:49:54 <06r​egret-⸸nde※> no ice elementals, no fire slimes 15:49:56 <04d​racoomega> Some kind of liquid/fluid that feels... antimagic-y somehow 15:49:59 <06p​leasingfungus> flimes 15:50:22 <06p​leasingfungus> antimagic-y for the will inf thing? 15:50:28 <06p​leasingfungus> seems like we could theme will inf in other ways 15:50:48 <04d​racoomega> No, no, it currently has AF_ANTIMAGIC 15:51:19 Unstable branch on crawl.kelbi.org updated to: 0.31-a0-1537-g69dc257577 (34) 15:51:36 <09h​ellmonk> void slime 15:51:40 <09h​ellmonk> put them in abyss 15:51:46 <09h​ellmonk> pog 15:51:46 <04d​racoomega> So I guess I was just wondering 'is there magical liquid substance that has a direct flavor fit'. There may not be. 15:51:56 <06r​egret-⸸nde※> infinite will is a weird thing to highlight on a slime because 1: why do different mindless slimes even have noticeably different capacity to think and care and rage against external manipulation and 2: acid blobs are at 160 will already anyway 15:52:12 <04d​racoomega> 160 is basically infinite 15:52:29 <09h​ellmonk> 160 is just like, you can vuln scroll it 15:52:29 <06r​egret-⸸nde※> "infinite without vuln", anyway 15:53:21 <04d​racoomega> So possibly it doesn't even require any additional justification to be arbitrarily high 15:53:21 <06p​leasingfungus> DO: right, i forgot 😛 15:53:35 <06p​leasingfungus> i like void slime btw 15:53:39 <06p​leasingfungus> it engulfs you in the void 15:53:49 <06p​leasingfungus> i feel like we're stealing that from RW or something but i'm fine with that 15:53:57 <06p​leasingfungus> oh it's mtg 15:53:58 <04d​racoomega> Spacey slime is a good aesthetic 15:54:12 <04d​racoomega> (Though just about all blobby space things are abyssal at present) 15:54:18 <06p​leasingfungus> w/e, their void slime is a totally different dynamic 15:54:20 <09h​ellmonk> rw slimes just do the splitty thing and sometimes cast a small projectile of the damage type they're immune to 15:54:23 <04d​racoomega> Maybe it ate a tiny piece of the abyss 15:54:28 <06p​leasingfungus> yum 15:54:31 <06r​egret-⸸nde※> going to need a tile that hopefully looks very different from starcursed masses 15:54:33 <09h​ellmonk> don't think dcss slimes are very similar 15:54:50 <04d​racoomega> I mean, also RW 'Void' is a very specific thing that none of this does 15:55:08 <06p​leasingfungus> when are we adding blazerip, the most busted spell in rw 15:55:09 <09h​ellmonk> yeah it's also tied to what, arcane element or sth 15:55:13 <06r​egret-⸸nde※> one has to name and associate a given pure element with something and rift wizard is just shoving in the words "arcane" and "void" for that 15:55:33 <06r​egret-⸸nde※> somewhat reflects how in crawl there's, what, "orb spider" and...? 15:55:51 <06r​egret-⸸nde※> (eye of devastation, I guess....) 15:56:18 <04d​racoomega> I was trying a few things with a portmanteau generator to see if any cute puns jumped out for various combinations of 'void' + 'jelly/ooze/slime' and am cackling at it suggesting 'Gaplesauce' 15:56:29 <06r​egret-⸸nde※> delicious. 15:56:56 <04d​racoomega> I mean, basically every void thing in RW eats walls 15:57:07 <09h​ellmonk> oh right, the wall destruction effect 15:57:19 <09h​ellmonk> been a while since i played 15:57:49 <06r​egret-⸸nde※> (since they have a Nature school rather than an earth school and thus have all of two earthy spells) 15:57:58 <06r​egret-⸸nde※> (also all of three or four poison spells?) 15:58:39 <06r​egret-⸸nde※> (I guess six with the spiders) 16:25:42 Unstable branch on underhound.eu updated to: 0.31-a0-1537-g69dc257577 (34) 18:03:56 03dolorous02 07* 0.31-a0-1538-g0302df589c: Fix erroneous comment. 10(3 minutes ago, 1 file, 3+ 4-) 13https://github.com/crawl/crawl/commit/0302df589c01 18:20:00 Unstable branch on crawl.kelbi.org updated to: 0.31-a0-1538-g0302df589c (34) 19:11:49 03dolorous02 07* 0.31-a0-1539-g569d6c7dce: Move Agony spell quote to Curse of Agony. 10(10 minutes ago, 1 file, 8+ 4-) 13https://github.com/crawl/crawl/commit/569d6c7dce06 19:36:14 Unstable branch on crawl.kelbi.org updated to: 0.31-a0-1539-g569d6c7dce (34) 22:51:15 <09g​ammafunk> > In file included from AppHdr.h:308, > from movement.cc:11: > movement.cc: In function ‘void move_player_action(coord_def)’: > movement.cc:871:30: warning: statement will never be executed [-Wswitch-unreachable] > 871 | ASSERT(!in_bounds(you.pos()) || !cell_is_solid(you.pos()) > | ~~~~~~~^~~~~~~~~ > debug.h:58:15: note: in definition of macro ‘ASSERT’ > 58 | 22:51:15 if (!(p)) AssertFailed(#p, FILE, LINE); \ > | ^ gcc warning on trunk 23:34:55 Unstable branch on crawl.develz.org updated to: 0.31-a0-1539-g569d6c7dce (34) 23:56:05 Windows builds of master branch on crawl.develz.org updated to: 0.31-a0-1539-g569d6c7dce