00:03:52 <floraline> all in all this has been a way bigger task than i thought it was at first, even having understood that it was going to be more work than what is laid out in the wiki
00:05:19 <floraline> i'm no sysadmin or else this would be way easier
00:06:26 <alexjurkiewicz> :)
00:06:58 <alexjurkiewicz> being a sysadmin is the only reason I managed to get CPO running
00:07:05 <alexjurkiewicz> soo many little weird issues
00:07:51 <alexjurkiewicz> it's impressive how well it all works considering it's been built by a million people over 20 years
00:08:46 <floraline> oh yes for sure
00:09:04 <floraline> and the wiki has been infinitely helpful even if it isn't complete
00:18:19 -!- Rast- is now known as Rast
00:23:14 <johnstein> !tell buppy experimentals shouldn't be a huge issue so long as there's a stable branch I can point to or some PR in the crawl repo. devil's in the details but generally the only holdup is me carving out time to do it :)
00:23:14 <Sequell> johnstein: OK, I'll let buppy know.
00:23:38 <johnstein> gammafunk, |amethyst, I moved pretty much everything except 0.21 and 0.22 games last night.
00:23:41 <johnstein> ^status
00:23:41 <Rotatell> 28 Crawlers. CBRO disk usage=68% (135GB) | RAM usage=24% (4GB)| uptime/CPU= 00:23:40 up 165 days,  3:59,  5 users,  load average: 0.74, 0.86, 0.90 (4 Cores) http://status.berotato.org
00:23:51 <gammafunk> johnstein: nice!
00:23:52 <johnstein> should be good for a few days at least
00:24:38 <johnstein> and I made Good Notes for myself to migrate the old games when doing setup for the new version. so when we open 0.23, I'll transfer 0.21
00:24:57 <johnstein> seems like maybe that's not a huge deal
00:26:04 <gammafunk> johnstein: did those games just get transfered to 0.22 trunk?
00:26:15 <gammafunk> You were saying you weren't going to do the per-version trunk transfer
00:27:08 <johnstein> I transferred each version to the most recent install I actually had for that version
00:27:16 <johnstein> I have no clue if that breaks anything
00:27:37 <johnstein> but I think the chances that the version I transferred to is broken should be low
00:28:01 <johnstein> I suppose I could check out each one in retrospect
00:28:43 <johnstein> %git 5545dd3
00:28:43 <Cheibriados> 07Grunt02 * 0.14-a0-3499-g5545dd3: Fix arc blade discharge behaviour. 10(4 years, 3 months ago, 1 file, 12+ 1-) 13https://github.com/crawl/crawl/commit/5545dd3c9da8
00:29:01 <johnstein> %git 0.14-b1~1
00:29:01 <Cheibriados> 07Grunt02 * 0.14-a0-3618-g3331d8b: Purge an extraneous bit from dc-mon.txt. 10(4 years, 3 months ago, 1 file, 0+ 2-) 13https://github.com/crawl/crawl/commit/3331d8b85e77
00:29:06 <johnstein> sorta close
00:29:37 <johnstein> %git 54a05ab
00:29:37 <Cheibriados> 07PleasingFungus02 * 0.15-a0-2393-g54a05ab: Add greatsling tiles (roctavian) 10(3 years, 11 months ago, 3 files, 1+ 0-) 13https://github.com/crawl/crawl/commit/54a05abb729b
00:29:51 <johnstein> %git 0.15-b1~1
00:29:51 <Cheibriados> 07PleasingFungus02 * 0.15-a0-2403-g91670f7: Remove Gozag from the changelog 10(3 years, 11 months ago, 1 file, 14+ 27-) 13https://github.com/crawl/crawl/commit/91670f780909
00:47:44 <ProzacElf> johnstein: i've been getting some really bad pings from cbro the last few days.  although the problem might be on my end
00:54:15 <johnstein> I haven't gotten anything from Ramnode. I'll double check my emails
03:34:11 -!- amalloy is now known as amalloy_
13:07:20 -!- amalloy_ is now known as amalloy
13:50:50 <ebering> gammafunk: is pr 757 still on your radar? I know spooky_vaults and datafiles have been pretty big pending merges so I'm guessing there's a backlog
13:54:06 <gammafunk> is that the abyss thing? if so, yes, and yeah there are a couple others to deal with
13:55:27 <ebering> yes
13:56:22 <muffindrake1> Is there something preventing pr 771 from being merged?
13:56:32 <muffindrake1> It contains a trivial improvement that remove duplicate code
13:56:45 <muffindrake1> budget s key
13:58:32 <gammafunk> not looking at the contents I would force push commit titles that begin with capitalization and change the commit title of the '!!!' one to something meaningful
13:59:00 <muffindrake1> I will reset those commits and submit as a single one, then
13:59:09 <floraline> wait we're not supposed to use capitals?
13:59:09 <gammafunk> sure, that would be fine
13:59:36 <gammafunk> floraline: I was saying that one should use capitalization
13:59:45 <floraline> oh i misread that
13:59:46 <gammafunk> but I can see how it would be interpreted in the opposite way :)
14:00:33 <floraline> i actually wanted to rebase some of my first commits in my PR because they are in poor form, but i was scared that i would break everything
14:01:03 <gammafunk> no, it's generally safe to force-push new ones
14:01:25 <gammafunk> the only issue is if someone else is working on the branch with you, but that's usually not the case for a PR
14:01:30 <floraline> i was trying to figure out how to use rebase to just change commit messages, but it looked like having merges in there made it complicated
14:01:50 <gammafunk> oh, yeah, you can just rebase -i relative to your current branch
14:01:57 <gammafunk> the one the PR is based on
14:02:07 <gammafunk> don't rebase relative to e.g. upstream/master
14:02:14 <gammafunk> where upstream is the official crawl repo
14:02:51 <gammafunk> just do an interactive rebase relative to the existing branch of the PR, edit the commit messages (or even the commits themselves if you want to make changes)
14:02:52 <floraline> i was reading that the rebase would like, try to re-apply the merges somehow
14:02:54 <gammafunk> and force push that
14:03:10 <gammafunk> oh, you have merge commits in your branch?
14:03:16 <floraline> i merged master into my branch
14:03:20 <floraline> like 3 or 4 times
14:03:34 <floraline> is that not standard practice?
14:03:40 <gammafunk> ok, honestly you can just rebase the entire branch to upstream/master and that would be fine
14:03:48 <gammafunk> I think you can have that interactive rebase retain the merges though
14:04:01 <amalloy> i wouldn't bother trying to keep the merges
14:04:06 <gammafunk> right
14:04:16 <gammafunk> we will probably just rebase those out ourself
14:04:35 <gammafunk> ourselves
14:04:37 <floraline> oh
14:04:39 <gammafunk> for we are not one
14:04:43 <muffindrake1> gammafunk: done
14:05:03 <floraline> i merged every time github said there was an auto merge conflict
14:05:08 <gammafunk> I will take a look but as I said to ebering there are a couple other things higher up in the queue
14:05:21 <gammafunk> if another dev wants to merge that though, they certainly could
14:05:50 <gammafunk> assuming it has no other issues
14:05:50 <floraline> is it generally recommended then that working branches shouldn't be merging master to resolve conflicts ahead of time?
14:06:30 <gammafunk> it seems fine to me; like I said, we're probably just going to rebase it at the end and your conflict resolution should be retained
14:06:38 <gammafunk> maybe someone has a different opinion though
14:06:57 <gammafunk> but I think we don't expect people to keep merging master regularly either
14:07:12 <gammafunk> if you're making new commits that's maybe a good idea
14:07:34 <floraline> i saw it as a way to help prevent the branch from getting stale
14:07:57 <Cheibriados> 03Muffindrake02 07https://github.com/crawl/crawl/pull/771 * 0.22-a0-442-g5e4a819: Remove duplicate code for attack punctuation - put the punctuation code into a function and remove exact duplicate used in a different part of the code base 10(6 minutes ago, 3 files, 6+ 27-) 13https://github.com/crawl/crawl/commit/5e4a81948d63
14:08:01 <gammafunk> yeah, for only that purpose I don't think it's necessary
14:08:01 <floraline> if it's always up to date, or at least no auto merge conflicts, then it can be merged at any time with no work
14:08:54 <gammafunk> it's probably better to just work with the dev person you've been working with to resolve any issues, and that can go slowly
14:09:56 <amalloy> however you manage your local branch is fine. personally i prefer to do it with rebases than with merges most of the time, but it's not a huge deal either way
14:11:26 <amalloy> resolving the conflicts yourself proactively will indeed make it easier for someone to come by and drive it, so that's appreciated but i think most people don't bother with that
14:11:29 <amalloy> *merge it
14:12:06 <gammafunk> most of us don't have licenses to drive pull requests
14:13:26 <Cheibriados> 03Muffindrake02 {amalloy} 07* 0.22-a0-526-g6e5688e: Remove duplicate code for attack punctuation (#771) 10(13 seconds ago, 3 files, 6+ 27-) 13https://github.com/crawl/crawl/commit/6e5688e9ae14
14:13:46 <ebering> when pf and wheals were merging my patches a few years ago they expected that I'd rebase relative to upstream/master when the details had been hammered out
14:14:04 <ebering> so that the changes could apply cleanly
14:15:26 <floraline> is it common to get rid of all the commits in PR771 like muffindrake just did? is that what squashing is
14:15:54 <muffindrake1> gammafunk said he wanted meaningful commit messages and some of them weren't
14:16:16 <muffindrake1> so I reset the branch and re-committed as a single one because it's small
14:16:17 <floraline> oh, but if they were already meaningful you wouldn't do that just to merge it
14:16:49 <gammafunk> it's fine to have individual commits if the changes are independent enough, yeah just want commit messages to be meaningful
14:17:02 <advil> contributing to the backlog, I'm on various combinations of vacation / work traveling for the last two weeks through the next two weeks, so that's why I haven't managed to have any time to look at PRs, normally I would've merged/commented on some of the current ones
14:17:36 <floraline> the git workflow is new to me, i'm coming from an SCM background which is pretty different from git branches
14:17:55 <muffindrake1> the dark ages?
14:18:22 <floraline> haha what SCM? pretty much
14:19:02 <gammafunk> hey, git is an SCM!
14:19:21 <muffindrake1> Has revision control for source code been solved with git, much in the same way that email is a solved problem now?
14:19:53 <floraline> oh sorry i mean Surround SCM
14:19:58 <floraline> which i think is owned by perforce now
14:20:00 <advil> lots of people love to hate git
14:20:26 <gammafunk> https://git-man-page-generator.lokaltog.net/
14:20:39 <floraline> can you do a sideways merge in git between two branches with different parents?
14:20:39 * geekosaur was considering clearcase >.> speaking of pretty different from...
14:20:39 * Sequell also was considering clearcase >.> speaking of pretty different from...
14:20:48 <muffindrake1> floraline: I understood you perfectly and my sentence sees git as the successor of anything primordial you have been working on
14:22:13 <gammafunk> floraline: yes, you can merge any two branches; they ultimately will share a common ancestor since they're in the same repo
14:23:15 <floraline> that's the number one thing that kills us with SCM
14:23:29 <floraline> you can't do a sideways merge so we end up losing most of our commit history
14:23:51 <floraline> we just have to copy the changes from one branch into the other and commit everything at once, then the original branch is deleted
14:34:09 <amalloy> gammafunk: in practice what you say is true, but in principle it doesn't have to be. a repo can have multiple distinct root commits
14:34:42 <amalloy> eg github stores its wikis in the disconnected branch "gh-pages"
14:34:42 <ebering> gammafunk: what's your opinion of a jorgrun statue grove ghost vault?
14:34:42 -!- panicbit3 is now known as panicibt
14:34:45 -!- panicibt is now known as panicbit
14:35:12 <ebering> erm
14:35:14 <ebering> statue garden
14:38:42 <gammafunk> amalloy: Oh, I didn't realize that could be the case.
14:38:57 <gammafunk> ebering: a ghost vault that places jorgrun?
14:39:16 <gammafunk> Jorgrun is sort of on the chopping block right now, so that particular unique is probably not the best one to use
14:39:25 <amalloy> gammafunk: well if you remove him he'll be dead. a ghost, if you will
14:39:58 <gammafunk> if we remove him, it's like he never existed
14:40:15 <gammafunk> ebering: if you wanted to go for a petrification themed vault in general, like catobles, maybe that would be a good one
14:40:20 <geekosaur> put him in the fallback ghosts :p
14:40:31 <gammafunk> do any other monsters have petrify spell?
14:42:28 <gammafunk> There isn't yet a ghost vault that places a unique, which there could be; we tend to note directly place them in vaults very often, probably just to reduce bias in unique placement, but a few such vaults wouldn't hurt
14:42:47 <gammafunk> however if you're mostly interested in the statue garden idea, maybe just a catoble vault would be good
14:43:08 <gammafunk> something vaguely similar to the lair ending, just much much smaller probably
14:43:59 <gammafunk> I want to make a spreadsheet of unique/place
14:44:03 <gammafunk> and see what the dist looks like
14:44:32 <ebering> i'm gonna form the committee for the preservation of jorgrun ;)
14:44:33 <gammafunk> MarvinPA has commented how there are too many uniques at the depth where jorgrun places, it would be neat to see the numbers
14:44:46 <geekosaur> in formaldehyde?
14:44:53 <gammafunk> well, he was brought into existence to give a monster a level 9 spell that isn't very good on monsters
14:45:22 <gammafunk> I guess you would sort of have to preserve his idea without the silly one-shotting, maybe some new kind of spell
14:45:25 <muffindrake1> -jorgrun +norris
14:45:31 <gammafunk> it would probably also help if you adjusted where he generated
14:45:42 <muffindrake1> fr: give norris damnation
14:45:48 <gammafunk> I'm not sure where we are lightest on uniques, hence my interest in said spreadsheet
14:46:21 <gammafunk> jorgrun the unique killer klown
14:46:37 <gammafunk> he petrifies you with terrible jokes
14:46:46 <muffindrake1> fr: give norris fire storm
14:47:41 <ebering> yeah, I'm aware of the issues with jorgrun, but his petrify+shatter combo is pretty iconic and seems like a good theme for a ghost vault
14:48:02 <ebering> do dtems try to LRD a petrified player?
14:50:33 <gammafunk> yes
14:50:51 <gammafunk> @?deep troll earth mage
14:50:54 <Gretell> deep troll earth mage (06T) | Spd: 10 | HD: 12 | HP: 39-57 | AC/EV: 12/10 | Dam: 27, 2009(claw), 2009(claw) | 10doors, spellcaster, see invisible | Res: 06magic(40), 08blind | XP: 858 | Sp: rapid deconstruction, dig | Sz: Large | Int: human.
14:51:00 <gammafunk> ah, no petrify
14:52:14 <ebering> ya
14:55:28 <ebering> @?catoblepas
14:55:28 <Gretell> catoblepas (06Y) | Spd: 10 | HD: 14 | HP: 61-91 | AC/EV: 10/2 | Dam: 36 | Res: 06magic(100) | XP: 937 | Sp: petrifying cloud (2d6) [11!AM, 06!sil] | Sz: Big | Int: animal.
14:56:01 <ebering> wow these are tougher than dtem?
14:56:25 <muffindrake1> @?yak
14:56:25 <Gretell> yak (07Y) | Spd: 10 | HD: 7 | HP: 30-45 | AC/EV: 4/7 | Dam: 18 | Res: 06magic(20) | XP: 204 | Sz: Large | Int: animal.
14:56:43 <muffindrake1> They are two yaks in one
14:56:55 <muffindrake1> 2 yak units in HP and 2 yak units in damage
14:57:09 <gammafunk> yeah, fairly comparable, but dtem can hit you with lrd from nearly anywhere
14:57:11 <geekosaur> not to mention one pinning you while the other gores you >.>
14:57:15 <gammafunk> they also come in a band with other deep trolls
14:57:40 <gammafunk> and dtem will dig out your favorable terrain on top of things
14:58:50 -!- muffindrake1 is now known as muffindrake
15:09:57 <Jorgrell> Unstable branch on crawl.jorgrun.rocks updated to: 0.22-a0-526-g6e5688e9ae (34)
15:17:46 <Cheibriados> 03Nikolai Lavsky02 07* 0.22-a0-457-g49d386f: Fix Injury Bond description 10(2 weeks ago, 1 file, 2+ 2-) 13https://github.com/crawl/crawl/commit/49d386fb4453
15:17:46 <Cheibriados> 03MarvinPA02 {GitHub} 07* 0.22-a0-528-gb6040eb: Merge pull request #776 from nlavsky/injury-bond-description 10(8 seconds ago, 0 files, 0+ 0-) 13https://github.com/crawl/crawl/commit/b6040ebe653d
15:18:51 <gammafunk> github merge button PogChamp
15:20:42 <advil> shatter in a ghost vault isn't very consistent with the idea of making ghost interactions a player choice
15:22:31 <|amethyst> will monsters cast shatter when their only enemies are behind glass?
15:23:11 <Cheibriados> 03Muffindrake02 07https://github.com/crawl/crawl/pull/761 * 0.22-a0-420-g9a10834: Add a few stab messages for blobs The default stab messages don't work so well with blobs, these ones attempt to poke fun at jellies with food imagery. 10(9 minutes ago, 1 file, 13+ 0-) 13https://github.com/crawl/crawl/commit/9a108342a90f
15:23:14 <ebering> I thought the answer was no which is why I thought the concept was viable
15:23:15 <|amethyst> because it seems like the loop in mon_shatter will stop at solid features if actual == false
15:24:15 <|amethyst> muffindrake:  need an empty line after the subject of the commit message
15:24:26 <amalloy> if they do that's a bug imo. walls are supposed to prevent interaction
15:25:15 <muffindrake> sigh
15:25:47 <gammafunk> someone got their commit message lines all into one big blob
15:27:07 <amalloy> muffindrake: if you tire of getting commit message suggestions, i recommend https://chris.beams.io/posts/git-commit/
15:27:45 <floraline> hey that's exactly the document i read on commit messages
15:27:51 <amalloy> it's a very popular one
15:27:58 <floraline> is the subject line really limited to 50 characters? github seems to be okay with more
15:28:36 <amalloy> floraline: there's no technical limit. but github very thoughtfully uses large font for the subject line, to discourage writing too many characters
15:28:51 <Cheibriados> 03Nikolai Lavsky02 07* 0.22-a0-459-gc254099: Make Iron Giants and other Throw Ally users obey Sanctuary 10(13 days ago, 1 file, 1+ 1-) 13https://github.com/crawl/crawl/commit/c254099d7c5f
15:28:51 <Cheibriados> 03MarvinPA02 {GitHub} 07* 0.22-a0-530-gd75db79: Merge pull request #777 from nlavsky/throw-ally-fix 10(11 seconds ago, 0 files, 0+ 0-) 13https://github.com/crawl/crawl/commit/d75db7994b5e
15:29:03 <muffindrake> amalloy: It would be helpful if those painstaking intricacies of "commit messages for the crawl repo" were written down somewhere
15:29:08 <floraline> the main thing i keep screwing up in my commit messages is doing "fixes" or "fixed" instead of "fix"
15:29:38 <floraline> and of course my other projects use "fixes" so i am never going to get this right
15:29:52 <amalloy> muffindrake: do we have commit message rules that differ from the ones in the document i linked? i think our rules are just the usual ones
15:30:16 <muffindrake> "usual"
15:30:28 <amalloy> floraline: quit your other projects and work on crawl full-time. it's the only answer
15:30:53 <floraline> that depends on how much crawl pays
15:31:03 <amalloy> we'll triple what we're paying you now
15:31:20 <floraline> LOL that's very enticing!!
15:31:24 <floraline> triple is a big number
15:31:35 <amalloy> muffindrake: the document i linked really is the standard. it is what is returned by google searches on how to write commit messages. it's the style of the linux kernel, afaik, as well as many other projects
15:33:24 <ebering> it could be put in docs/develop though!
15:33:30 <ebering> or referenced
15:33:33 <gammafunk> 4. Do not end the subject line with a period
15:33:35 <amalloy> sure
15:33:37 <gammafunk> finally, I am vindicated
15:34:16 <Cheibriados> 03Muffindrake02 07https://github.com/crawl/crawl/pull/761 * 0.22-a0-420-gf36c84e: Add a few stab messages for blobs 10(5 minutes ago, 1 file, 13+ 0-) 13https://github.com/crawl/crawl/commit/f36c84e8e130
15:34:20 <wheals> that's the only line we need to change to make a crawl style guide
15:34:20 <amalloy> ebering: a commit adding that reference will be the one and only time i encourage creating a bad commit message
15:34:22 <floraline> NO periods! i'll fight you
15:35:38 <gammafunk> your kind can never win, floraline
15:36:19 <gammafunk> The weight of your sentence punctuation will drag you to your doom
15:36:31 <muffindrake> Fixed a bug!!!!!!!!!
15:36:49 <gammafunk> grunt_commit_lang
15:37:25 <advil> re commit titles, the full advice in that post is "shoot for 50 characters, but consider 72 the hard limit."
15:37:38 <muffindrake> vim wraps at 72 by default
15:37:47 <advil> which is much more reasonable than a 50 char limit imo
15:37:48 <muffindrake> specifically for commits
15:37:50 <gammafunk> yeah, that's one I see recommended a lot, 50 for the commit title
15:38:00 <muffindrake> commit bodies*
15:38:13 <gammafunk> 50 is pretty tough to stick to due to trying to credit people and bug reports
15:38:22 <gammafunk> I guess said credit could be moved to the commit body
15:38:38 <gammafunk> but that's one example of where we do diverge from that standard
15:39:14 <Cheibriados> 03MarvinPA02 07* 0.22-a0-531-gbf3ec1f: Add nlavsky to CREDITS.txt 10(2 minutes ago, 1 file, 1+ 0-) 13https://github.com/crawl/crawl/commit/bf3ec1f414eb
15:39:23 <Cheibriados> 03Muffindrake02 07https://github.com/crawl/crawl/pull/790 * 0.22-a0-513-ga1d4054: Add lightning-themed vault 10(7 minutes ago, 1 file, 54+ 0-) 13https://github.com/crawl/crawl/commit/a1d40548de89
15:40:00 -!- MarvinPA__ is now known as MarvinPA
15:41:30 <amalloy> yeah, it's nice to have credit in the title since that's what gets reported to ##crawl
15:45:28 <muffindrake> Ah, that branch will definitely conflict, that's too bad
15:45:34 <muffindrake> I'll just make a new PR and branch then
15:46:07 <muffindrake> unless the merger (if any) doesn't mind resolving that conflict
15:47:43 <gammafunk> I need to do some work/testing on the vault before it could merged anyhow, so it's fine
15:49:08 <gammafunk> for anyone working on those ghost vaults, we probably mostly need ones for early dungeon (so at least able to place D:3-8, and it's fine if it can place in additional places)
15:52:16 <floraline> what do you mean credit in commit titles? isn't the 'credit' of who worked on it in the commit history?
15:52:42 <amalloy> floraline: we often credit bug reporters
15:53:39 <amalloy> %git 11ed031617a06b59
15:53:39 <Cheibriados> 07gammafunk02 * 0.22-a0-456-g11ed031: Fix glyph usage in two temple entrances (Reeces) 10(2 weeks ago, 1 file, 6+ 6-) 13https://github.com/crawl/crawl/commit/11ed031617a0
15:54:27 <gammafunk> yeah, Reeces didn't make a commit, just reported the error to me (in that case multiple times over many months before I finally fixed it)
16:03:25 <floraline> oh
16:05:05 <|amethyst> often it's more than just a report too
16:05:56 <|amethyst> someone will say "shouldn't that be != instead of ==" or "if you made foos not frob bars, this wouldn't come up"
16:09:22 <travis-ci> The build has errored. (master - b6040eb #9816 : Chris Campbell): https://travis-ci.org/crawl/crawl/builds/395173132
16:10:01 <Jorgrell> Unstable branch on crawl.jorgrun.rocks updated to: 0.22-a0-531-gbf3ec1f414 (34)
16:24:35 <muffindrake> unrelated to crawl, but this comment in a different github repository, which is a fork of a program that went proprietary for bogus reasons, just wrecked me
16:24:39 <muffindrake> https://github.com/LibreSprite/LibreSprite/issues/1#issuecomment-244792551
16:25:07 <muffindrake> That's the creator of that previously-free-software program talking
16:27:00 <muffindrake> We must make crawl proprietary to reduce CO2 emissions, guys.
16:28:28 <geekosaur> completely ignoring that pretty much all free software cadges spare cycles that would be generating heat anyway
16:34:28 <floraline> is crawl contributing to the heat death of the universe? that's bad press
16:34:58 <muffindrake> NEWS FLASH: computers generate heat! more at 11
17:52:11 <Cheibriados> 03gammafunk02 07* 0.22-a0-532-gcd2a3d9: Bug fixes and code generalizations for gammafunk_ghost_hdyra_chop 10(64 minutes ago, 1 file, 52+ 41-) 13https://github.com/crawl/crawl/commit/cd2a3d91711c
17:52:11 <Cheibriados> 03gammafunk02 07* 0.22-a0-533-g4d20840: An orcish armoury ghost vault for Dungeon and Orc (Biasface) 10(57 minutes ago, 1 file, 81+ 0-) 13https://github.com/crawl/crawl/commit/4d20840e7c64
17:59:26 -!- yesno_ is now known as yesno
18:10:00 <Jorgrell> Unstable branch on crawl.jorgrun.rocks updated to: 0.22-a0-533-g4d20840e7c (34)
18:21:26 <Lantell> Unstable branch on underhound.eu updated to: 0.22-a0-533-g4d20840e7c (34)
18:33:27 <Rotatell> Barfbag (L2 MfGl) Crash caused by signal #15: Terminated (D:1)
19:13:24 <Henzell> runemage (L25 GnFi) Crash caused by signal #11: Segmentation fault (Lair:1)
20:40:12 -!- amalloy is now known as amalloy_
21:05:21 <ebering> gammafunk: ebering_ghost_inner_flame isn't ORIENT:float but all the other ghost vaults are
21:06:13 <gammafunk> that doesn't matter too much, actually; not having it be float means it's a minivault
21:06:29 <gammafunk> I think the reason it is that way is because you didn't add the orient in your commit
21:06:54 <gammafunk> it being a minivault would normally change its distribution of usage
21:07:01 <ebering> yeah, a pure oversight on my part. I guess, should ghost vaults be minivaults?
21:07:02 <gammafunk> but due to ghost vault placement this shouldn't matter
21:07:06 <ebering> oh, ok
21:07:22 <gammafunk> it's a good question, honestly
21:07:47 <gammafunk> probably there are some successfuly placement benefits to it being a minivault but I'm not sure
21:08:22 <ebering> well it hasn't killed anyone yet
21:08:53 <gammafunk> yeah, it's a fairly light threat and 89 can roll nothing fairly often, or just typical level monster
21:09:09 <gammafunk> ebering: not sure if you can run mapstat, but that would verify that it's placing
21:09:35 <ebering> I probably can somehwere, but not too worried about running it asap
21:09:52 <gammafunk> sometimes the monster can die in that vault btw
21:10:03 <gammafunk> not a lot we can do about it, and hopefully it doesn't happen a lot
21:10:25 <ebering> yeah, I thought about crafting a fire-immune monster set for it
21:10:30 <gammafunk> just due to player waking the monster up and it wandering
21:10:35 <ebering> for theme plus also avoiding that issue
21:10:42 <gammafunk> certainly could, yeah
21:10:53 <ebering> but that would probably drag down its depth
21:11:22 <gammafunk> drag down?
21:11:55 <gammafunk> it's trickier to choose the right set of fire monsters for a given depth, it's true
21:12:02 <ebering> I can't think of any appropriate fire immune D:3 monsters... yeah
21:12:03 <gammafunk> *fire monster
21:12:12 <gammafunk> !vault gammafunk_cloud_chamber
21:12:12 <Sequell> 1/1. https://github.com/crawl/crawl/blob/master/crawl-ref/source/dat/des/variable/float.des#L4393
21:12:38 <gammafunk> that has an increasing fire set that works fairly well in flame clouds
21:12:52 <gammafunk> you'd probably have to make the vault a little bigger as it's a little tough to make an appropriate threat if you can only place one monster
21:13:00 <gammafunk> but you could try with just one
21:13:05 <gammafunk> or you could just leave it as it is
21:14:31 <gammafunk> !seen nicolae
21:14:31 <Sequell> Sorry gammafunk, I haven't seen nicolae.
21:14:34 <gammafunk> hmm
21:14:51 <gammafunk> !seen nicolae-
21:14:51 <Sequell> I last saw nicolae- at Tue Apr  3 03:22:19 2018 UTC (11w 2d 21h 52m 31s ago) parting ##crawl-dev, saying 'chanpart'.
21:14:53 <gammafunk> ah
21:15:00 <gammafunk> too bad he's not around any more
21:15:07 <gammafunk> he'd probably like making some of these
21:15:43 <ebering> send an email
21:15:47 <ebering> see what happens
21:15:50 <ebering> 11w isnt long
21:16:17 <gammafunk> oh it's nbd, we actually have a lot of contributors
21:16:40 <gammafunk> I have a few more to make, a couple more submissions that need editing, and at least one other person saying they'll make some
21:16:58 <gammafunk> that person loves new and interesting food costs, especially spell hunger, so I'm not sure if I can trust them though
21:17:14 <gammafunk> dang, he's not in this channel, so that trolling won't work
21:17:28 <ebering> yeah but maybe he'll put another easter-egg submission up
21:18:13 <gammafunk> I will rigously vet all nicolae submissions for any easter eggs
21:18:23 <gammafunk> fool me once, shame on you...
21:21:31 <ebering> there's no way to get the ghost's name in dlua is there?
21:21:56 <gammafunk> no, not presently
21:22:26 <gammafunk> that might be a neat thing to add I guess
21:36:12 <floraline> the webtiles 100% cpu thing only happened once today but i'm still concerned
21:36:22 <floraline> and webtiles log is showing a lot of random exceptions throughought the day with no activity
21:37:23 <floraline> does anyone know if there are actually any servers using the built in tornado support for SSL?
21:40:13 <gammafunk> floraline: yes cue, cjr, and cpo all do
21:41:48 <floraline> to my knowledge CPO uses an ssl-termination proxy
21:42:23 <gammafunk> oh yeah, that may be the case
21:42:36 <gammafunk> and I'm not sure of the details of cue's ssl setup
21:42:52 <gammafunk> floraline: You can ask TZer0, the cue admin, about that
21:43:05 <gammafunk> he's in this channel, but also has contact info on the cue lobby I think
21:44:32 <floraline> ok thank you i'll get in contact with him
22:01:37 <alexjurkiewicz> yeah, CPO uses nginx and webtiles-changes
22:02:23 <alexjurkiewicz> gammafunk: I think ghost vaults should only appear once per game, I got a glass both with transporter in/out twice in my current game
22:04:03 <alexjurkiewicz> !seen zibudo
22:04:04 <Sequell> I last saw ZiBuDo at Fri Feb  9 03:35:30 2018 UTC (18w 6d 22h 28m 33s ago) quitting, saying 'Ping timeout: 256 seconds'.
22:04:11 <alexjurkiewicz> that's the cjr admin ^
22:06:29 <ebering> @?gargoyle
22:06:29 <Gretell> gargoyle (159) | Spd: 10 | HD: 6 | HP: 23-32 | AC/EV: 18/6 | Dam: 20 | 11non-living, 10items, 10doors, fly, unbreathing | Res: 06magic(40), 10elec, 09poison+++, 12drown, 04rot+++, 13neg+++, 13torm | XP: 416 | Sp: stone arrow (3d12) [11!AM, 06!sil] | Sz: Medium | Int: human.
22:07:17 <alexjurkiewicz> interesting spam https://crawl.develz.org/tavern/viewtopic.php?f=8&t=25452&view=unread#unread
22:18:06 <gammafunk> yeah, some of the simplest ones should be allow_dup, but it's true that we don't really need this for other
22:18:24 <gammafunk> there are actually two different ghost transporter vaults that have glass though
22:18:44 <gammafunk> those are in fact the only two ghost transporter vaults
22:19:48 <gammafunk> eventually we'll have good enough coverage that it won't be an issue, but I think we'll leave allow_dup at least for now; I will definitely take a look at that before release, after we have a final set
22:23:15 -!- lobata_ is now known as lobata
22:36:28 <floraline> it looks like there's an issue in tornado where you can trigger many exceptions by reloading the lobby very quickly
22:36:35 <floraline> is this known / solved anywhere? or maybe just me
23:07:25 <floraline> yes this is definitely an issue with the http-timeouts-2.4 branch suggested by the wiki