Modding

Important

Before you begin, ensure you have SQLite Browser installed on your computer.

It is possible to change team and player names using a visual database editor such as SQLite Browser.

You can choose to modify your current save or the "root save" database, which LIGA Esports Manager uses as the foundation for generating new game saves.

Modifying the Correct Save

Current Save

This method will only affect your current save and not future saves.

Your current save is located in:

%APPDATA%\LIGA Esports Manager\saves\save_1.db

The number increases with each additional save.

Root Save

Note

This is the recommended method.

This method will not affect your current save but will ensure new and subsequent saves will automatically include your modificatons.

Run the following in a PowerShell terminal window.

cd $env:APPDATA'\LIGA Esports Manager'
mkdir custom\saves
cp saves\save_0.db custom\saves\save_0.db

In the next step you will be modifying the custom save you've just created:

%APPDATA%\LIGA Esports Manager\custom\saves\save_0.db

Team Names

Caution

Do not move teams from their original federation.

For example, you can move a team from USA to Brazil but not from USA to Sweden, as they are in two different federations.

Please refer to the federations section below for a list of country IDs and their federation.

Launch SQLite Browser and open up the save of your choosing.

Once the database loads, click on the "Browse Data" tab and switch to the "Team" table by using the "Table" dropdown.

This will give you a table view of the team's tabular data.

In LIGA Esports Manager, there are 5 divisions that teams are grouped into. The higher a team's tier, the better. So if you would like to modify just the team names in the Premier division, you would only modify the teams with a tier level of 4.

Division	Tier
Open	0
Intermediate	1
Main	2
Advanced	3
Premier	4

Clicking on the "tier" column sorts the teams from highest to lowest tier. You can also filter teams by a specific tier value by entering the desired number in the textbox beneath the column header.

For example, to display only the teams in the Premier division, type in =4 in the filter textbox under the tier column header.

To change a team's name, double click on the name field to open up the editor and change their name.

Once you're happy with the changes, click on "Apply" and then "Write Changes".

Player Names

Launch SQLite Browser and open up the save of your choosing.

Once the database loads, click on the "Browse Data" tab and switch to the "Player" table by using the "Table" dropdown.

This will give you a table view of the player's tabular data.

To change a player's name, double click on the name field to open up the editor and change their name.

Once you're happy with the changes, click on "Apply" and then "Write Changes".

Team Logos

Adding custom team logos works very much the same way as modding the team names.

The first thing to do is to create a "blazonry" folder within the app's "custom" folder.

Run the following in a PowerShell terminal window.

cd $env:APPDATA'\LIGA Esports Manager'
mkdir custom\blazonry

Now place your custom logos within the custom\blazonry folder.

Launch SQLite Browser and open up the custom save created in the previous step.

Once the database loads, click on the "Browse Data" tab and switch to the "Team" table by using the "Table" dropdown.

To change a team's logo, double click on the blazon field to open up the editor and change the path to your custom logo:

custom://blazonry/compLexity.svg

Once you're happy with the changes, click on "Apply" and then "Write Changes".

Player Avatars

Adding custom player avatars works very much the same way as modding the team logos.

The first thing to do is to create an "avatars" folder within the app's "custom" folder.

Run the following in a PowerShell terminal window.

cd $env:APPDATA'\LIGA Esports Manager'
mkdir custom\avatars

Now place your custom player avatars within the custom\avatars folder.

Launch SQLite Browser and open up the custom save created in the previous step.

Once the database loads, click on the "Browse Data" tab and switch to the "Player" table by using the "Table" dropdown.

To change a player's logo, double click on the avatar field to open up the editor and change the path to your custom avatar:

custom://avatars/apEX.png

Once you're happy with the changes, click on "Apply" and then "Write Changes".

Map Pool

Launch SQLite Browser and open up the save of your choosing.

Once the database loads, click on the "Browse Data" tab and switch to the "GameVersion" table by using the "Table" dropdown. This will list the IDs of the game you would like to customize the map pool for.

