Difference between revisions of "HPL3/Amnesia: Rebirth/Modding/Creating a Mod"
Line 96: | Line 96: | ||
There are two different ways to run a mod: | There are two different ways to run a mod: | ||
− | <u>Through the Custom Story menu page in Main menu:</u> | + | <u>Through the Custom Story menu page in Main menu:</u> This method should generally be used when testing the final version of your mod. |
− | [[File:Rebirth-custom-stories-emnu.jpg|thumb|left]] {{clr}} | + | [[File:Rebirth-custom-stories-emnu.jpg|thumb|left|Custom Stories menu.]] {{clr}} |
<u>Command Line:</u> To run a mod directly with dev features enabled, you only need to run the game executable passing the "-mod" argument followed by word <code>local:</code> and then immediately the name of the mod folder. This method should be used throughout the development of your mod. | <u>Command Line:</u> To run a mod directly with dev features enabled, you only need to run the game executable passing the "-mod" argument followed by word <code>local:</code> and then immediately the name of the mod folder. This method should be used throughout the development of your mod. |
Revision as of 14:10, 6 November 2020
This article describes in detail how to create, setup and structure your mod.
Contents
Mod Types
Amnesia: Rebirth has one mod type called a Stand-Alone mod.
Stand-Alone Mod
A Stand-Alone mod describes a mod of extensive game modification: Custom assets, Custom scripts and even overrides of existing game scripts.
Mod Structure
A typical mod structure (folders and files) may look like this:
modFolder/
├── config/
│ ├── lang/
│ │ ├── english.lang
│ ├── main_init.cfg
├── maps/
├── entry.hpc
├── resources.cfg
The mod structure may change and have more or less files, depends on your mod type, but it's important to have entry.hpc and resources.cfg for every mod.
Mod Entry File
When creating a mod, be it a simple add-on or a fully fledged total conversion, an entry file is needed so that the mod can be listed by the custom stories menu or simply be started by the game.
This means that an XML file with name entry.hpc
needs to be created in the root directory of the mod, and its contents will depend on what kind of mod you are creating.
Setting up the Entry File
![Icon tip.png](/nsfr_img_auth.php/b/be/Icon_tip.png)
- Create a file named
entry.hpc
in your mod's root folder. - Paste the following content into the file and save:
<?xml version="1.0" encoding="UTF-8"?> <Content Version="1.0" Type="StandAlone" Title="Your mod name here" Author="Your name here" Description_English="Mod description here" LauncherPic="LauncherPic.png" InitCfg="config/main_init.cfg" />
Common Attributes
Any valid entry.hpc
file (like the one shown above), will have at least the following attributes:
Version | The version for the mod, since the mod might get updated in the future. |
Type | The type for the content the mod is offering. Possible values are "AddOn" or "StandAlone" .
|
Title | This sets the title for the mod. It should not be longer than 128 characters, especially if the mod is to be uploaded to the Steam Workshop. |
Author | The creator(s) of the mod. This will be shown below the title on the info column in the ModLauncher application. |
Description_English | The description of the mod. Should not exceed 8000 characters for the same reason as the title.
For localizing descriptions, add a translated entry for the target language under the Description_(name of target language) parameter. |
LauncherPic | The file to be used as a thumbnail picture for the Custom Story menu page. |
InitCfg | The relative path to the file which information when initializing the mod. The default value is "config/main_init.cfg" and usually shouldn't be changed.
|
Special Attributes
There are special attributes which can be added to a mod entry file in order to enable optional functionalities:
UID | A string in the form "provider_name.mod_name" . This is used so other mods can reference your mod as a Mod Dependency
|
Dependencies | A list of UIDs separated by commas. The resources in these mods will be available to the game when the current mod is running. |
Mod Configuration Files
In addition to the mod entry file, the mod needs to be correctly configured in order to load resources such as maps, script, sounds, sounds, etc (As seen in the Mod Structure diagram).
Read the following articles in order to understand how to set up and configure them:
It is recommended to copy the files from the mods provided with the game and modify them, instead of creating them on your own.
Running the Mod
There are two different ways to run a mod:
Through the Custom Story menu page in Main menu: This method should generally be used when testing the final version of your mod.
Command Line: To run a mod directly with dev features enabled, you only need to run the game executable passing the "-mod" argument followed by word local:
and then immediately the name of the mod folder. This method should be used throughout the development of your mod.
Example:
AmnesiaRebirth.exe -mod local:my_mod
There are more arguments which can be added to the command line. It is recommended to create a .bat
file which will launch the mod.
![Icon tip.png](/nsfr_img_auth.php/b/be/Icon_tip.png)
Main article: Developer Commands
What's Next
Now that the mod is set up, you may proceed to set up a Modding Environment for your game, and learn how to use the Developer Debug Menu. it is also recommended to set up an online repository. More articles are available in the main Amnesia: Rebirth modding category.