Mods
Mods change Longshot: new textures and music, a HUD of your own, a timer, a randomizer, a photo mode. This page is for players: what mods can do, how to install them, how to turn them on and off in the game, what their permissions mean, and what to do when one goes wrong. To make mods, start with your first mod.
Script mods are new. Mods that replace the game’s files work today. Script mods (mods with a script, which ask for permissions) run in the game, but few have been played with yet: tell us what goes wrong (below).
What mods can do
| Kind | What it does | For example |
|---|---|---|
| File mods | Replace or add the game’s own files: textures, models, texts, sounds, music | HD textures, a new soundtrack, a retranslation |
| Texture packs | Swap the game’s textures for PNG images, at any resolution | A sharper font, a recoloured outfit |
| Script mods | Read the game while you play and react to it, through Longshot’s API, with your permission | A HUD with your hearts and rupees, a speedrun timer, an item tracker, a minimap, a photo mode, a damage multiplier, a chest randomizer |
| Content mods | Add to the game: new items, characters, placements and texts | A new kind of rupee |
| Code mods | Change the game’s own code: patches made for emulators, native C or C++ mods, mods with hooks of their own | A frame rate patch, a new menu page |
A mod can be more than one kind: a script mod can bring its own textures, or add content. The example mods show what script mods can do, each in a few lines.
Before you start
- Back up your saves. A mod can change what gets saved, and removing it later doesn’t undo progress made with it. See where Longshot keeps them.
- The game can stay open. It sees a mod you add, change or remove while it runs, and uses it at once where it can (Changes while you play).
- Each version has its own mods. Each version you build has its own game folder, with its own
modsfolder. An update of the game keeps it. A mod made for an older version of the game may need an update of its own.
Install a mod
From the launcher
Select the version and choose Mods. The launcher’s Mods page lists that version’s mods in the order the game loads them, with what each holds and its switch, and:
- Add a folder… or Add a .zip… copies a mod made for an emulator into the
modsfolder as it is (itsromfsfolder, and itsexefsandcheatsfolders when it has them); - Move up and Move down set the order (below);
- a mod’s settings can be changed there with the game closed;
- Profiles keep several lists of which mods are on, over the one
modsfolder; - Play without mods starts the game once with every mod off (Safe start).
The game can stay open: it sees what the launcher adds, removes or switches while you play (Changes while you play).
The mod portal is not open yet. The page has a Browse the mod portal section for it, which says so. Until it opens, you install a mod from a file or a folder.
By hand: the mods folder
- Open the game folder. In the launcher, select the version and choose Open folder.
- Make a
modsfolder there, besidebin, if there isn’t one yet. - Put the mod in it, as it came:
- a package,
something.lsmod: copy the file intomodsas it is (it is a zip with the mod’smod.jsonin it; don’t unpack it); - a folder with a
mod.json: copy the folder intomods; - a mod made for an emulator: one folder per mod, with its
romfsfolder in it (below).
- a package,
- Turn it on in the Mods tab. The game finds it while it runs, or at its next start. A mod with a script stays off until you have seen what it asks for.
Mods made for emulators
Most mods made for emulators already come in the layout Longshot reads: unpack each into a folder of its own inside
mods, with its romfs folder (and its exefs and cheats folders, when it has them):
mods/ 01-hd-textures/ romfs/ ... 02-new-music/ romfs/ ...Deeper layouts work too, such as mods/contents/<title id>/<name>/romfs, and a pack made for a console’s SD card, with
its atmosphere/contents/... and atmosphere/exefs_patches/<name>/ folders. Unpack a .zip of such a mod first: the
game reads a .zip only when it has a mod.json in it, as a package does.
romfs, the game’s files, works at the next start.exefs, patches to the game’s code (.ips,.pchtxt) and code modules, asks you first, then goes in at the next build (Code mods).cheatsare listed under their mod in the Mods tab and switched there, at once. Cheats that change the game’s code are not supported, and are listed as such.
The Mods tab
Open Longshot’s menu in the game (F1) and go to the Mods tab. It is there when you have mods.
Back is Esc on the keyboard, B (or the back button) on a controller, or a right click, everywhere in the tab.
The list
The tab lists your mods in two groups: Built in, the mods that come with Longshot (below), always first, then Your mods, the ones you installed, in the order the game loads them. Up and Down choose a mod; Enter, A or a click opens its page; Back closes the menu.
Each line is the mod’s name and its status:
| Status | Means |
|---|---|
| On | It is on, and running (or its files are in the game) |
| Off | It is off |
| Faulted | It stopped for its faults, or its start failed (A mod stopped) |
| On, waits for permissions | It is on, but you have not granted what it needs yet |
| On, not loaded | It is on, but cannot load: its page says why (Not loaded) |
and after it, when it applies: , waits for restart (its switch takes effect at the next start), , needs a rebuild (its code goes in at the next build), , unsafe (native code, hooks of its own, or an unsafe permission: Unsafe mods). A red diamond marks a fault or an unsafe mod.
Two more lines appear when they apply: Safe start (“Your mods are off”) at the top when the game was started without mods (Safe start), and Restart the game now at the bottom while a switch waits for a restart.
A mod’s page
Its name, then these rows, in this order:
- Enabled: Off or On. Left and Right, Enter, or a click on a half switch it. A code mod shows its warning first: Enter accepts it, Esc or Left keeps the mod off. Turning off a library that other mods need asks first: press Off again within 5 seconds. A script mod switches at once; the others wait for a restart or a build (Turning mods on and off).
- Permissions: “N of M granted”. Enter opens its page (below).
- Settings: the mod’s own options, drawn as the menu’s own rows, then Its own settings page (Open) for a mod that has one. A mod that plays sounds also has a Sound volume row.
- Cheats, for a mod that was on when the game started and has cheats: each switched at once.
- About: Version (and its author), State, Has (what the mod holds) and Notes. The help box shows each in full.
- Start
again , for a mod that faulted. - Reload, in dev mode, for a running folder mod.
- Move in the list (not for built-in mods): back to the list with the mod picked up. Up and Down move it; Enter or Back puts it down (When two mods change the same file).
Back returns to the list, with that mod selected.
The Permissions page
One row per permission the mod has, in the words the prompt uses, with a diamond for its risk (gold for medium and high, red for unsafe); the help box shows the permission’s name and its risk (Low, Medium, High or Unsafe).
- Optional permissions (the ones a mod asks for only when it needs them) say Granted or Not granted, and switch. Granting one asks twice: press Enter again within 5 seconds. Taking one back is immediate, and the mod hears it.
- Required permissions say Required, granted or Required, not granted: they go with the mod’s switch.
- A built-in mod’s permissions are shown, and cannot be changed.
Back returns to the mod’s page.
Which mods are on, their order and what you granted are kept in mods.json, beside your settings file
(longshot_options.ini), so an update of the game keeps them. The launcher’s Mods page edits the same list.
Permissions
A script mod reaches the game only through Longshot’s API, and only with your permission. When you turn one on, the game asks, over everything else on the screen:
Permissions
Heart HUD 1.0.0 asks to:
- Can see what happens in your game
- Can draw on your screen over the game
You can see them in the Mods tab: the mod’s Permissions. Not now keeps the mod off.
Not Now · Allow
- Not Now is chosen first. It keeps the mod off; turning it on again asks again.
- Allow grants what the list says, and the mod starts.
- Only you can answer it. A mod cannot draw over the window or press its buttons, and it ignores what you were pressing in the game when it appeared.
- It asks again when a new version of the mod asks for more, and when a running mod asks for one of its optional permissions, the ones it needs only for one of its features (“asks, while it runs, to”). You can take those back on the mod’s Permissions page.
Each line is marked by its risk:
| Risk | Means | For example |
|---|---|---|
| low (no mark) | It reads the game, or shows or plays things of its own. It cannot change your game | “Can see what happens in your game”, “Can draw on your screen over the game”, “Can keep its own data on this PC”, “Can play its own sounds” |
| medium | It changes your game or what gets saved, within the limits Longshot sets, or talks to one server | “Can change your game and what gets saved”, “Can press buttons for you, and change what your controller does”, “Can give you items, and keeps a list of what it gave”, “Can talk to wss://example.org” |
| high | It changes much more, or reaches far | “Can change the characters, enemies and things around you”, “Can talk to any server on the internet”, “Can talk to devices on your home network”, “Can read the game’s own files on this PC” |
| unsafe, only for mods you trust | It has the run of the game (below) | “Can read all of the running game’s memory”, “Can change the running game’s memory directly”, “Hooks the game’s own code where Longshot never named a place” |
Every permission, and what it lets a mod do, is in the permission table.
Your game’s data stays on your PC. A mod that can read the game’s memory or its files cannot also have the network: the game refuses such a mod before it loads.
Script mods run in a sandbox. A script mod can do only what its permissions let it. While one is on, the game also confines itself, on Linux and on Windows: it can read its own folder and write its own folders (saves, caches, logs), nothing else of yours, and it has no network of its own. What needs the network or your desktop (sending a crash report, opening a link, a mod’s granted servers, the Discord status’s connection) goes through a small helper process beside the game. On Windows the first start with a script mod takes a few seconds longer.
Unsafe mods
Some mods go past what the API checks. Each is marked in the Mods tab, and asks you first, in plain words:
- Mods with code patches (an
exefsfolder of.ipsor.pchtxtfiles, or code modules,exefs/subsdk*) change the game’s code. Longshot cannot check or limit what they do: once built in, such code runs with everything the game can do. It can crash the game or damage a save, and a mod from somewhere you don’t trust could do worse. - Mods with hooks of their own (a
sites.tomlin their folder) and mods that read or write the game’s memory are marked Unsafe: “full access to the running game, only for mods you trust”. - Native mods bring C or C++ that the build compiles on your PC. They are marked Unsafe, native code, and their warning says: “It runs as you, with full access to your PC: your files, your network, your other programs, and the game. Longshot cannot check, limit or stop it. Only a mod whose source you trust is safe.”
Such a mod is off when the game finds it. Turning it on shows its warning: accept it to turn the mod on, or leave it off. Longshot remembers what you accepted by the contents of the mod’s code, so a new version of the mod, or any change to its code, turns it off and asks again.
Turning mods on and off
When a switch takes effect depends on what the mod holds, and its line in the tab says which:
- A script mod and nothing else (a script, no game files, no textures) switches at once, while you play. Off stops it within the frame: everything it shows goes, the camera and the controller go back to the game, and what it made ends. On starts it again from the beginning, asking first for any permission it lacks. Its own data and its settings are kept either way.
- Every other mod (game files, a texture pack, a script mod that also brings files, and a mod one of those needs) says “Takes effect when you restart”: its files are put together when the game starts. Restart the game now appears at the bottom of the list, and closing the menu offers the restart too, naming each mod you switched.
- A code mod waits for a build (below).
A mod that needs another. A mod can need another (a library). Turning the library off stops the mods that need it too, so the tab asks first: press Off again within 5 seconds to turn them all off. They stay on in the list and say that a mod they need is off; turning the library back on starts them again by themselves.
Changes while you play
The game watches the mods folder and the list while it runs, so you don’t have to close it to add a mod from the
launcher, or to copy one in by hand:
- A mod added appears in the Mods tab within a second, switched as the launcher’s list says (a mod with a script is off until you turn it on and have seen what it asks for), also when it is the first mod of a game started with none. A script mod starts at once, asking first for any permission it lacks, when the game is running in its sandbox, which it does when a script mod of yours was on as it started (the built-in Discord status does not count). If none was, its line says “Restart the game to start it (it runs confined)”: scripts only ever run in the sandbox, and closing the menu offers the restart. The same goes for a script mod switched on in the Mods tab or in the launcher. A mod of game files alone (a mod made for an emulator, or a folder with no script) is used from the next time the game loads those files: re-enter the area. Anything else (a code mod, cheats, a texture pack, a mod with a content module) says “Found while the game runs: it loads at the next start”.
- A mod updated in place: a script mod reloads by itself; game files are used from their next load. If its
mod.json, its code or its cheats changed, its line says “Changed while the game runs: … Restart the game to apply it”, and closing the menu offers the restart. - A mod removed stops, its files are no longer used, and its line says so until the next start.
- A switch changed in the launcher applies as a switch in the Mods tab does: at once for a script mod, else at the next start.
- In a co-op room (once co-op is in Longshot) nothing changes while you play: what you change waits until you leave the room.
A file the game has already loaded keeps its old version until it loads it again, and a file that grew more than the game set room for at the start (or a new file of a kind the game sizes ahead) waits for a restart; the mod’s line says so.
To have the game not watch at all (every change then waits for the next start), start it with the environment variable
HOS_MODS_WATCH=0.
With the game closed, you can also rename a mod’s folder so that it starts with _ or - (_02-new-music).
Everything inside it is then left out, and the mod is not in the tab. Remove the _ to bring it back.
Code mods need a build
Longshot builds the game’s code ahead of time, so a patch to the code, a native mod or a mod’s own hooks cannot go in at a start. They go in when the game is built:
- Put the mod in
modsas any other. It is off when the game finds it. - In the Mods tab, turn it on and accept its warning.
- Build the game again from the launcher. The build reads your mods and their order, and builds in the code of the mods that are on and accepted. A native mod’s code takes seconds; the game itself is not translated again.
- Start the game. The Mods tab says, for each code mod, whether its code is in the game or still waits for a build.
Until that build, none of such a mod is used: not its code, and not its files or cheats either. Once a build has taken a mod’s code in, turning it off and on is a restart, with no build. Build again after adding or removing a code mod, or after changing its files: the tab says when a mod waits for one.
Some code mods are switched only by a build, and the tab says so: a mod with a code module, and, where three or more mods change one function of the game, the extra ones. A mod with a patch to a place where Longshot itself changes the game’s code (widescreen, the field of view, the upscalers’ camera jitter) is left out whole, and the tab names the place.
Built-in mods
Some of Longshot is written as mods. They come with every version, are listed under Built in in the Mods tab, and always load first. You cannot uninstall them, and they hold only the permissions they list, granted without a prompt. A built-in mod’s files are checked against the build each time it starts, so a mod you install cannot pass for one.
The mod inspector
The mod inspector shows what your mods are doing. It is on whenever you have a mod. Press F8 to open it (you can bind another key, or turn it off, on its page of the Mods tab). It opens over the whole screen and takes the keyboard and the controller while it is open, so the game waits: the arrows or the D-pad move, Enter or A presses, and Esc or B closes it. Along its top, cards show the mods’ time this frame and over a second, how many are running, their faults and their memory, in green, amber or red against their budgets; Pause holds the numbers still so you can read a spike. It has three tabs:
- Mods: every mod in a table, with what it is doing (running, starting, waiting for permissions, stopped by faults, did not start, off, not loaded), how much of each frame its script takes against its budget, its faults and its memory, and a totals row. Click a column’s header to sort by it. Beside the table is the mod you choose in it: Restart for a mod that stopped, Turn off or Turn on, its numbers, a graph of its last 120 frames (point at a bar to read that frame, click to mark it), its last fault and its last slow frame broken down by where the time went, and its log.
- Log: every mod’s last lines together, filtered by mod and by level.
- Frame: every mod’s last 120 frames stacked across the screen, so you can see which mod made a frame slow.
It remembers its tab, its sort, the mod you chose and its filters. Its Corner line setting shows a short line
(mods: 1.2 ms, 0 faults) in the top right corner of the screen, always. With its window closed, the inspector costs
next to nothing.
The Discord status
Longshot’s built-in mod Discord status shows “Playing Longshot” in your Discord status, with where Link is, his age, hearts, Gold Skulltula tokens and pieces of heart, and the time played, while the Discord app runs on this PC. It comes with Longshot and runs in every game, with or without your mods (and in Safe start). While Discord is not running it only looks for it every 15 seconds.
To turn it off, switch Discord status off in the Mods tab (Mods → Built in), as any mod: it then does not run at all. Its settings are on its page there:
| Setting | What it sets | Default |
|---|---|---|
| Status text | the status’s two lines, a template | {location|{location} - {age}{break}{hearts|❤️ {hearts}/{max_hearts} · }{skulltulas|🕷️ {skulltulas} · }{heart_pieces|💗 {heart_pieces}}}{!location|{version} {build}{!version| {commit}}} |
| Picture | the large picture: an art asset’s name in the Discord application, or an https:// link to a picture |
longshot |
| Picture’s text | the picture’s text, shown on hover, a template | Longshot {version} {build}{!version| {commit}} |
| Discord application id | the Discord application: the bold name and its art | Longshot’s |
| Let mods set my Discord status | whether your other mods may put their own lines in the status | on |
The fields: {location}, {age}, {map} (the game’s own name for it), {hearts}, {max_hearts}, {rupees},
{skulltulas}, {heart_pieces}, {version} (v3.0.0), {build} (RC7, N486, nothing on a release), {commit} and
{release} (all of it, as the menu shows it). {break} starts the second line. {location|...} shows what is inside
only when there is a location, {!location|...} only when there is none (any field works, and they nest); an empty
field takes its brackets and spaces with it. Write a brace as {{. An empty Text shows only the picture and the time.
Mods can set your Discord status. A mod you install may show its own lines there (a fishing tally, a speedrun’s
split): when several do, the one that asks with the highest priority shows, and your usual status comes back when none
does, or when that mod is turned off. A mod can change only the two lines and the small picture (and the time the
status counts from), never the large picture, its text or the application. The game’s log says which mod sets it
(Discord: the status is ...'s now). Turn Let mods set my Discord status off to keep it to Longshot’s own.
Before, the status was the Insert menu’s Gameplay → Discord status row and the discord_status=, discord_text=,
discord_image=, discord_image_text= and discord_app_id= lines of longshot_options.ini. The row is gone; at the
mod’s first start a discord_status=0 you had switches it off in the Mods tab (so a status you had turned off stays
off), and each of the other lines becomes its setting, once; from then on the Mods tab is what counts.
Safe start
When a mod stops the game from starting, or you want to check whether a problem comes from a mod, start without mods:
Play without mods, on the version’s Mods page in the launcher. It starts the game once with every mod off, without
changing your list: no mod files, no cheats, no scripts, and no built-in mods but the Discord status (the mod inspector
is off too). The Mods tab’s first line then says Safe start: “Your mods are off”. The Discord status keeps working.
Without the launcher, start the game with the environment variable HOS_NO_MODS=1 for the same.
Code that a build put into the game stays in it until the next build: to take a code mod out for good, turn it off and build again.
Mods in co-op
Co-op is not in Longshot yet (#68). Mods already say who in a room will need them:
- Only you: most HUDs, timers and trackers. Your own choice; nobody else needs it.
- Everyone, at the same version: a mod that changes the game or adds to it (a randomizer, new items, damage rules). A mod that changes the world everyone plays in can’t be one player’s choice.
- Only the host.
How a room compares its players’ mods comes with co-op itself.
When two mods change the same file
The one lower in the list wins. Move a mod with Move in the list, on its page in the Mods tab, or on the launcher’s
Mods page; the new order applies at the next start (for script mods too). Until you move something, the list is in the
order of the mods’ folder names inside mods, ignoring case, so numbering the folders (01-..., 02-...) still sets
it: here 02-new-music wins over 01-hd-textures for any file they both have. Files that only one mod has are used
either way, and the tab says how many of a mod’s files a lower mod takes.
Many of the game’s files are archives: one file that holds many (an actor’s pack, the menus’ layouts, a language’s texts). When two mods each change such an archive, Longshot serves one archive with each mod’s changes in it, so both mods work; only where both changed the same file inside it does the lower mod win.
Mods that make files bigger (HD textures) work together too. The game sets aside a fixed amount of memory for each of its files, in a resource size table, and a mod with larger files ships that table with its entries grown. You don’t have to combine tables yourself: at each start Longshot makes one table from the game’s and every enabled mod’s, and raises the entry of any mod file bigger than its entry says. The first start after you add large mods can take a few seconds longer while their files are measured.
Troubleshooting
A mod stopped
A script mod that keeps failing is stopped for the rest of the session: three faults in a minute. A fault is an error in its script, or a moment its script ran too long (a script may take 5 ms at a time and 8 ms of a frame, so a slow mod can’t make the game stutter for long). Its line in the Mods tab says Faulted, its page’s State says why, and the mod inspector shows its last fault.
- Start
again , on the mod’s page (or Restart in the inspector), starts it afresh. If it fails again, it stops again. - A mod that stops in the same place each time has a bug: report it to its author.
- A mod that is slow only while the PC is busy (short of memory, or building in the background) may run fine once the PC is free: the log’s line for the fault says how much of the time was the mod’s own.
“Not available for your game version”
A mod can need a part of the game that Longshot has not found in your version of the game: a place in the game’s code the mod hooks, or a feature of the API that depends on one. Such a mod stays off, its line names what is missing, and the rest of your mods run. There is nothing to fix on your side: the mod, or Longshot, needs an update for your version. The same goes for a code patch made for another version of the game, which is left out.
“On, not loaded” and “On, waits for permissions”
The mod’s page says why, under About. The common reasons:
| It says | What to do |
|---|---|
| A mod it needs is off, or not installed | Turn that mod on, or install it |
| It needs another Longshot release, or another API version | Update Longshot, or get the version of the mod made for yours |
| It conflicts with another mod (both claim the same thing, or one says they don’t work together) | Turn one of the two off |
| Its permissions are not granted | Turn it on again and answer the prompt |
| It waits for a build | Build the game again (Code mods) |
The log
The game writes what it does with mods to longshot_log.txt, in the game folder’s logs folder (the launcher’s Open
folder). The run before is in longshot_log.1.txt.
| The log says | It means |
|---|---|
mods: 2 mods from ... |
The mods found, and the folder they came from |
mods: none in ... |
A mods folder with no mod in it: check that each mod has its romfs folder, or its mod.json |
mods: 01-hd-textures: 154 RomFS files (...) |
That mod is on, with this many files |
mods: ...: off (the Mods tab) |
A mod you switched off on the tab |
mods: ... is off (its name starts with _) |
A folder you turned off by its name |
mods: <id>: not loaded: ... |
A mod that did not load, and why |
script runtime: started <id> <version> ... |
A script mod started |
mod runtime: <id>: ... |
A line a script mod wrote |
script runtime: <id>: fault in ... |
An error in a script mod, or a slow moment, and where |
script runtime: <id> stopped after 3 faults in a minute; ... |
A script mod stopped, with its last fault |
mods: ...: ExeFS ...: built into the game |
That code patch is in this build of the game |
mods: ...: ExeFS ...: not in the game yet: ... |
That code patch waits for a build |
sandbox: ... |
What the game’s sandbox did, while a script mod is on |
No mods: ... mods from line means the game found no mods: no mods folder in this version’s game folder, or nothing
in it.
Something stops working only while a script mod is on (a controller, the overlay, the sound): start once with the
environment variable HOS_SANDBOX=0 to check whether the sandbox is the cause, and report it with both logs.
Report a broken mod
- A mod that misbehaves: tell its author, with the mod’s name and version (its page in the Mods tab), what you did,
and
longshot_log.txtfrom that run. Its lines carry the mod’s id. - A built-in mod that faults or stops says in the log that it is a bug in Longshot (“please report it with this
log”). So does a
HostErrorin any mod’s line. Report those to us, and anything else that goes wrong with every mod or with none: Gameplay → Bug report in the menu gathers the log for you.
Never attach game files, keys or saves to a report.
Uninstalling
- Close the game.
- Delete the mod from the
modsfolder: its folder, its.lsmodfile, or its.zip. - Start the game. The mod is gone from the Mods tab.
To keep a mod but not use it, turn it off instead, or rename its folder to start with _. Uninstalling a mod does not
undo what it changed in a save. A script mod’s own data and settings stay in the modstore folder beside your saves,
so installing it again finds them; delete its files there to forget them too. A code mod’s code stays in the game until
the next build.
What doesn’t work
- Some code modules. A module that rewrites the game’s code while it runs (many hook frameworks do), or one that
needs something of the console Longshot does not have, is left out, and the Mods tab says why (as does
exefs_patches.txtin the game folder). A mod that replaces the game’s ownmain,sdkorrtldcannot be loaded at all. - The mod portal is not open yet, so there is no browsing or one-click install: you put mods in the
modsfolder, or add them on the launcher’s Mods page. - Longshot rewords one of the game’s texts for a PC (a hint that names the console’s built-in microphone). A mod that has its own copy of that text file wins over the rewording.
For mod authors
Start with your first mod, step by step, then using the Longshot API; making mods lists every guide and reference page. The file mod contract covers how file mods are found, ordered and served. Also:
- Code patches apply when their file’s name (IPS) or its
@nsobidline (pchtxt) is the game code’s build id,E0F3CCFAF50065AE4EA01EB5AEB13B1A45DA3348.exefs_patches.txtin the game folder lists what the build applied. - Cheats run as Atmosphere runs them, every frame (opcodes 0 to A and C0 to C3), from
mods/<name>/cheats/E0F3CCFAF50065AE.txt.{Master}codes are always on. - The size table Longshot makes at each start is written to
modcache/rsizetable.zsin the game folder. - Elsewhere:
HOS_MODS=<folder>, set in the game’s environment, names the folder that holds the mods. The game does not take it fromlongshot_env.txt.HOS_TEXTS=0shows the game’s own texts instead of the ones reworded for a PC.
