Difference between revisions of "Modding"

From RimWorld Wiki
Jump to navigation Jump to search
(fixing typo in mac path)
 
(72 intermediate revisions by 35 users not shown)
Line 1: Line 1:
__NOTOC__
+
<!--Top Nav Box-->
 
+
{| align=center
==MODs files are stored in:==
+
| {{Basics_Nav}}
{|
 
|[[File:Folders-OS-Windows-8-Metro-icon.png|36px]]
 
|
 
===Windows version===
 
 
|}
 
|}
<code>path to game folder/Mods</code>
 
 
----
 
----
{|
 
|[[File:Folders-OS-Linux-Metro-icon.png|36px]]
 
|
 
===Linux version===
 
|}
 
  
----
+
'''Game modifications''' (or '''mods''') are a way of altering the way the game functions by adding, changing, or removing content such as items, textures, sounds, or more. RimWorld has built-in support for modding, including Steam Workshop support.
{|
 
|[[File:Folders-OS-Apple-Metro-icon.png|36px]]
 
|
 
===Mac OS X version===
 
|}
 
  
==General Modding Advice==
+
== Using Mods ==
*The tilde key (`) brings up the dev console, which will report any errors it encounters. This is the quickest way to see what, if any, errors exist in your mod.
 
*Use Developement Mode (Found in Options) to help debug your mod.
 
  
==Mod Info:==
+
If you own RimWorld on Steam, then the easiest way of finding and downloading mods is by using [https://steamcommunity.com/app/294100/workshop/ Steam Workshop]. Steam Workshop automates the process of downloading and installing mods, as well as keeping them up to date with new releases.
This is found in \MODNAME\About\
 
*The contents of About.xml are plain text. HTML Markup tags cause NullRef's.
 
*You can have an image for your mod. Restrict the image width to 600 pixels
 
  
==Textures:==
+
Even if you do not own RimWorld on Steam, Workshop can still be used to discover new mods; while some mods are released on [https://www.nexusmods.com/rimworld Nexus Mods], no other mod site has close to the same amount of mods available. You can use tools such as [https://github.com/rimpy-custom/RimPy/releases RimPy] to download and install mods from Steam Workshop and GitHub instead.
These are found in \MODNAME\Textures\
 
*You can have any path you want from this point on.
 
*When referencing textures in your mod, using <TexturePath>, have the complete path relative to your mod, including the filename (but not the file extension) Example for the RoyalBed Testmod: <TexturePath>Things/Building/RoyalBed</TexturePath>
 
*You can randomize textures within a folder using a <textureFolderPath> pointing at a folder with multiple textures inside. Each Thing of the given def will have a random texture from the folder (which may change when the game is saved and reloaded).
 
  
==Mod Folder Structure:==
+
=== Manual Installation ===
While you can name all .xml files whatever you want. You cannot rename the folders; the game looks in folders with specific names to find specific data.
 
  
==New Interactable "Things":==
+
You can install mods manually by unzipping them into subfolders within your local Mods folder. This location varies by operating system:
A thing is anything that exists in the game world. It includes resources, races (humanoid and animal), buildings, furniture, and many others.
 
  
These are defined in \MODNAME\Defs\ThingDefs
+
{| class="wikitable" style="margin-right:auto"
If you make a new workbench, you'll need to define a recipe for it. This is a list, so you can have many new recipes listed.
+
|-
 
+
! Operating System !! Default Folder Location
The recipes themselves are defined in: \MODNAME\Defs\RecipeDefs
+
|-
In here you can define what ingredients/resources are required, what can be used, and what the default recipe is.
+
| Windows || <code>C:\Program Files (x86)\Steam\steamapps\common\RimWorld\Mods</code>
 
+
|-
Any new resources will need to be defined in: MODNAME\Defs\ThingDefs
+
| Mac || <code>Library/Application Support/Steam/steamapps/common/RimWorld</code>
 +
|-
 +
| Linux (standalone) || <code>~/.steam/steam/steamapps/common/RimWorld/Mods</code>
 +
|-
 +
| Linux (GoG) || <code>/home/<user>/GOG/Games/RimWorld/game/Mods/</code>
 +
|}
  
==New Turrets:==
+
=== Activating Mods ===
These are defined in two files in: \MODNAME\Defs\ThingDefs
 
Buildings_Big.xml and Weapons_Guns.xml (Remember, these can be named anything)
 
  
Buildings_Big.xml defines the structure of the turret itself. IE:
+
Once you have installed mods, you can select the '''Mods''' option from the main menu of RimWorld to activate them. Activating or deactivating mods requires RimWorld to restart.
<syntaxhighlight lang="xml" >
 
<building>
 
<turretGunDef>Gun_TurretImprovised</turretGunDef>
 
<burstCooldownTicks>300</burstCooldownTicks>
 
</building>
 
</syntaxhighlight>
 
Weapons_Gun.xml defines the weapon the turret uses. Anything can be used as a weapon for turrets, including grenades.
 
  
==New Resources:==
+
== Making Mods ==
These are defined in: MODNAME\Defs\ThingDefs\Resources.xml
 
  
==New Research Projects:==
+
Please check out the [[Modding_Tutorials|Modding Tutorials]] hub for tutorials and guides on how to create and publish your own mods.
These are found in: MODNAME\Defs\ResearchProjectDefs
 
You can have research trees as well, where additional research projects get unlocked as you move through.
 
This is how to add prerequisites:
 
<syntaxhighlight lang="xml" >
 
<prerequisites>
 
<li>-this is the <defName> of the prerequisite-</li>
 
</prerequisites>
 
</syntaxhighlight>
 
Because it's a list, you can have multiple prerequisites for a research project.
 
  
== References ==
+
[[Category:Modding]]
*[http://ludeon.com/forums/index.php?topic=1681.0 forum thread]
 
*[http://rimworldgame.com/publicArtSource/ThingGraphics.zip RimWorld core art source]
 

Latest revision as of 08:05, 24 October 2023

Basics Menus Game Creation Gameplay Pawns Plants Resources Gear Mods
Basics Menu Controls User Interface Save File Modding Version history

Game modifications (or mods) are a way of altering the way the game functions by adding, changing, or removing content such as items, textures, sounds, or more. RimWorld has built-in support for modding, including Steam Workshop support.

Using Mods[edit]

If you own RimWorld on Steam, then the easiest way of finding and downloading mods is by using Steam Workshop. Steam Workshop automates the process of downloading and installing mods, as well as keeping them up to date with new releases.

Even if you do not own RimWorld on Steam, Workshop can still be used to discover new mods; while some mods are released on Nexus Mods, no other mod site has close to the same amount of mods available. You can use tools such as RimPy to download and install mods from Steam Workshop and GitHub instead.

Manual Installation[edit]

You can install mods manually by unzipping them into subfolders within your local Mods folder. This location varies by operating system:

Operating System Default Folder Location
Windows C:\Program Files (x86)\Steam\steamapps\common\RimWorld\Mods
Mac Library/Application Support/Steam/steamapps/common/RimWorld
Linux (standalone) ~/.steam/steam/steamapps/common/RimWorld/Mods
Linux (GoG) /home/<user>/GOG/Games/RimWorld/game/Mods/

Activating Mods[edit]

Once you have installed mods, you can select the Mods option from the main menu of RimWorld to activate them. Activating or deactivating mods requires RimWorld to restart.

Making Mods[edit]

Please check out the Modding Tutorials hub for tutorials and guides on how to create and publish your own mods.