mirror of
https://github.com/loot/loot.github.io.git
synced 2026-07-27 14:13:30 -07:00
Oliver Hamlet
c1194ac2ec
Hugo is a lot easier to work with locally (especially on Windows), and because it's not natively supported by GitHub Pages, it gets deployed using GitHub Actions, so it's also easier to keep the version of Hugo in sync between local builds and deployments. I've compared the generated _site/ and public/ folders and they look equivalent, except that Hugo also generates a sitemap: that can be disabled, but it's good to have.
18 lines
992 B
HTML
18 lines
992 B
HTML
---
|
|
layout: page
|
|
title: Quickly Testing Your Masterlist Changes
|
|
weight: 4
|
|
aliases:
|
|
- Quickly-Testing-Your-Masterlist-Changes.html
|
|
---
|
|
|
|
<p>You can easily test your masterlist changes <em>before</em> syncing them to the online repository, using the method detailed below, which makes LOOT use a local masterlist of your choosing rather than the online one.</p>
|
|
|
|
<ol>
|
|
<li>Run LOOT, open the <b>File</b> menu and select <b>Settings...</b>.</li>
|
|
<li>Select the game you want to test and, in the <b>Masterlist Source</b> field, enter the path to your local masterlist. E.g., if you have the Skyrim masterlist in a repository at <code>C:\foo\bar\skyrim\masterlist.yaml</code>, then put that in the field.</li>
|
|
<li>Save your settings, and the settings dialog will automatically close. LOOT will now update using your local masterlist instead of the online one.</li>
|
|
</ol>
|
|
|
|
<p>Note that LOOT won't keep your local masterlist synced with the online one, so you'll have to do that yourself.</p>
|