For example, let's add de_cache to CS2. Using the table below, you can see that CS2's game version ID is 2.

Now switch over to the "GameMap" table and grab the ID of the map you would like to add. In this example, you want de_cache which is 3.

Finally, you're ready to add de_cache to CS2. Switch over to the "MapPool" table and click "Insert a new record in the current table".

In the modal that opens up, you only need to insert the gameMapId and gameVersionId values which are 3 and 2, respectively.

Once you're happy with the changes, click on "Apply" and then "Write Changes".

The final step is to place the actual map files in the plugins directory that the application uses to load custom maps into Counter-Strike.

Open up a folder to %APPDATA%\LIGA Esports Manager\plugins and place the maps in their appropriate game folder.

Federations

In LIGA Esports Manager every team is part of one of two federations.

When making changes to the database, such as when changing the country of a team, it is important to keep the balance of the Federations and only re-assign a country within the same Federation.

You can run the following query directly in SQLite Browser to get the list of countries within a federation or use the table below.

SELECT
    c.id AS countryId,
    c.name AS countryName
FROM
    Country c
JOIN
    Continent co ON c.continentId = co.id
JOIN
    Federation f ON co.federationId = f.id
WHERE
    f.name = 'Electronic Sports Europa';

Electronic Sports Europa

Electronic Sports Americas

id Name 1 Andorra 2 United Arab Emirates 3 Afghanistan 6 Albania 7 Armenia 8 Angola 11 American Samoa 12 Austria 13 Australia 15 Åland 16 Azerbaijan 17 Bosnia and Herzegovina 19 Bangladesh 20 Belgium 21 Burkina Faso 22 Bulgaria 23 Bahrain 24 Burundi 25 Benin 28 Brunei 33 Bhutan 35 Botswana 36 Belarus 39 Cocos [Keeling] Islands 40 Democratic Republic of the Congo 41 Central African Republic 42 Republic of the Congo 43 Switzerland 44 Ivory Coast 45 Cook Islands 47 Cameroon 48 China 52 Cape Verde 54 Christmas Island 55 Cyprus 56 Czech Republic 57 Germany 58 Djibouti 59 Denmark 62 Algeria 64 Estonia 65 Egypt 66 Western Sahara 67 Eritrea 68 Spain 69 Ethiopia 70 Finland 71 Fiji 73 Micronesia 74 Faroe Islands 75 France 76 Gabon 77 United Kingdom 79 Georgia 81 Guernsey 82 Ghana 83 Gibraltar 85 Gambia 86 Guinea 88 Equatorial Guinea 89 Greece 92 Guam 93 Guinea-Bissau 95 Hong Kong 98 Croatia 100 Hungary 101 Indonesia 102 Ireland 103 Israel 104 Isle of Man 105 India 106 British Indian Ocean Territory 107 Iraq 108 Iran 109 Iceland 110 Italy 111 Jersey 113 Jordan 114 Japan 115 Kenya 116 Kyrgyzstan 117 Cambodia 118 Kiribati 119 Comoros 121 North Korea 122 South Korea 123 Kuwait 125 Kazakhstan 126 Laos 127 Lebanon 129 Liechtenstein 130 Sri Lanka 131 Liberia 132 Lesotho 133 Lithuania 134 Luxembourg 135 Latvia 136 Libya 137 Morocco 138 Monaco 139 Moldova 140 Montenegro 142 Madagascar 143 Marshall Islands 144 North Macedonia 145 Mali 146 Myanmar [Burma] 147 Mongolia 148 Macao 149 Northern Mariana Islands 151 Mauritania 153 Malta 154 Mauritius 155 Maldives 156 Malawi 158 Malaysia 159 Mozambique 160 Namibia 161 New Caledonia 162 Niger 163 Norfolk Island 164 Nigeria 166 Netherlands 167 Norway 168 Nepal 169 Nauru 170 Niue 171 New Zealand 172 Oman 175 French Polynesia 176 Papua New Guinea 177 Philippines 178 Pakistan 179 Poland 181 Pitcairn Islands 183 Palestine 184 Portugal 185 Palau 187 Qatar 188 Réunion 189 Romania 190 Serbia 191 Russia 192 Rwanda 193 Saudi Arabia 194 Solomon Islands 195 Seychelles 196 Sudan 197 Sweden 198 Singapore 199 Saint Helena 200 Slovenia 201 Svalbard and Jan Mayen 202 Slovakia 203 Sierra Leone 204 San Marino 205 Senegal 206 Somalia 208 South Sudan 209 São Tomé and Príncipe 212 Syria 213 Swaziland 215 Chad 217 Togo 218 Thailand 219 Tajikistan 220 Tokelau 221 East Timor 222 Turkmenistan 223 Tunisia 224 Tonga 225 Turkey 227 Tuvalu 228 Taiwan 229 Tanzania 230 Ukraine 231 Uganda 232 U.S. Minor Outlying Islands 235 Uzbekistan 236 Vatican City 241 Vietnam 242 Vanuatu 243 Wallis and Futuna 244 Samoa 245 Kosovo 246 Yemen 247 Mayotte 248 South Africa 249 Zambia 250 Zimbabwe

