loot/libloot
0
0
Fork 0
mirror of https://github.com/loot/libloot.git synced 2026-07-27 14:16:01 -07:00
Code Issues Packages Projects Releases Wiki Activity

Replace LOOT wiki links with website links

Browse Source 
The wiki will be removed once v0.9.0 is released.
This commit is contained in:
Oliver Hamlet
2016-04-12 21:37:00 +01:00
parent 1031d9720f
commit 6a21c88c03
3 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CONTRIBUTING.md
+1 -1
View File
@@ -1,7 +1,7 @@
Contributing To LOOT
====================
A general guide to contributing to LOOT, may be found on [LOOT's wiki](https://github.com/loot/loot.github.io/wiki/How-To-Contribute). Information more specific to this repository is found here.
A general guide to contributing to LOOT, may be found on [LOOT's wiki](https://loot.github.io/docs/contributing/How-To-Contribute). Information more specific to this repository is found here.
## Repository Branching Structure
README.md
+1 -1
View File
@@ -10,7 +10,7 @@ LOOT also provides some load order error checking, including checks for requirem
Although LOOT is able to calculate the correct load order positions for the vast majority of mods without any user input, some plugins are designed to load at certain positions in a load order, and LOOT may be unable to determine this from the plugins themselves. As such, LOOT provides a mechanism for supplying additional plugin metadata so that it may sort them correctly.
LOOT is intended to make using mods easier, and mod users should still possess a working knowledge of mod load ordering. See [Introduction To Load Orders](https://github.com/loot/loot.github.io/wiki/Introduction-To-Load-Orders) for an overview.
LOOT is intended to make using mods easier, and mod users should still possess a working knowledge of mod load ordering. See [Introduction To Load Orders](https://loot.github.io/docs/help/Introduction-To-Load-Orders) for an overview.
## Building LOOT
docs/LOOT Readme.html
+4 -4
View File
@@ -221,7 +221,7 @@ figure > div {
<p>While LOOT is able to calculate correct load order positions for the vast majority of plugins using only their content, it cannot do so for all plugins. As such, LOOT provides a mechanism for supplying additional plugin metadata so that it may sort them correctly. An online <em>masterlist</em> is provided to supply metadata for many plugins that need it, while users can make their own metadata additions, which are saved in their <em>userlist</em>.
<p>LOOT is intended to make using mods easier, and mod users should still possess a working knowledge of mod load ordering. See <a href="https://github.com/loot/loot.github.io/wiki/Introduction-To-Load-Orders">Introduction To Load Orders</a> for an overview.
<p>LOOT is intended to make using mods easier, and mod users should still possess a working knowledge of mod load ordering. See <a href="https://loot.github.io/docs/help/Introduction-To-Load-Orders">Introduction To Load Orders</a> for an overview.
<h2 id="install">Installation &amp; Uninstallation</h2>
@@ -469,9 +469,9 @@ figure > div {
<h2 id="contrib">Contributing &amp; Support</h2>
<p>LOOT is very much a community project, and contributions from its users are very welcome, whether they be metadata, translations, code or anything else. The best way to contribute is to <a href="https://github.com/loot/loot.github.io/wiki/How-To-Contribute">make changes yourself</a> at GitHub! It's the fastest way to get changes you want applied, and you'll get your name automatically immortalised in our <a href="http://loot.github.io/credits/">credits</a>.
<p>LOOT is very much a community project, and contributions from its users are very welcome, whether they be metadata, translations, code or anything else. The best way to contribute is to <a href="https://loot.github.io/docs/contributing/How-To-Contribute">make changes yourself</a> at GitHub! It's the fastest way to get changes you want applied, and you'll get your name automatically immortalised in our <a href="http://loot.github.io/credits/">credits</a>.
<p>If you encounter an issue with LOOT, check the <a href="https://github.com/loot/loot.github.io/wiki/LOOT-FAQs">Frequently Asked Questions</a> wiki page in case a solution is available there.
<p>If you encounter an issue with LOOT, check the <a href="https://loot.github.io/docs/help/LOOT-FAQs">Frequently Asked Questions</a> wiki page in case a solution is available there.
<p>Otherwise, general discussion and support takes place in LOOT's official forum thread, which is linked to on <a href="http://loot.github.io">LOOT's homepage</a>.
@@ -481,7 +481,7 @@ figure > div {
<h2 id="credits">Credits</h2>
<p>LOOT is developed on <a href="https://github.com/loot/">GitHub</a>. A full list of GitHub contributors may be found <a href="http://loot.github.io/credits/">here</a>.
<p>LOOT is developed on <a href="https://github.com/loot/">GitHub</a>, and a full list of GitHub contributors may be found <a href="http://loot.github.io/credits/">here</a>.
<p>LOOT's masterlists were largely converted from <a href="http://boss-developers.github.io">BOSS</a>'s masterlists, and so credit is due to the very large number of sources and people who have contributed to them.
<p>In addition, the following are credited with application-related support:
<ul>