00:15:17 <Discord|> <04C​gettys> I'm dubious of the current overloaded of mode and requested duration in general
00:15:59 <Discord|> <04C​gettys> It makes it messy to e.g. make rest's 100 turn wait if already rested configurable
00:45:44 <Gretell> Monster database of master branch on crawl.develz.org updated to: 0.35-a0-52-gbbfe210076
04:13:19 <Lantell> YellowBlue (L20 HuSu) ERROR: range check error (-1 / 70) (Vaults:1)
04:36:23 <Lantell> Experimental (bcrawl) branch on underhound.eu updated to: 0.23-a0-5261-gd9800d219b
07:09:23 -!- The topic of #crawl-dev is: Crawl Development | https://github.com/crawl/crawl | Logs: http://s-z.org/crawl-dev/, temporarily http://crawl.akrasiac.org/logs/cheibriados/ | People with +v have commit access, devs on bridged discord as well | General Crawl-related chat to #crawl | Long stuff to a pastebin service, please
09:47:28 <Discord|> <08o​____0> I think I see now that RMODE_START and CONTINUE are used exclusively for long-walking already
09:47:50 <Discord|> <08o​____0> !crash
09:47:55 <Discord|> <04C​erebot> 22659. LexAckson, XL20 PoMo, T:43580 (milestone): https://crawl.akrasiac.org/rawdata/LexAckson/crash-LexAckson-20260210-162650.txt
09:48:36 <Discord|> <08o​____0> oh that one didn't show up here heh
09:53:59 <geekosaur> usually means a double crash (i.e crashed again during cleanup/reporting)
09:55:21 <Discord|> <04d​racoomega> Well, there are several servers that just don't report crashes here at all
09:55:25 <Discord|> <04d​racoomega> But they can still be fetched with the !crashlog command
09:56:34 <geekosaur> yeh, that was the other thing I was wondering, but I thought Henzell had that ability
09:58:00 <Discord|> <04d​racoomega> So did I
09:58:16 <Discord|> <04d​racoomega> (Though certainly that is a reason that behavior happens a bunch)
09:59:24 <Discord|> <04d​racoomega> In any case, I am going to guess what happened in that crash is that a monster fell down a shaft in LoS during monster catchup
09:59:43 <Discord|> <04d​racoomega> And then it tries to notify the player of noticing the now-dead monster
10:04:05 <Discord|> <04d​racoomega> The crash that actually got reporter here is more cryptic to me, though
10:06:16 <Discord|> <04d​racoomega> Looks like show_update_at() may have been called with an out of bounds coordinate?
10:07:08 <Discord|> <04d​racoomega> Oh!
10:07:21 <Discord|> <04d​racoomega> The player is swapping with an ally that has barbs, and the barbs is killing them mid-swap
10:07:39 <Discord|> <04d​racoomega> So their position is invalid by the time it tries to redraw where they are
10:08:45 <Discord|> <08o​____0> That's really funny
15:54:51 <Discord|> <08o​____0> Ok so that's what I wanted. I still need to go through and clean up things but I'll submit a PR tonight (obviously it will need to wait until after tournament anyway)
15:54:51 <Discord|> <08o​____0> https://cdn.discordapp.com/attachments/747522859361894521/1470915946620391516/cWDCU5T.mp4?ex=698d08b9&is=698bb739&hm=0994ea1e5c036b68d4ce57f993a563a428ad5c0a817726561941ceecabdbcb41&