Note that for Skyrim, multiple copies or Total Conversions will all edit the same plugins.txt file, and so they lack the level of independence that is achievable for other games.
-
If you encounter an issue, check the Frequently Asked Questions wiki page in case a solution is available there. If no solution for your problem is listed there, please seek further support in an official LOOT thread (see Contributing To LOOT). +
LOOT is very much a community project, and contributions from its users are vital to its upkeep, whether they be metadata, translations, code or anything else. The best way to contribute is to make changes yourself at GitHub! It's the fastest way to get changes you want applied, and you'll get your name automatically immortalised in our credits. +
If you encounter an issue with LOOT, check the Frequently Asked Questions wiki page in case a solution is available there. -
LOOT is very much a community project, and contributions from its users are vital to its upkeep. The best way to contribute is to make changes yourself at GitHub! It's the fastest way to get changes you want applied, and you'll get your name automatically immortalised in our credits. - -
Otherwise, general discussion takes place in LOOT's official forum threads. These are linked to at the bottom of LOOT's homepage. +
Otherwise, general discussion and support takes place in LOOT's official forum threads. These are linked to at the bottom of LOOT's homepage.
If you want to submit metadata, the easiest way to do so is to add the metadata to your own LOOT install, then use the Copy Metadata As Text feature to easily get it in a form that you can then edit into a masterlist on GitHub or post in the official forum threads.
Information on dirty plugins is very welcome, but for such information to be useful we require at least the filename and the CRC of the dirty plugin. The CRC may be calculated using Wrye Bash or 7-zip, with other sources being unverified as correct. In the case of 7-zip, the CRC checksum for data
is the one required. In addition to the CRC, the number of records removed (the ITM count) and/or undeleted (the UDR count) are also welcome.
-
LOOT supports translation into other languages, with the following limitations: -
Translations are best submitted through GitHub's forking system. You will need to fork the LOOT source code repository. All file paths given below are relative to the base folder of that repository. -
To translate LOOT's installer: -
src/installer.nsi in a text editor of your choice.
- English Strings. Copy and paste this section into a new text file, and translate the quoted strings, replacing the English text. For the lines beginning
VIAddVersionKey, only translate the second quoted string.
- File->New catalogue from POT file...and choose the template file at
resources/l10n/template.pot. In the Catalog propertiesdialog, just click
OKwithout changing anything. -
loot.po translation file in the relevant subdirectory of resources/l10n, then select Catalogue->Update from POT file...and choose the template file you downloaded. Click
OKin the
Update summarydialog. -
Some languages may use different words or phrases for different contexts where only one word or phrase may be used for all contexts in English. While no contextual information is supplied to translators by default, it can be added on request. To request the addition of contextual information to a text string, create an issue for your request in LOOT's issue tracker, quoting the structure that contains the string for which you are requesting contextual information. -
Some strings to be translated may contain special characters. Different types of special character that may be encountered are: -
\. Backslashes must be escaped using another backslash, so if you wanted to display a single backslash \, you would put \\ in your translated string.
- ". Double-quotation marks must be preceded by a backslash, ie. \", or LOOT will crash when it tries to display the string.
- %1%. If formatting placeholders are used in the untranslated string, they must all be present in the translated string, or LOOT will crash when it tries to display the translated string. Placeholders can be moved around so that the sentence makes grammatical sense in the target language.
-loot.po in resources/l10n/<locale>/LC_MESSAGES/, where <locale> is your language's locale code.
-LOOT is developed by a team on GitHub, with contributions from users. A full list of GitHub contributors may be found here. An up-to-date list of team members may be viewed on the project wiki. Unless otherwise noted, team members can be contacted on the Bethesda Softworks Forums or on The Nexus Forums via the private messaging system.
LOOT's masterlists were largely converted from BOSS's masterlists, and so credit is due to the very large number of sources and people who have contributed to them.