v50 Steam/Premium information for editors
- v50 information can now be added to pages in the main namespace. v0.47 information can still be found in the DF2014 namespace. See here for more details on the new versioning policy.
- Use this page to report any issues related to the migration.
This notice may be cached—the current version can be found here.
Editing v0.31 Talk:Activity zone
Jump to navigation
Jump to search
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
You are editing a page for an older version of Dwarf Fortress ("Main" is the current version, not "v0.31"). Please make sure you intend to do this. If you are here by mistake, see the current page instead.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
==Flow-stylee activity zones?== | ==Flow-stylee activity zones?== | ||
Does anyone know what this comment in the 0.31.02 changelog at [http://www.bay12games.com/forum/index.php?topic=53505.0] means: | Does anyone know what this comment in the 0.31.02 changelog at [http://www.bay12games.com/forum/index.php?topic=53505.0] means: | ||
Line 17: | Line 6: | ||
--[[User:Altaree|Altaree]] 14:12, 9 April 2010 (UTC) | --[[User:Altaree|Altaree]] 14:12, 9 April 2010 (UTC) | ||
:When you are at the activity zone definition/selection state (right after hitting the Zones key from the main menu), you will see a key listed as "rectangle" (default "e") on the menu. Pressing that key toggles between three zone creation states: "rectangle" (the default, you set one corner of a rectangle and then the other), "flow" (you select a location and the area is "filled" with the activity zone, just like defining a room, and can be expanded and contracted the same way), and "floor flow" (not sure what the difference between it and "flow" is, anyone else done any testing?). I'm guessing zones don't become a simple property of the map squares where you defined the zone, like stock(p)iles and (d)esignations do. Instead the way you defined the zone is saved, and the area it occupies is re-calculated with every frame, after the zone menu is closed and play resumes. So a "flow-style" activity zone would be one that was originally defined using the "flow" method, and a large one could cause a performance hit at least, simply because its borders need to be recalculated from the definition every frame, which can get pretty complicated for some convoluted fortress designs. --[[Special:Contributions/66.190.120.90|66.190.120.90]] 15:45, 1 May 2010 (UTC) | :When you are at the activity zone definition/selection state (right after hitting the Zones key from the main menu), you will see a key listed as "rectangle" (default "e") on the menu. Pressing that key toggles between three zone creation states: "rectangle" (the default, you set one corner of a rectangle and then the other), "flow" (you select a location and the area is "filled" with the activity zone, just like defining a room, and can be expanded and contracted the same way), and "floor flow" (not sure what the difference between it and "flow" is, anyone else done any testing?). I'm guessing zones don't become a simple property of the map squares where you defined the zone, like stock(p)iles and (d)esignations do. Instead the way you defined the zone is saved, and the area it occupies is re-calculated with every frame, after the zone menu is closed and play resumes. So a "flow-style" activity zone would be one that was originally defined using the "flow" method, and a large one could cause a performance hit at least, simply because its borders need to be recalculated from the definition every frame, which can get pretty complicated for some convoluted fortress designs. --[[Special:Contributions/66.190.120.90|66.190.120.90]] 15:45, 1 May 2010 (UTC) | ||
− | |||
::Flow will include but not pass through walls, floor flow will not include walls. I've had this crash several times, glad it's fixed. [[User:Mason11987|Mason]] <sup>([[User talk:Mason11987|T]]-[[Special:Contributions/Mason11987|C]])</sup> 11:52, 24 May 2010 (UTC) | ::Flow will include but not pass through walls, floor flow will not include walls. I've had this crash several times, glad it's fixed. [[User:Mason11987|Mason]] <sup>([[User talk:Mason11987|T]]-[[Special:Contributions/Mason11987|C]])</sup> 11:52, 24 May 2010 (UTC) | ||
Line 33: | Line 21: | ||
Dwarves will also frequently drop food while carrying it somewhere to eat, and it can never be moved again if this happens. Apparently something in the ownership tags gets screwed up, so the food ends up owned by a null "nobody" dwarf that prevents removal of the food by any dwarf, including the one that dropped the food. My trade depot is currently full of miasma due to these unmovable dropped meals. Turning off all jobs except "refuse hauling" only leaves the dwarves that own the food standing around with "No Job." --[[User:Tatterdemalian|Tatterdemalian]] 03:10, 24 May 2010 (UTC) | Dwarves will also frequently drop food while carrying it somewhere to eat, and it can never be moved again if this happens. Apparently something in the ownership tags gets screwed up, so the food ends up owned by a null "nobody" dwarf that prevents removal of the food by any dwarf, including the one that dropped the food. My trade depot is currently full of miasma due to these unmovable dropped meals. Turning off all jobs except "refuse hauling" only leaves the dwarves that own the food standing around with "No Job." --[[User:Tatterdemalian|Tatterdemalian]] 03:10, 24 May 2010 (UTC) | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |