Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

"Make top priority" means two different things in buildingplan vs prioritize overlays

未关闭
#5,955 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 3 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
52/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
活跃
技术栈
cpp
领域
tooling

调研方向

The two conflicting "make top priority" labels belong to the buildingplan and prioritize overlays, so start by searching the repository for that string to find where each label is defined. Confirm which overlay sets the building's item-matching tasks and which toggles job.flags.do_now. Pick one new label, most likely the one the issue suggests, and apply it in only one overlay. Done when the two overlays no longer share a label for different actions.

由索引模型根据 Issue 内容生成。

描述

Two controls on the building info sheet share the label "make top priority" but do unrelated things:

  • buildingplan's inspector overlay (Ctrl+T, shown while a building waits for items) bumps the building's item-matching tasks to the front of buildingplan's queues — i.e. "get materials delivered first".
  • prioritize's enroute overlay (Ctrl+T, shown once the construction job is active) toggles job.flags.do_now — i.e. "dwarves should build this before other work".

They appear on the same screen at different lifecycle phases, so users will reasonably assume the same label means the same action. Renaming one of them (e.g. buildingplan's to something like "prioritize materials", or prioritize's to "do job now" to match the flag) would remove the ambiguity.

Surfaced while working on #2353.

主要语言
C++
星标
2.1k
派生
509
平均合并
2 天 19 小时
30 天内合并 PR
25

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

DFHack/dfhack 的其他 Issue

查看 DFHack/dfhack 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。