For the moment, you can add your own localizations and fonts in The Last Spell.
However, we’re very hopeful that will change in the future!

If you want to subscribe to a Steam mod:

• Go to the Workshop Hub of TLS: https://sp.zhabite.com/app/1105670/workshop/
  
• Click on Browse → Items
  
• A list of mods should appear, and you just need to click on the one(s) you want and click “Subscribe” in the Page that opens.
  
• The mod will automatically download after that.

A mod is usually made like this:
→ Parent folder
→ → Manifest.xml
→ → Thumbnail
→ → Modules Folders
→ → → Files/Folders that are necessary for the proper functioning of the module
(fonts; .csv, etc)

The mods work with a “Module” architecture. A Mod can be a Translation Mod and/or a Fonts
Mod.

A module is defined by creating a subfolder of the Parent Folder. However, that folder must have
a specific name, the name of the folder will allow us to know its Type (the available Modules
names will be listed in their respective sections, further in the document). If the Module needs a
configuration file, you’ll need to create one in the Module folder (the content of this file depends
on the type of the Module).

You don’t need this example per se, but it will help with the mod structure creation as you will be
able to copy this model.

You’ll need to subscribe to this mod to download it, it can be found here:
https://sp.zhabite.com/sharedfiles/filedetails/?id=2607059231

This mod gives a small example of both a Localization Module and a Fonts Module.

• Localization: it loads an entire new localization, but this file is mostly empty (so most of the labels will default to the standard English). To check that it works, you have to launch the game, go to options and then select the language “Example Language” and then go back to the main menu => the “Options” label will be replaced by “Options Test”.

• Fonts: it replaces the 2 fonts of the game. You won’t notice any difference on the “standard” font because it actually loads the same that is used without mod, but you will definitely notice that the title font has changed.

→ Create the structure for your mod
This section will describe what needs to be done to create a mod, so that you know how it works, but you can actually ease the process by duplicating the Example Mod structure. To do so, once downloaded you can find it in your steam files at this location:

SteamLibrary\steamapps\workshop\content\1105670\2607059231

Copy all the folder “2607059231” into %Appdata%\..\LocalLow\Ishtar Games\The Last Spell\Mods\, then rename the folder to your mod’s name and delete the “steam_workshop.txt” (this removes the link with the original Steam Workshop mod).

Otherwise, you first need to create a “Mods” folder in this folder %Appdata%\..\LocalLow\Ishtar Games\The Last Spell\. Then, inside this folder, you
must create a folder with your mod in it (you can name the folder as you want).



In your new mod folder, you need to have a file called “manifest.xml”, and at least one Module in a folder named accordingly (cf the respective Module sections later in this guide). If the mod folder doesn’t have those, then it won’t be considered a mod by the game.


→ The “manifest.xml” file
This file allows us to know the title and the description of the mod. This will allow the mod to be
correctly displayed in the interface that lists the currently installed/used by the game mods. That info will also be used when the mod goes online to name and describe the mod. If you put “true” after “OverrideSteamDatas”, that info will also be used when the creator of the mod will publish an update.

• OverrideSteamDatas: This is used to know if you want to update the title and the description of the mod in the workshop when the creator will want to publish an update for the mod. It’s not required, and if it’s not declared, then it will be considered that the creator doesn’t want to update the title and the description of the mod after an update.
  
• Title: (Required) This allows you to give a title to the mod when it’s published in the workshop.
  
• Description: (Optional) This allows you to write a description to the mod when it’s published in the workshop.
  
• Author: (Optional) This allows you to put the creator’s name in the interface that lists the used mods.
  
• Version: (Introduced with the Version 2 of the Modding) This will allow us to know the version that is targeted. We’ll also have the “ModdingVersion” and the “ModdingMinVersion” that will allow us to know whether the Mod is considered as compatible or not. The modder will need to write the current version of the ModdingVersion during its creation, so after an update if the ModdingVersion and/or the ModdingMinVersion has changed, the game will be able to detect if the Mod is still compatible. With Version 3, you need to have at least “3” as the version number.

You can find the Modding Version here:


Once that’s done, your mod is enabled in game!

→ Check if the mod is active
When you launch the game, you should see a button in the upper left corner of your screen in the
main menu.



The button will open a menu displaying the currently active mods ingame.

When you’re subscribed to a mod on Steam, then you will automatically download the mods to which you’re subscribed. If you’re also the creator of this mod, then you’ll technically have 2 version of the mod. So, one of those version (the Online one) will be greyed out, to prevent any bug or issue).

Once you have a working local mod and want to publish it to the Steam Workshop, you’ll need to
enable the “Developer” mode in the game.

In Steam, you need to right-clic on “The Last Spell”, “Settings”, and a menu will open. In the last line called “Launch Options”, you’re going to write the password to unlock the “Developer mode”. The password is “-dev”.


Once that’s done, you need to launch The Last Spell, and go back to the “Mod” menu. Now, you
should have a screen that looks like this.


You need to click on “Create in Workshop” to upload your mod in Steam.


Once that’s done, a file called “steam_workshop.txt” at the root of your local mod will be created. The file is actually a number representing the ID of the mod in the workshop. Don’t modify or erase that file because you’ll need it to publish updates for your mod!

If you want to update a Steam mod, you’ll need to have the mod locally. So, you’ll need to have the
steam_workshop.txt file in %Appdata%\..\LocalLow\Ishtar Games\The LastSpell\Mods\.

If you have the mod locally, and you’re in developer mode, the button in the menu will change and
will be named “Update in Steam”.


You need to be the creator of the mod to update it! Otherwise, it won’t work.

If you want to create and upload a thumbnail so it’s displayed on Steam, the image must:

• Be less than 1Mb
  
• Be one of the supported formats/extensions => .jpg, .png, .jpeg, or .gif
  
• Be named thumbnail.<extension>

Once your image is created, you need to place it in the mod folder, just like the manifest file.

We suggest making square images, because if it’s not square, then it will be resized and may end up
looking less good!

The purpose of this Module is to bring new languages into the game.

Read this article to learn how to create your Localization Module:
https://sp.zhabite.com/sharedfiles/filedetails/?id=3444212103

The purpose of this Module is to bring new fonts into the game. There are 2 fonts in The Last Spell,
one used mostly for titles and the second being the “standard” one.

Read this article to learn how to create your Font Module:
https://sp.zhabite.com/sharedfiles/filedetails/?id=3470141700