Mod - Revision history

DuskTheUmbreon: /* Publishing on Steam Workshop */ Note that the blank/empty upload issue can be fixed by including a preview

2025-10-11T03:00:53Z

Publishing on Steam Workshop: Note that the blank/empty upload issue can be fixed by including a preview

GeloMor: Interwiki link

2025-07-31T01:53:26Z

Interwiki link

Cali: Undo revision 309760 by Ziusudra (talk) "Steam Workshop" is a proper noun which is an exception mentioned in Rule N

2025-06-13T19:01:36Z

Undo revision 309760 by Ziusudra (talk) "Steam Workshop" is a proper noun which is an exception mentioned in Rule N

Ziusudra: /* Publishing on Steam Workshop */ rule N on section title

2025-06-13T18:52:27Z

Publishing on Steam Workshop: rule N on section title

Gorbage: Added "The" before "Steam Workshop"

2024-04-03T11:53:05Z

Added "The" before "Steam Workshop"

Silverwing235: /* Mod info */

2023-09-27T18:58:28Z

Mod info

Lethosor: /* Objects and graphics folder */

2023-08-14T01:50:59Z

Objects and graphics folder

Silverwing235: /* Updating/missing mods */

2023-06-15T13:18:08Z

Updating/missing mods

Silverwing235: /* Mod info */

2023-06-15T09:39:26Z

Mod info

Silverwing235: /* Mod info */

2023-06-14T22:00:54Z

Mod info

