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

deal with steam deployment isolation

Offen
  • Stimmt etwas nicht?
#5,719 2 Kommentare 1 Reaktion 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 2 Tagen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
25/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Veraltet
Tech-Stack
cpp
Bereich
desktop, devtools

Rechercherichtung

The issue describes changes to the DFHack launcher and dfhooks, including dfhooks.ini, but names no source files or tests. Start by locating the launcher and dfhooks entry points and tracing how they find the game and load DFHack. Done means supporting separate Steam install folders, the stated backward compatibility, and deferred hook updates after DF exits; the issue has had no comment for over 180 days.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

We've been getting reports that the beta version of the Steam client is installing DFHack in a folder labeled "Dwarf Fortress 2346660" instead of in "Dwarf Fortress", which is breaking the way that we make our dfhooks library visible to Dwarf Fortress

After some discussion on discord the following approach seems to me to be the best method for dealing with this:

  • Let Steam install DFHack wherever it likes
  • The DFHack launcher will, each time it is launched, locate the DF installation and if necessarily push dfhooks.dll/dfhooks.ld.so into that folder, along with a dfhooks.ini that contains the path of the DFHack installation
  • dfhooks will be modified to read this dfhooks.ini and use it to locate dfhack.dll/dfhack.ld.so and load it. This location will also be passed to the dfhack initialization and will be used as the dfhack app root folder location.
  • If the launcher is being launched in "show-activity" mode (because the game was launched from DF, not from DFHack) it will check to see if an update to dfhooks.dll is needed and will schedule that update after DF exits (to avoid a locked file conflict) when needed

Backward compatibility:

  • If dfhooks.ini is missing assume DFHack is installed in the same folder as DF
  • If the parameter for passing the dfhack root folder to dfhack.dll is missing, assume DFHack is installed in the current working directory
Vorherrschende Sprache
C++
Sterne
2.1k
Forks
509
Ø Merge
2 T. 13 Std.
Gemergte PRs (30 T.)
28

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.