From 4efb01142913d5f1d72878e8bb409f6353443b6d Mon Sep 17 00:00:00 2001 From: Myk Taylor Date: Thu, 5 Nov 2020 16:01:44 -0800 Subject: [PATCH] quickfort guide: 'c' stockpiles don't make sense explain why "custom" stockpiles aren't meaningful to create in a blueprint and what the user should do instead --- docs/guides/quickfort-user-guide.rst | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/guides/quickfort-user-guide.rst b/docs/guides/quickfort-user-guide.rst index 964776f65..0df4bc24c 100644 --- a/docs/guides/quickfort-user-guide.rst +++ b/docs/guides/quickfort-user-guide.rst @@ -502,7 +502,12 @@ meeting area all at once: #zone main pasture and picnic area nmg(10x10) -The order of the individual letters doesn't matter. +The order of the individual letters doesn't matter. Note that "custom" +(:kbd:`c`) stockpiles cannot be declared in a blueprint since what would +get created would depend on what happens to be set in the "custom stockpile +settings" in your game. Instead, place stockpiles using the keys that +represent the types you want to store and then use a ``#query`` blueprint to +customize them. Detailed configuration for zones, such as the pit/pond toggle, can also be set by mimicking the hotkeys used to set them. Note that gather flags default to