Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

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

未關閉
#5,955 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 4 天內回覆

還沒有人認領這個 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
平均合併
3 天 17 小時
30 天內合併 PR
13

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

DFHack/dfhack 的其他 Issue

查看 DFHack/dfhack 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。