Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

deal with steam deployment isolation

Ouverte
  • Quelque chose ne va pas ?
#5,719 2 commentaires 1 réaction 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 2 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
25/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
À l'abandon
Stack technique
cpp
Domaine
desktop, devtools

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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
Langage dominant
C++
Étoiles
2.1k
Forks
509
Merge moyen
2 j 13 h
PR mergées (30 j)
28

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de DFHack/dfhack

Toutes les issues de DFHack/dfhack

Issues similaires

Plus d'issues C++

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.