← Older revision		Revision as of 03:00, 11 October 2025
Line 90:		Line 90:

	Once the upload process is completed successfully, you'll find a <code>[STEAM_FILE_ID:#########]</code> appended to your info.txt. Make sure this entry is included for future uploads if you want to make changes to your mod and have it overwrite the existing entry on the workshop. Otherwise you'll create a new entry every time you upload.		Once the upload process is completed successfully, you'll find a <code>[STEAM_FILE_ID:#########]</code> appended to your info.txt. Make sure this entry is included for future uploads if you want to make changes to your mod and have it overwrite the existing entry on the workshop. Otherwise you'll create a new entry every time you upload.
		+
		+	If you have problems with blank or empty mods uploading, adding a preview.png file (as detailed [[Mod#Mod_info\|above]]) may fix this problem.

	=== Publishing on DFFD ===		=== Publishing on DFFD ===

← Older revision		Revision as of 01:53, 31 July 2025
Line 98:		Line 98:

	[[Category:Modding]]		[[Category:Modding]]
		+	[[ru:Mod]]

@@ Line 85: / Line 85: @@
 There are two official platforms for publishing ''Dwarf Fortress'' mods, recommended because it's easy for people to find them there. These are [https://steamcommunity.com/app/975370/workshop/ the Steam Workshop] and [https://dffd.bay12games.com/ the Dwarf Fortress File Depot (DFFD)].
-=== Publishing on steam workshop ===
+=== Publishing on Steam Workshop ===
 To upload a mod to Steam Workshop, you need to add STEAM tags to the <code>info.txt</code> file (see above.) Afterward, you put the unzipped mod folder in the "<code>mods/mod_upload</code>" folder. Then select Mods from the title menu, and upload your mods using the button you'll see there. Other Steam users will be able to subscribe to your mod immediately once it is uploaded.

@@ Line 85: / Line 85: @@
 There are two official platforms for publishing ''Dwarf Fortress'' mods, recommended because it's easy for people to find them there. These are [https://steamcommunity.com/app/975370/workshop/ the Steam Workshop] and [https://dffd.bay12games.com/ the Dwarf Fortress File Depot (DFFD)].
-=== Publishing on Steam Workshop ===
+=== Publishing on steam workshop ===
 To upload a mod to Steam Workshop, you need to add STEAM tags to the <code>info.txt</code> file (see above.) Afterward, you put the unzipped mod folder in the "<code>mods/mod_upload</code>" folder. Then select Mods from the title menu, and upload your mods using the button you'll see there. Other Steam users will be able to subscribe to your mod immediately once it is uploaded.

@@ Line 83: / Line 83: @@
 == Publishing mods ==
-There are two official platforms for publishing ''Dwarf Fortress'' mods, recommended because it's easy for people to find them there. These are [https://steamcommunity.com/app/975370/workshop/ Steam Workshop] and [https://dffd.bay12games.com/ the Dwarf Fortress File Depot (DFFD)].
+There are two official platforms for publishing ''Dwarf Fortress'' mods, recommended because it's easy for people to find them there. These are [https://steamcommunity.com/app/975370/workshop/ the Steam Workshop] and [https://dffd.bay12games.com/ the Dwarf Fortress File Depot (DFFD)].
 === Publishing on Steam Workshop ===

@@ Line 72: / Line 72: @@
 STEAM tags are only used by Steam.
 * The <code>STEAM_FILE_ID</code> used to identify the mod in the Workshop. This is automatically managed when uploading to Steam the first time, and required if you wish to update an existing Steam Workshop mod.
-* The <code>STEAM_TAG</code> and <code>STEAM_KEY_VALUE_TAG</code> are used by Steam's search engine and the categorization. You can use as many entries as you want, use a separate tag for each one.
+* The <code>STEAM_TAG</code> and <code>STEAM_KEY_VALUE_TAG</code> are used by Steam's search engine for categorization. You can use as many entries as you want, use a separate tag for each one.
 * You can also create a thumbnail for your mod, by creating an image called <code>preview.png</code> in the same level as your info.txt file. This image will become the thumbnail when the mod is uploaded to Steam Workshop. The image should be less than 1MB in size.

@@ Line 77: / Line 77: @@
 === Objects and graphics folder ===
-At the root of your mod folder you can have a <code>objects\</code> and <code>graphics\</code> folder, this is where all the [[raw file]]s or [[graphics]] goes (exactly the same as objects from previous versions of Dwarf Fortress) allowing you to tweak or add new content for the game. It's beyond the scope of this short guide to go into what specific tags do, but the vanilla objects and previous mods by members of the community will give you plenty of examples to work with. See: [[modding]].
+A mod folder can contain an <code>objects</code> and <code>graphics</code> folder. These are where all the [[raw file]]s or [[graphics]] for the mod go (exactly the same as objects from previous versions of Dwarf Fortress) allowing you to tweak or add new content for the game. It's beyond the scope of this short guide to go into what specific tags do, but the vanilla objects and previous mods by members of the community will give you plenty of examples to work with. See [[modding]] for more information.
-The graphics filenames are not important, furthermore they can be arbitrarily nested into other sub-folders to help you organize your mod content.
+The graphics filenames are not important; furthermore, they can be arbitrarily nested into other sub-folders to help you organize your mod content.
 == Publishing mods ==

@@ Line 26: / Line 26: @@
 If a [[save]] is using a mod that's been updated, and is currently using an older version of that mod, the player will be prompted about this when a save is loading. When this happens, you have the choice of simply updating the mod, updating ''all'' mods at once, continuing to use the older version of the mod in question without updating, selecting the previous task but not updating ''any'' possibly outdated mods or simply returning to the title screen.
-If a save is using a mod that is missing, the player will be prompted about this when a save is loading. When this happens, try to reinstall the mods. Either by manually downloading them again or in case of Steam Workshop making sure you are subscribed and if you do by unsubscribing and subscribing again.
+If a save is using a mod that is missing, the player will be prompted about this when a save is loading. When this happens, try to reinstall the mods, either by manually downloading them again, or in the case of Steam Workshop, making sure you are subscribed and if you are, by unsubscribing and subscribing again.
 == Modding ==

@@ Line 46: / Line 46: @@
 {{main|Mod info token}}
-Each mod must have a <code>info.txt</code> at the root of your mod folder. It has a few fields defining basic metadata information about the mod and can be edited using any text editor (like notepad++). See Example:
+Each mod must have an <code>info.txt</code> at the root of your mod folder. It has a few fields defining basic metadata information about the mod and can be edited using any text editor (like notepad++). See Example:
 {{code|