|
|
@ -96,13 +96,14 @@ When you `download DFHack <downloading>`, you will end up with a release archive
|
|
|
|
operating system should have built-in utilities capable of extracting files from
|
|
|
|
operating system should have built-in utilities capable of extracting files from
|
|
|
|
these archives.
|
|
|
|
these archives.
|
|
|
|
|
|
|
|
|
|
|
|
The release archives contain several files and folders, including a ``hack``
|
|
|
|
The release archives contain several folders, including a ``hack`` folder where
|
|
|
|
folder, a ``dfhack-config`` folder, and a ``dfhack.init-example`` file. To
|
|
|
|
DFHack binary and system data is stored, a ``dfhack-config`` folder where user
|
|
|
|
install DFHack, copy all of the files from the DFHack archive into the root DF
|
|
|
|
data and configuration is stored, and a ``blueprints`` folder where `quickfort`
|
|
|
|
folder, which should already include a ``data`` folder and a ``raw`` folder,
|
|
|
|
blueprints are stored. To install DFHack, copy all of the files from the DFHack
|
|
|
|
among other things. Some packs and other redistributions of Dwarf Fortress may
|
|
|
|
archive into the root DF folder, which should already include a ``data`` folder
|
|
|
|
place DF in another folder, so ensure that the ``hack`` folder ends up next to
|
|
|
|
and a ``raw`` folder, among other things. Some packs and other redistributions
|
|
|
|
the ``data`` folder.
|
|
|
|
of Dwarf Fortress may place DF in another folder, so ensure that the ``hack``
|
|
|
|
|
|
|
|
folder ends up next to the ``data`` folder.
|
|
|
|
|
|
|
|
|
|
|
|
.. note::
|
|
|
|
.. note::
|
|
|
|
|
|
|
|
|
|
|
|