0007865: Many vault clouds fail to autoexclude - Dungeon Crawl Stone Soup Tracker

Notes
(0024731) Claws (developer) 2013-12-15 04:33	All of those zot vaults have maybe one turn out of eleven that isn't actually blocked by the cloud, and I doubted there was going to be particularly many concerns with auto-exclusions in Abyss or Hells, though I suppose I didn't do much testing with autoexplore/autotravel with said vaults. Plus, I'm not greatly fond of portals having giant blocks of auto-exclusions to prompt through, considering how usually important it is to carefully travel through them anyway. (I am vaguely tempted to have some portals use teleporters back to the start for the times when people leave their consumables at the start of a portal, upon which I'd be fine for said autoexclusion blockades.) I wouldn't mind making most of these exclud_rad = 0 regardless, though, and I'll considering working up a quick patch.

(0024733) KiloByte (manager) 2013-12-15 05:54	Have you researched what excl_rad of -1 and 0 mean? Not knowing what they do is why I haven't refactored/removed/optimized circle_def yet; I'd be happy if someone could tell me that.

(0024734) minmay (reporter) 2013-12-15 08:18	According to dat/dlua/lm_fog.lua, excl_rad of -1 means do not autoexclude clouds from this generator at all, and excl_rad of 0 means autoexclude squares with clouds on them but not the ones around them. So excl_rad of -1 is really only appropriate for clouds that aren't going to appear again (such as volcano eruptions), and terrible on others.

Relationships