00:32:41 Fork (bcrawl) on crawl.kelbi.org updated to: 0.23-a0-4753-g3cc4eb4eda 03:22:20 Experimental (bcrawl) branch on underhound.eu updated to: 0.23-a0-4753-g3cc4eb4eda 09:35:10 <09gammafunk> question for people interested in sequell data/game tracking 09:35:39 <09gammafunk> I would like to have qw bot games on cdi tracked in sequell 09:36:11 <09gammafunk> currently I have a cdi local sequell instance to do this, but it isn't ideal due to the overhead and the challenges of making it more publicly accessible 09:37:01 <09gammafunk> the reason being sequell is based on Perl for its irc side, and extending SASL support to perl is not something I'd like to maintain, and this would require that to hook up the local instance to e.g. freenode, as they require it of all aws-based IP ranges 09:37:09 <09gammafunk> not to mention this instance is pretty slow 09:37:24 <09gammafunk> so my thought was to add a cdi logfile to sequell, but the question is how to do it 09:37:56 <09gammafunk> I could add it as a normal trunk source but have it only accessible to the qw account on cdi, so other users' games would remain untracked 09:38:13 <09gammafunk> however this does add a lot of games to sequell data, which potentially influences default queries we might do 09:39:25 <09gammafunk> obviously we have the bot nick and there are just a lot of games being played, but given that cdi qw can run for days on end, I am somewhat worried that this may "pollute" queries we typically do, which don't always do e.g. !bot as the target account 09:40:18 <09gammafunk> alternately I could ask snark about adding it as its own game type, but this is a bit of a hack and possibly not what that type of thing was intended for (and I may need snark to set it up sequell-side, since it's not clear to me that adding a new game type in sequell config alone is sufficient) 09:40:55 <09gammafunk> so my question is: does anyone have strong opinions about potentially many qw bot games being added to trunk data 10:19:22 When I was running what I think ended up being a few hundred qw games, I know I definitely wanted a way to query it via sequell, and I'd be even more interested in doing so with how much longer you've been running it. 10:21:34 I wouldn't really worry about "polluting" queries - people with serious queries affected by this will learn to filter them out 10:22:21 I'd be more concerned if the quantity is large enough to bloat sequell's dbs and slow down everything 10:23:01 Add qw runs to boring? 10:23:19 !lg * day 10:23:20 3750. BlackCat the Convoker (L12 OpSu of Gozag), blasted by an electric eel (bolt of electricity) on Lair:1 on 2022-08-05 17:22:04, with 14982 points after 14958 turns and 1:01:02. 10:24:19 e.g. there were 3750 games finished in the last 24 hours, if cdi qw is playing 1000+ every day then that's probably nontrivial db bloat? 10:24:39 but I don't know how fast you are running it etc 10:26:06 when I was doing serious qw testing myself I had 10+ threads playing games in parallel and it produced a lot of games (and I used a sequell clone) 10:27:29 Same here but my sequell clone was ripgrep. 10:27:32 if it is only 100 games a day or something then I wouldn't worry about it 10:33:36 <09gammafunk> elliptic: yeah I'm able to run it at 10ms delay on cdi, but just one instance, looks like it's getting up to 800 games a day 10:37:29 yeah I don't know how much of an issue it is to have 20% more stuff in dbs 12:12:40 03PleasingFungus02 07* 0.29-a0-999-gf35a41adde: Shift Frozen Ramparts damage later (acrobat) 10(3 days ago, 1 file, 2+ 2-) 13https://github.com/crawl/crawl/commit/f35a41adde02 12:12:40 03PleasingFungus02 07* 0.29-a0-1000-g458353e8b9: Display current attack delay in weapon description 10(48 minutes ago, 1 file, 21+ 0-) 13https://github.com/crawl/crawl/commit/458353e8b998 12:12:40 03PleasingFungus02 07* 0.29-a0-1001-g36053be5b9: Decrease deep abyss exit spawn rate (Oneirical) 10(48 minutes ago, 1 file, 3+ 1-) 13https://github.com/crawl/crawl/commit/36053be5b90c 12:12:40 03PleasingFungus02 07* 0.29-a0-1002-g3a827bf7a4: Deduplicate some abyss spawn logic 10(45 minutes ago, 1 file, 10+ 12-) 13https://github.com/crawl/crawl/commit/3a827bf7a410 12:12:40 03PleasingFungus02 07* 0.29-a0-1003-g08a8388b2b: Don't force alligators to always be patrolling 10(44 minutes ago, 1 file, 1+ 3-) 13https://github.com/crawl/crawl/commit/08a8388b2b84 12:12:40 03PleasingFungus02 07* 0.29-a0-1004-g417cb75212: Fix deep abyss spawns 10(30 minutes ago, 1 file, 16+ 19-) 13https://github.com/crawl/crawl/commit/417cb75212a2 12:12:40 03PleasingFungus02 07* 0.29-a0-1005-g6e1c3f9eef: Update more things for deep abyss 10(19 minutes ago, 2 files, 5+ 1-) 13https://github.com/crawl/crawl/commit/6e1c3f9eef95 12:40:48 Unstable branch on crawl.kelbi.org updated to: 0.29-a0-1005-g6e1c3f9eef (34) 14:45:28 03PleasingFungus02 07* 0.29-a0-1006-g0dd7720b37: Fix a Zenata monspeak typo (ebird) 10(47 seconds ago, 1 file, 1+ 1-) 13https://github.com/crawl/crawl/commit/0dd7720b377f 14:55:24 Unstable branch on crawl.kelbi.org updated to: 0.29-a0-1006-g0dd7720b37 (34) 15:07:49 04Build failed for 08master @ 0dd7720b 06https://github.com/crawl/crawl/actions/runs/2806412654 15:23:06 Unstable branch on underhound.eu updated to: 0.29-a0-1006-g0dd7720b37 (34) 15:27:15 <13Sastreii> scythes still exist right? bc i remade finisher (and Jorgrun) 15:27:15 <13Sastreii> https://cdn.discordapp.com/attachments/747522859361894521/1005240592495808623/Schermata_2022-08-06_alle_00.11.09.png 15:27:16 <13Sastreii> https://cdn.discordapp.com/attachments/747522859361894521/1005240592919445514/Finisher_doll.png 15:27:16 <13Sastreii> https://cdn.discordapp.com/attachments/747522859361894521/1005240593338859581/Finisher.png 15:27:17 <13Sastreii> https://cdn.discordapp.com/attachments/747522859361894521/1005240594030932080/Jorgrun.png 15:28:45 <13Sastreii> this was the first concept, but it was too fancy and it got discarded 15:28:46 <13Sastreii> https://cdn.discordapp.com/attachments/747522859361894521/1005240974441717770/Schermata_2022-08-06_alle_00.27.46.png 15:40:10 <10PleasingFungus> ooh 15:40:15 <10PleasingFungus> that is a very sharp finisher 15:40:34 <10PleasingFungus> the red one, not the spooky ghost one 🙂 15:41:10 <10PleasingFungus> assume the ghost ended up looking like a club or blunt weapon when zoomed out? 15:43:50 <08nicolae> i kind of want to make an unrand just to use this tile for it 15:45:41 <10PleasingFungus> crawl is desperately short on scythe unrands. we need more 15:45:50 <10PleasingFungus> [joke] 15:46:15 <13Sastreii> it was just a depiction of the concept “it can instakill you and somewhat extract your soul in the process” But it ended being vaguely comic rather than menacing 15:47:07 <10PleasingFungus> heh heh 15:47:14 <10PleasingFungus> it feels more like an illustration for scythe of curses 18:00:33 <10PleasingFungus> feels like kind of a small release 18:00:36 <09gammafunk> honestly it doesn't affect me much either way, I will have enough time to set up t and hopefully run it 18:00:51 <10PleasingFungus> hm 18:00:56 <09gammafunk> hrm, smaller than last for sure probably, but I guess I'd not call it small 18:01:28 <09gammafunk> the only problem I see is one week from now, according to that schedule, spell has to be properly balanced 18:01:36 <09gammafunk> which doesn't give loads of play testing time 18:01:49 <10PleasingFungus> sure 18:01:52 <09gammafunk> but that schedule is also unusual and I'm not sure we should actually follow it 18:01:58 <10PleasingFungus> well 18:02:08 <10PleasingFungus> (for others' context: continuing a discussion about a new spell i just implemented) 18:02:15 <09gammafunk> we typically just do two weeks of freeze then release then t 18:02:15 <10PleasingFungus> i don't think that's actually what that schedule implies 18:02:24 <10PleasingFungus> i think this is actually very conventional 18:02:29 <10PleasingFungus> it's still two weeks between freeze and release 18:02:45 <10PleasingFungus> the 1 week out event is just us cutting the 0.29 branch, which we traditionally do somewhere in between 18:02:51 <10PleasingFungus> the beta branch, that is 18:02:53 <10PleasingFungus> right? 18:04:08 <10PleasingFungus> re release size: 0.28 had about 1700 commits and 0.29 is coming in at somewhere around 1k 18:04:22 <10PleasingFungus> i forget how to get exact numbers on these, or historical numbers 18:05:45 <09gammafunk> in the past our metric for release was basically 1k commits, yeah 18:05:51 <09gammafunk> but it has certainly fluctuated 18:06:24 <09gammafunk> I think you probably have enough time for your spell, the part that's throwing me off about the schedule is 1w -> then make branch and tag as beta 18:06:31 <09hellmonk> just merge all the vault prs after feature freeze 18:06:40 <09hellmonk> Ez commit padding 18:07:09 <09gammafunk> there is a practical issue with the branch, and that is once hong installs the beta, he doesn't usually update it 18:07:12 <09gammafunk> for cwz 18:07:16 <10PleasingFungus> mm 18:07:37 <09gammafunk> so I guess I'd recommend that we don't try to have beta tagged/branched like two weeks before t 18:07:45 <09gammafunk> but closer to t, one week 18:08:38 <09gammafunk> or I guess we could tag/branch but not ask any admins to install it yet, but that sort of defeats the purpose 18:08:45 <09gammafunk> since the beta must be a new branch 18:08:49 <10PleasingFungus> i don't feel strongly. 18:09:13 <09gammafunk> guess we can always just ask hong to update it closer to t and hopefully he has time, or maybe he just waits until t 18:09:33 <09gammafunk> anyhow, that's the only issue I can see, I'm not too invested either way 18:09:37 <09gammafunk> go with what you feel! 18:09:52 <12ebering> !lg * cwz x=vlong 0.28 18:09:55 <04Cerebot> 15035. [vlong=0.28.0] fionasse the Caller (L1 MfSu), frozen to death by an endoplasm on D:1 on 2022-08-05 18:30:40, with 0 points after 43 turns and 0:00:07. 18:10:03 <12ebering> if you ask hong he'll update it! 18:10:03 <09gammafunk> yeah we got it good last t 18:10:05 <12ebering> we did last time 18:10:13 <09gammafunk> he may update it 18:10:13 <12ebering> just needs a lil poke 18:10:22 <09gammafunk> trust me, I've dealt with this issue for a number of years 18:10:38 <12ebering> I think you are being unfair to hong here and things are better now that we have more regular interaction with several cwz players but ok 18:11:21 <09gammafunk> I mean, it's not being unfair, it's just that he's quite busy and just historically has trouble finding the time. Keep in mind I'm in direct contact with him via email, and we've conversed directly many times 18:12:11 <09gammafunk> anyhow, I'm not super invested in the timing 18:12:56 <12ebering> me neither tbh, got a lot going on around semester start 18:13:23 <12ebering> but the release being a few days before t lets us ask server admins for install after the "release version" is ready 18:13:49 <12ebering> avoiding the cwz issue entirely 18:14:16 <09gammafunk> yes, that is idea, the only part that surprised me was that release was a full week before t 18:14:40 <09gammafunk> we've never actually done that far in advance to my knowledge, but agree that the only sort of tricky issue is what happens between beta and actual release 18:14:49 <09gammafunk> mostly because of cwz 18:15:12 <09gammafunk> the other problem to have is not having the branch available to install except very close to t, but this schedule won't have that problem 18:15:20 <09gammafunk> we have cut it a bit close in the past 22:34:43 Unstable branch on crawl.develz.org updated to: 0.29-a0-1006-g0dd7720b37 (34) 22:55:59 Windows builds of master branch on crawl.develz.org updated to: 0.29-a0-1006-g0dd7720b37 23:18:12 Unstable branch on cbro.berotato.org updated to: 0.29-a0-1006-g0dd7720b37 (34) 23:53:56 Monster database of master branch on crawl.develz.org updated to: 0.29-a0-1006-g0dd7720b37