454
edits
Mod Creation/Enabling DevTools for the Steam and Epic Clients: Difference between revisions
From Melvor Idle
Mod Creation/Enabling DevTools for the Steam and Epic Clients (view source)
Revision as of 23:09, 14 June 2021
, 14 June 2021final formatting
m (more formatting) |
m (final formatting) |
||
| Line 13: | Line 13: | ||
How to use console commands, scripts, and extensions on Steam. | How to use console commands, scripts, and extensions on Steam. | ||
===Setup=== | ===1. Setup=== | ||
You only have to do this once. | You only have to do this once. | ||
<ol> | <ol> | ||
| Line 38: | Line 38: | ||
</ol> | </ol> | ||
===Loading Scripts=== | ===2.a. Loading Scripts=== | ||
Loading scripts must be run every time the game is opened on Steam. | Loading scripts must be run every time the game is opened on Steam. | ||
<ol> | <ol> | ||
| Line 60: | Line 60: | ||
</ol> | </ol> | ||
===Alternate Variation=== | ===2.b. Alternate Variation=== | ||
The following variant results in a cleaner directory without potential file name clashes. Note that the above does not clash for Combat Simulator + SEMI at the moment. | The following variant results in a cleaner directory without potential file name clashes. Note that the above does not clash for Combat Simulator + SEMI at the moment. | ||
====Additional Setup==== | |||
Do all the normal steps 1-5 of the Setup section then follow the below instructions. | |||
<ol> | |||
<li>Create a directory Extensions in the Melvor Idle installation directory.</li> | |||
<li>Make new directories for the extensions and scripts. e.g.</li> | |||
<pre> | |||
Extensions/ | Extensions/ | ||
Greasy Fork/ | Greasy Fork/ | ||
| Line 80: | Line 84: | ||
scripts/ | scripts/ | ||
styles/ | styles/ | ||
</pre> | |||
<li>Place the icons, styles, and source (i.e. scripts or sources) directories of the extracted extensions in the respective created directories.</li> | |||
</ol> | |||
====Alternate Variation Loading Scripts==== | |||
If you followed the alternate variation setup steps, you will have to load scripts slightly differently. | |||
<ol> | |||
<li>Open the game and load a character.</li> | |||
<li>Open the dev tools console (F12).</li> | |||
<li>Set the context of the console to game.</li> | |||
<ul> | |||
<li>The top left of the console has a dropdown: change it from top to game (steam.melvoridle.com). After doing this, you can use the console.</li> | |||
</ul> | |||
<li>Load the scripts and extensions you placed in the installation directory before.</li> | |||
<pre> | |||
[ | [ | ||
// own | // own | ||
| Line 102: | Line 119: | ||
//'Extensions/SEMI-steam/styles/semi.css', | //'Extensions/SEMI-steam/styles/semi.css', | ||
].forEach(cssFile => $(document.head).append(`<link rel="stylesheet" href="${chrome.runtime.getURL(cssFile)}">`)); | ].forEach(cssFile => $(document.head).append(`<link rel="stylesheet" href="${chrome.runtime.getURL(cssFile)}">`)); | ||
</pre> | |||
<li>If you are using extensions, edit the main extension script so all source files and icons can be found.</li> | |||
<ul> | |||
<li>e.g. edit the paths in contentScript.js for Combat Simulator and SEMI.js for SEMI</li> | |||
<pre> | |||
Combat Simulator: | |||
-icons/ -> Extensions/MICS-steam/icons/ | |||
-sources/ -> Extensions/MICS-steam/sources/ | |||
SEMI: | |||
-icons/ -> Extensions/SEMI-steam/icons/ | |||
-scripts/ -> Extensions/SEMI-steam/scripts/ | |||
</pre> | |||
</ol> | |||
==Auto-loading Scripts in Steam== | ==Auto-loading Scripts in Steam== | ||
