00:32:03 Fork (bcrawl) on crawl.kelbi.org updated to: 0.23-a0-4884-gcf1f1e11f7 04:22:52 Experimental (bcrawl) branch on underhound.eu updated to: 0.23-a0-4884-gcf1f1e11f7 06:33:41 <08nlavsky> I cannot reproduce the bug in the latest 0.29 build, 0.29.1-15-g9cfb28693d. The fix for large rock tossing has been backported to 0.29 already (https://github.com/crawl/crawl/commit/7ab86472d2c83a) 06:34:58 <08nlavsky> I see, CAO has 0.29.1-2-gbd0b4ee654 still, that's why the bug is still there 06:47:48 <06advil> cao doesn't auto-rebuild stable branches 06:48:51 <06advil> I started a rebuild 06:48:59 <06advil> !versions 06:49:15 !versions 06:51:01 !version 06:51:03 <08nlavsky> &versions 06:51:14 trunk: 0.30-a0-883-g5ad918d; 0.29: 0.29.1-2-gbd0b4ee654; 0.28: 0.28.0-62-gf889007; 0.27: 0.27.1-37-g7b29ead; 0.26: 0.26.1-16-g4e020e1; 0.25: 0.25.1-11-g244df3a; 0.24: 0.24.1-14-gf8d2b50; 0.23: 0.23.3-3-gaaff5ab; 0.22: 0.22.3-3-g34f245f; 0.21: 0.21.3-3-g218456f; 0.20: 0.20.2-3-g29329e0; 0.19: 0.19.6-3-g7d5932f; 0.18: 0.18.2-3-g5ac21b8; 0.17: 0.17.3-4-g93a25c6; 0.16: 0.16.3-4-gc506b73; 0.15: 0.15.3-3-g8e... 06:51:29 <04Cerebot> CAO: 0.30-a0-883-g5ad918d, CBR2: 0.30-a0-883-g5ad918d77d, CDO: 0.30-a0-883-g5ad918d77d, CKO: 0.30-a0-883-g5ad918d77d, CPO: 0.30-a0-883-g5ad918d, CUE: 0.30-a0-883-g5ad918d77d, CWZ: 0.30-a0-883-g5ad918d77d, CXC: 0.30-a0-782-ge64f9170bb, LLD: 0.29.1-2-gbd0b4ee654 06:51:33 loll 06:51:57 I think `!version` is the henzell command, but it probably does need to be run in irc 06:51:58 <08nlavsky> hmm, cxc still has 782 for trunk, and lld has no trunk at all! 06:52:29 not sure if namanix did the thing with submodules? 07:12:26 <06advil> apparently SDL3 is in development now 07:21:15 Stable (0.29) branch on crawl.akrasiac.org updated to: 0.29.1-15-g9cfb28693d 08:12:54 <10PleasingFungus> sdl3…! 08:15:11 <10PleasingFungus> > BlackBerry QNX support has been removed. > - OS/2 support has been removed. mein gott 08:16:21 <10PleasingFungus> also NaCl, which i’d forgotten about entirely 08:29:03 <06advil> %git stone_soup-0.27 08:29:05 <04Cerebot> nlavsky * 0.27.1-37-g7b29ead8ac: fix: don't allow cursing/uncursing wrong items (3 weeks ago, 1 file, 8+ 2-) https://github.com/crawl/crawl/commit/7b29ead8acef 08:29:22 <06advil> %git stone_soup-0.28 08:29:23 <04Cerebot> nlavsky * 0.28.0-62-gf88900778d: fix: don't allow cursing/uncursing wrong items (3 weeks ago, 1 file, 8+ 2-) https://github.com/crawl/crawl/commit/f88900778dad 08:30:59 <10PleasingFungus> hm, our servers don’t allow entering explore mode, right? why? 08:32:11 <06advil> not sure 08:32:24 <06advil> maybe just, old hardline roguelike policies? 08:32:50 <06advil> I assume it would behave like a quit from the milestone perspective (similar to wizmode) but I don't actually know that 08:34:01 <06advil> !lm adviltest 08:34:03 <04Cerebot> 275. [2023-03-16 15:33:39] adviltest the Trooper (L1 HOFi) began the quest for the Orb on turn 0. (D:1) 08:34:46 I thought it was because there were worries it might leak some wizmode stuff 08:35:55 <06advil> I'm not actually sure it does generate a quit-like milestone, unless sequell is lagging a lot 08:40:42 <06advil> oh, maybe it just registers as entering wizmode? 08:40:49 <06advil> !lg adviltest 08:40:50 <04Cerebot> 199. adviltest the Trooper (L1 HOFi), entered wizard mode on D:1 (ldierk_walled_garden_2) on 2023-03-16 15:33:43, with 0 points after 0 turns and 0:00:04. 08:40:56 <06advil> that seems to be the same game 08:41:47 <06advil> I can see that someone might worry but I'm not exactly sure what it would leak 08:42:15 <06advil> as long as external stuff handles the milestone correctly 08:42:21 <10PleasingFungus> seems good to enable 08:42:36 <06advil> might be good to know why sequell is saying the wrong thing though 08:44:13 <10PleasingFungus> sure 08:48:12 <06advil> the log entry is just generated incorrectly 08:55:27 <06advil> anyways, I'm fine with someone enabling this (with a fixed log entry; changing the kill type would be the only tricky part which would need some testing before opening up the feature) 08:58:49 <06advil> alternatively I think individual servers would be able to add -explore to the command line 08:59:01 <06advil> but that would still have the wrong log line 08:59:03 <10PleasingFungus> i can fix the ktyp but not sure about the rest 09:01:32 <06advil> it could be blanket enabled by removing or conditionally defining the way that -explore + how the default value for explore_mode is handled in fixup_options 09:02:06 <06advil> or leaving it to servers to add -explore 09:02:18 <06advil> maybe fixing ktyp and changing it on one server is the conservative approach 09:17:37 <10PleasingFungus> don’t feel a need to be that conservative 18:40:36 ironwallaby (L7 MuHu) Crash caused by signal #11: Segmentation fault (D:4)