id Name 4 Antigua and Barbuda 5 Anguilla 9 Antarctica 10 Argentina 14 Aruba 18 Barbados 26 Saint Barthélemy 27 Bermuda 29 Bolivia 30 Bonaire 31 Brazil 32 Bahamas 34 Bouvet Island 37 Belize 38 Canada 46 Chile 49 Colombia 50 Costa Rica 51 Cuba 53 Curacao 60 Dominica 61 Dominican Republic 63 Ecuador 72 Falkland Islands 78 Grenada 80 French Guiana 84 Greenland 87 Guadeloupe 90 South Georgia and the South Sandwich Islands 91 Guatemala 94 Guyana 96 Heard Island and McDonald Islands 97 Honduras 99 Haiti 112 Jamaica 120 Saint Kitts and Nevis 124 Cayman Islands 128 Saint Lucia 141 Saint Martin 150 Martinique 152 Montserrat 157 Mexico 165 Nicaragua 173 Panama 174 Peru 180 Saint Pierre and Miquelon 182 Puerto Rico 186 Paraguay 207 Suriname 210 El Salvador 211 Sint Maarten 214 Turks and Caicos Islands 216 French Southern Territories 226 Trinidad and Tobago 233 United States 234 Uruguay 237 Saint Vincent and the Grenadines 238 Venezuela 239 British Virgin Islands 240 U.S. Virgin Islands

Packaging

When you're ready to share your mod, it must be packaged as a .zip file with a specific folder structure. To simplify this process, there is a command-line tool that bootstraps everything for you.

You can download the tool here.

Note

Windows may display a security warning because the tool is not code-signed.

To install, click on More Info and Run Anyway.

File Structure

• The name of the .zip file must be the name of your mod.
• The name of the root folder inside the .zip file must be called custom.
• The metadata JSON file contains mod metadata like title, version, and author.
• The root save file is located in custom/saves/save_0.db.

You can view a real example here.

mod-name.zip
└── custom/
    └── saves/
        └── save_0.db
    └── metadata.json

Metadata File

The metadata JSON file must be contained within the custom/metadata.json folder and is used by the app to identify and display your mod correctly.

• name: The display name of your mod.
• version: The semantic version string (e.g.: 1.0.0, 0.3.2-beta.1).
• author: Your name or handle.
• description: A short description of what your mod does.

{
  "name": "MOD NAME",
  "version": "0.0.1",
  "author": "YOUR NAME",
  "description": "MOD DESCRIPTION"
}

Publishing

You can publish your mod in two ways:

1. Fork the modding repository and open up a pull request with your mod added to the mods folder inside this repo.
2. Upload the .zip file to #mod-releases in our discord server.