编辑“模组创作教程”（章节）

== Generate blank mod ==

You can get started creating a blank mod using either the Launcher to generate the starting files and directory, or doing so manually. Use the images below as a guide to creating a new mod with the Launcher, or skip down to the Manual section for instructions on creating the files yourself.

=== Launcher ===
<gallery mode="slideshow" style="margin-top:0">
 File:Stellaris paradox launcher modding 1.png|'''Open Mod Tools'''<br>Paradox Launcher has a tab dedicated to mod management. Open it and select Mod Tools.
 File:Stellaris paradox launcher modding 2.png|'''Select Create a Mod'''<br>All properly installed local mods can be found in the drop-down list. Select Create a Mod.
 File:Stellaris paradox launcher modding 3.png|'''Fill in descriptor data'''<br>Every mod has a descriptor file which stores basic metadata about the mod, such as full name, version (just for modder's reference), local installation path, and tags. It is useful to use a mod folder name which reflects mod's arbitrary but unique prefix.
 File:Stellaris paradox launcher modding 4.png|'''Done'''<br>Launcher will notify if mod has been created successfully. Any errors might indicate lack of space on a drive (usually partition C:) or insufficient write/read permissions (antivirus, file system permissions).
 File:Stellaris paradox launcher modding 5.png|'''Ready for edits and upload'''<br>Newly created mod is displayed in the window upon selection in the drop-down list. This is where first mod uploads and updates are uploaded. Contents of Description window will be visible on the mod store page after upload. Note: Description and Thumbnail inputs in this window '''are not''' stored locally and can be lost. It is highly recommended to store description text file and thumbnail in mod root folder.
</gallery>

=== Manually ===
Above effect can be achieved without using Paradox Launcher. Every mod requires two descriptor files, each one in proper directory.
# First mod descriptor contains '''metadata''' and '''local path''' where the game (Paradox Launcher) should look for the mod. It must be placed in '''%USERPROFILE%'''\Documents\Paradox Interactive\Stellaris\'''mod'''\
<!--## '''C''' is partition where your Documents folder is stored, usually system partition,-->
## '''%USERPROFILE%''' is your system user profile folder (by default this point to the same location as C:\Users\%USERNAME%),
## '''mod''' is a Stellaris folder for '''local''' mods (as opposed to Steam Workshop mods), Other Stellaris folders are '''logs''', '''save games''', '''screenshots''' etc.
# Second mod descriptor contains just '''metadata''' and is stored in '''root (main) mod folder''', which in the example would be '''%USERPROFILE%'''\Documents\Paradox Interactive\Stellaris\'''mod'''\'''tutmod'''\
## If Paradox Launcher was not used to create a mod one must create root mod folder manually.
## Root mod folder descriptor must be named '''descriptor.mod''',
## Paradox Launcher uses second descriptor when it imports a mod from mod store (Paradox Mods, Steam Workshop). When a mod is downloaded for a mod store this descriptor file is copied from the '''mod root folder''' to the Stellaris '''mod''' folder and a local path is added.

Tip: You can paste <code>%USERPROFILE%\Documents\Paradox Interactive\Stellaris\mod\</code> directly into the file explorer address bar without specifying user name.

Properly created mod has the following file structure on start:
# %USERPROFILE%\Documents\Paradox Interactive\Stellaris\mod\'''tutmod.mod'''
# %USERPROFILE%\Documents\Paradox Interactive\Stellaris\mod\'''tutmod\descriptor.mod'''

Example descriptor contents below.
{| class="wikitable"
! \mod\tutmod.mod !! \mod\tutmod\descriptor.mod
|-
| <pre>version="0.1"
tags={
	"Gameplay"
}
name="Tutorial Mod"
supported_version="2.8.1"
path="C:/Users/OldEnt/Documents/Paradox Interactive/Stellaris/mod/tutmod"</pre> || <pre>version="0.1"
tags={
	"Gameplay"
}
name="Tutorial Mod"
supported_version="2.8.1"</pre>
|}
Note how the only difference between two descriptor files is the '''path''' line.

{| class="wikitable"
! \mod\tutmod.mod !! \mod\tutmod\descriptor.mod
|-
|
[[File:Stellaris mod folder structure 1a.png|thumb|New tutmod folder with its first descriptor as visible in local mods directory. Note other local mods with friendly names and descriptors for Steam Workshop mods with an ugc_ prefix.]]
 ||
[[File:Stellaris mod folder structure 1c.png|thumb|Second descriptor inside of root (main) tutmod folder. Unlike the first one, this one does not contain local path to the root mod folder.]]
|}

'''Tip:''' You can use masks ([[wikipedia:Wildcard character|wildmarks]]) in the version string for descriptor files. Instead of writing:
 supported_version="2.8.1"
you can use:
 supported_version="2.8.*".
Launcher will recognise mod as up to date even when minor Stellaris patch is released. This has no effect on mod loading and the code, '''<code>supported_version</code>''' is merely a visual indicator.
Trivia: Some low level mods (like music or graphic) use also a wildmark for the second number (expanded support), which the launcher accepts (but throws an accusation entry in the error.log).