-
Notifications
You must be signed in to change notification settings - Fork 472
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[quickfort] Stockpile and zone support #2974
Comments
Project plan
Next steps We'll need replacements for other "query" and "config" use cases:
|
myk002
changed the title
[quickfort] Move stockpile configuration into
[quickfort] Stockpile and zone support
Apr 17, 2023
place
blueprints
This was referenced May 20, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The most important missing feature of
quickfort
today is stockpile placement and configuration. Placement is done byplace
mode, and should not be too difficult to update on its own. However, stockpile configuration is done inquery
blueprints, and is a greater challenge.query
andconfig
blueprints are "freeform keystroke repeaters" -- you could have them reproduce any key sequence. This was fine when everything could be done with the keyboard. In v50, it is a great liability.I propose we deprecate
query
andconfig
modes entirely (along with keystroke aliases in general) and move stockpile configuration intoplace
mode, introducing a DSL for configuration. This approach has already been proven to work with the existingzone
blueprint format, where you can set zone properties as you declare the zones.All existing logic in
query
blueprints would need to be migrated, but given the change in the operating environment, I don't think this is avoidable. We can keep compatibility with existingplace
blueprints, though, with simple "all or nothing" category enablement.The DSL could be based on the current (successful) keystroke alias library, using a similar vocabulary. e.g.:
or more formally:
where
<name>
is the name of a saved stockpile config that thestockpile
plugin can apply to the given stockpile.stockpile
will need to be extended to add ("permit") or subtract ("forbid") stockpile settings in addition to just overwriting the config (when the<name>
is given without a command prefix).We would also need to create all these library stockpile configs and make them accessible.
The text was updated successfully, but these errors were encountered: