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

Update dev docs to latest.

Browse Source
This commit is contained in:
Oliver Hamlet
2015-01-04 17:19:19 +00:00
parent 0d4781ab6a
commit 34babdf857
2 changed files with 13 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/dev/LOOT Metadata Syntax.html
+7 -11
View File
@@ -77,9 +77,7 @@ html {
font-size: 1.429rem;
/*letter-spacing: 0.005em;*/
}
.subhead, h4,
#summary > h1,
html /deep/ paper-item {
.subhead, h4 {
font-weight: 400;
font-size: 1.143rem;
line-height: 1.75;
@@ -87,9 +85,7 @@ html /deep/ paper-item {
/* line-height: 1.5; */
/*letter-spacing: 0.01em;*/
}
.button,
html /deep/ paper-tab,
html /deep/ paper-button {
.button {
font-weight: 500;
font-size: 1rem;
text-transform: uppercase;
@@ -105,17 +101,17 @@ a:hover {
text-decoration: underline;
}
/* Tables */
html /deep/ table {
table {
border-collapse: collapse;
width: 100%;
background-color: #E8EAF6;
}
html /deep/ table td, table th {
table td, table th {
vertical-align: top;
text-align: left;
padding: 8px 16px;
}
html /deep/ table th {
table th {
border-bottom: 1px solid rgba(0, 0, 0, 0.12);
}
@@ -436,14 +432,14 @@ nav: 0
<li>One of the plugins has a priority greater than or equal to 1,000,000. In this case, only the modulo (ie. remainder when divided) with 1,000,000 is used when comparing plugin priority values &ndash; the rest is only used to signify that the plugin should be compared against all others.
</ul>
<p>For example, <code>priority: 153000352</code> and <code>priority: 352</code> have equal values when compared, but a plugin with the first priority will be compared against all others, while a (non-empty) plugin with the second priority will be compared against only those it conflicts with.
<p>A plugin with a higher priority value will load after a plugin with a lower priority value. Value can be anything in the range <code>-2000000000</code> to <code>2000000000</code>, and if unspecified defaults to <code>0</code>.
<p>A plugin with a higher priority value will load after a plugin with a lower priority value. The value can be anything in the range <code>-2000000000</code> to <code>2000000000</code>, and if unspecified defaults to <code>0</code>.
<tr><td><code>after</code><td>file list<td>&#x2717;<td>An unordered list of plugins that this plugin must load after, but which are not dependencies. Used for resolving specific compatibility issues and by user rules for specifying custom plugin positions.
<tr><td><code>req</code><td>file list<td>&#x2717;<td>An unordered list of files that this plugin requires to be present. This plugin will load after any plugins listed. If any of these files are missing, an error message will be displayed. Intended for use specifying implicit dependencies, as LOOT will detect a plugin's explicit masters itself.
<tr><td><code>inc</code><td>file list<td>&#x2717;<td>An unordered list of files that this plugin is incompatible with. If any of these files are present, an error message will be displayed.
<tr><td><code>msg</code><td>message list<td>&#x2717;<td>The messages attached to this plugin. The messages will be displayed in the order that they are listed.
<tr><td><code>tag</code><td>tag list<td>&#x2717;<td>An unordered list of Bash Tags suggested for this plugin. If a Bash Tag is suggested for both addition and removal, the latter will override the former when the list is evaluated.
<tr><td><code>url</code><td>location list<td>&#x2717;<td>An unordered list of locations for this plugin. If the same version can be found at multiple locations, only one location should be recorded. This metadata is not currently used by LOOT.
<tr><td><code>dirty</code><td>dirty info list<td>&#x2717;<td>An unordered list of dirty info structures for this plugin.
<tr><td><code>dirty</code><td>dirty info list<td>&#x2717;<td>An unordered list of dirty info structures for this plugin. Plugin entries with regular expression filenames <strong>must not</strong> contain dirty info.
</table>
<p><strong>Each plugin must have only one matching non-regex entry.</strong> If multiple non-regex entries exist with the same <code>name</code> value, all but the first will be ignored. A plugin may match any number of regex entries though, and their metadata will be merged, with later entries being merged into earlier entries as detailed in the table below. Merging only takes place if both entries have their <code>enabled</code> value set to <code>true</code> (which is the default if unspecified).
docs/dev/LOOT Readme.html
+6 -10
View File
@@ -77,9 +77,7 @@ html {
font-size: 1.429rem;
/*letter-spacing: 0.005em;*/
}
.subhead, h4,
#summary > h1,
html /deep/ paper-item {
.subhead, h4 {
font-weight: 400;
font-size: 1.143rem;
line-height: 1.75;
@@ -87,9 +85,7 @@ html /deep/ paper-item {
/* line-height: 1.5; */
/*letter-spacing: 0.01em;*/
}
.button,
html /deep/ paper-tab,
html /deep/ paper-button {
.button {
font-weight: 500;
font-size: 1rem;
text-transform: uppercase;
@@ -105,17 +101,17 @@ a:hover {
text-decoration: underline;
}
/* Tables */
html /deep/ table {
table {
border-collapse: collapse;
width: 100%;
background-color: #E8EAF6;
}
html /deep/ table td, table th {
table td, table th {
vertical-align: top;
text-align: left;
padding: 8px 16px;
}
html /deep/ table th {
table th {
border-bottom: 1px solid rgba(0, 0, 0, 0.12);
}
@@ -394,7 +390,7 @@ var {
<li>The <var>language</var> is the language LOOT runs in that the message will be displayed for. This field has no effect for user-added messages, as they cannot contain multiple localisations, and LOOT will always display messages that have only one localisation, even if it doesn't match the current language.
</ul>
<p>If a message's condition determines that it should not be displayed, then it will not be displayed, no matter the language. However, if a message's condition determines that it should be displayed, but the language is specified and doesn't match the language LOOT is running in, the message will not be displayed.
<tr><td>Bash Tags<td>A list of Bash Tags. These are used by Wrye Bash when generating a Bashed Patch. LOOT's metadata includes Bash Tag addition and removal suggestions, and any Bash Tags that came with the plugin are also displayed.
<tr><td>Bash Tags<td>A list of Bash Tags. These are used by Wrye Bash when generating a Bashed Patch, and are detailed in <a href="https://wrye-bash.github.io/docs/Wrye%20Bash%20Advanced%20Readme.html#patch-tags">Wrye Bash's readme</a>. LOOT's metadata includes Bash Tag addition and removal suggestions, and any Bash Tags that came with the plugin are also displayed.
<p>As LOOT can suggest Bash Tags be added or removed, it is possible for the same Tag to appear twice, being suggested for addition and removal. In such cases, removal overrides addition.
<p>Each Bash Tag has three fields:
<ul>