Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

[Feature Request] Adopt gui/production-manager (work order groups, loadouts, profiles) as a built-in tool

Offen
  • Stimmt etwas nicht?
#5,876 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 3 Tagen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
15/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Ruhig
Tech-Stack
lua
Bereich
devtools

Rechercherichtung

This is a proposal to adopt an external Lua GUI tool in-tree, not a defined change. Start with the orders plugin's orders import path and the built-in library/* orders, which the tool reads and reuses, and with the user dfhack-config/orders/ files. Related issues #5407 and #3555 cover overlapping scope and should be read first. Done would need a maintainer decision on whether and how the feature is added, which the thread does not yet contain.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

What

I wrote a GUI tool that adds grouping on top of the orders plugin: work
orders get put into named groups, groups get bundled into loadouts,
and a full set of loadouts is a profile you can switch in one click
(e.g. peace vs wartime). It also exports a profile to a compact share token
for trading setups between players.

It's Lua-only, Zlib, and shells out to orders import rather than
reimplementing it. It reads groups from the built-in library/* orders and
the user's dfhack-config/orders/ files, and only removes orders it added
itself, so it doesn't disturb orders the player or tools like autocheese
created outside it.

It's on the workshop as a mod right now:
https://steamcommunity.com/sharedfiles/filedetails/?id=3784821619

Image

Why in-tree

The orders plugin handles a flat list, but there's no way to toggle a
subset on/off together, switch a whole setup at once, or share one. This
seems to cover a chunk of what #5407 (selective import/export, mark
inactive, editor) and #3555 (orders in folders by industry) ask for.

More concretely, I think this earns its place because it sits cleanly on top
of what's already there: it reuses the orders import path and the built-in
library rather than forking them, so it's additive, not a replacement. It
also respects orders it didn't create, which is the part that usually trips
up work-order tooling and makes people afraid to use it. And being Lua-only
means it's a small, self-contained review.

Happy to do whatever refactoring it needs to merge — just point me at
what you'd want changed.

Vorherrschende Sprache
C++
Sterne
2.1k
Forks
509
Ø Merge
2 T. 19 Std.
Gemergte PRs (30 T.)
25

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus DFHack/dfhack

Alle Issues in DFHack/dfhack

Ähnliche Issues

Weitere Issues zu C++

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.