00:00:01 Unstable branch on CRAWL.XTAHUA.COM updated to: 0.24-a0-235-g3f03afc (34) 00:01:29 Stable (0.23) branch on CRAWL.XTAHUA.COM updated to: 0.23.1-49-g05433c6 00:52:12 -!- amalloy_ is now known as amalloy 01:37:27 Unstable branch on crawl.develz.org updated to: 0.24-a0-235-g3f03afc (34) 01:52:04 -!- TAS-2012v is now known as TAS_2012v 02:08:21 Windows builds of master branch on crawl.develz.org updated to: 0.24-a0-235-g3f03afc 02:17:11 -!- Tiobot is now known as Guest24414 02:58:36 Monster database of master branch on crawl.develz.org updated to: 0.24-a0-235-g3f03afc 02:58:49 -!- TAS-2012v is now known as TAS_2012v 03:30:45 Stable (0.23) branch on crawl.kelbi.org updated to: 0.23.1-49-g05433c6f1a 04:40:37 -!- amalloy is now known as amalloy_ 04:47:44 -!- amalloy_ is now known as amalloy 11:24:22 Stable (0.23) branch on underhound.eu updated to: 0.23.1-49-g05433c6f1a 13:01:59 Stable (0.23) branch on crawl.akrasiac.org updated to: 0.23.1-49-g05433c6 13:06:57 Unstable branch on crawl.akrasiac.org updated to: 0.24-a0-235-g3f03afc (34) 14:32:14 New branch created: pull/1029 (1 commit) 13https://github.com/crawl/crawl/pull/1029 14:32:14 03NormalPerson702 07https://github.com/crawl/crawl/pull/1029 * 0.24-a0-236-gcecf454: Turn off skill targets when aptitudes change from level up (11943) 10(5 minutes ago, 2 files, 3+ 1-) 13https://github.com/crawl/crawl/commit/cecf454b50d4 16:50:34 is it weird that having immune allies in the path of a (non-penetrating) zap doesn't affect the process of targeting/casting it in any way? 16:50:49 noticed it just now while playing a venom mage of hepli 16:51:46 was surprised for a moment that my zaf macro happily shot stings at my ancestor when there was a gnoll behind them 16:53:42 it might miss the ancestor, of course, so it's not like firing through a plant 16:56:12 and if you do hit the ancestor, it won't damage them 16:57:14 but it still seems a little weird to me that it's just as easy to do something that's usually not going to help you at all 16:58:02 as to do the "normal" thing 16:59:18 a "really fire in your ancestor's direction" prompt would be even weirder because it's not like it would damage them, and the "your path is blocked! fire anyway?" one that's used for plants is overkill too 16:59:34 so i'm not sure what i'd like better 16:59:52 maybe if it just didn't autotarget the gnoll in that situation? 17:01:19 then my zaf macro wouldn't work quite as mindlessly, but if i really wanted to try for the 10% shoot-through-immune-thing play i could do it 17:54:08 -!- fmul is now known as enygmata 18:06:53 advil: I saw that fix you made to rng order in the xom_dancing_weapon lua code, and I wondered if there are many other seed stability bugs like that 18:07:20 Is the kind of ordering in place before you change guaranteed to cause seed problems? 18:08:22 makes me think I might need to check the other tests for unrand availability; there seems to be a couple dozen of them or so 18:38:12 -!- fmul is now known as enygmata 18:57:45 gammafunk: i think anytime you let external state determine whether you should ask for a random number or not, you break seed stability 19:17:10 well I guess I should double-check those calls to you.unrands 20:19:43 -!- MakMorn_ is now known as MakMorn 21:12:23 hrm 21:12:28 so if I understand this correctly 21:12:49 !source vaults_rooms_hard.des:1307 21:13:09 https://github.com/crawl/crawl/blob/master/crawl-ref/source/dat/des/branches/vaults_rooms_hard.des#L1307 21:13:10 shouldn't this cause a problem 21:13:48 since that item statement has a randomized set that is only used if sniper+piercer have generated? 21:16:14 moving the definitions around wouldn't help either, since the item statement doesn't get actual evaluation until vault placement time, I think 23:57:13 Stable (0.23) branch on CRAWL.XTAHUA.COM updated to: 0.23.1-49-g05433c6