MySix Core

Mod settings normally live in a config file on each computer: changing one means finding and editing that file, and the same world plays by different rules on another PC or on a server. Core, which every other MySix mod needs, lets you see and change every MySix setting in game, and keeps the settings inside the world save. For a dedicated server it adds restarts that count down on everyone's screen, instead of throwing players out without warning, and, once its admin turns it on, keeps out players who lack the mods the server needs.

• The mysix command: press F5 and type mysix to list every MySix setting with its value, mysix get <setting> for what one does and its default, and mysix set <setting> <value> to change it. A setting for everyone is changed by the host or a server admin; each player changes their own. It is not a cheat command, so using it never marks you as having cheated.
• Settings kept in the world: settings for everyone, and each player's own choices (for that player), are kept inside the world save, in two small records far past the world's edge, where no one can go, so a world plays the same on any computer: a single-player world carried by Steam Cloud, or one moved onto a server. A world with no settings in it yet (a new one, or one last saved without Core 1.0.15 or later) takes the host's settings as it loads, and each player's own as they join, and keeps them from its next save. Edit a settings file while the game is closed and the world takes the change the next time it is played on that computer; on a computer it has never been played on, the world's own settings win over the file.
• Warned restarts, for admins of a dedicated server: put a file named restart.txt in BepInEx\config\MySix.Core on the server (make the folder if it is not there). Its first line is how many minutes' warning to give (5 if empty; from a quarter of a minute to 120); any further lines are a message of your own, shown with the first warning. Everyone is told in the middle of their screen straight away, then again when 10, 5, 2 and 1 minutes, and 30 and 10 seconds, are left (those shorter than the warning you gave); then the server saves the world and shuts down. Core does not start it again: whatever runs your server - WindowsGSM, a service, a script - must be set to restart it when it stops. A file named restart-cancel.txt calls it off. The warnings are in English.
• Keeping out players without the server's mods, for admins of a dedicated server (off by default): set Core.RequireMods to true and a player whose game lacks a mod the server needs, or has an older version of one, is turned away before entering the world. With MySix Core 1.0.18 or later their game tells them, in their language and under the heading 'Mod incompatibility', which mods to install or update and to what version; a game without mods, or with an older Core, shows the game's own 'Incompatible version'. Newer versions are let in, and so are mods the server does not have. Mods that run only on the server, Mods Not Cheating, and any listed in Core.NotRequired (GUIDs or mod names, separated by commas) are never asked of players. While it is off, the server only writes to its log whom it would let in or turn away, so you can see who is ready before switching it on. Both settings stay in each server's own settings file and are never kept in the world. To switch it from outside the game, put a file named joincheck.txt in BepInEx\config\MySix.Core whose first line is on or off; the server reads it within 2 seconds, and a server that is stopped reads it as it starts.
• Core's world-pass settings: Core.CycleSeconds (600 seconds) and Core.MaxObjectsPerFrame (2000) only pace Unique Items' one pass over the world, made by the computer hosting it when Unique Items' StartClockForOldPicks is on (off by default); nothing else uses them.

Part of the MySix mod suite. Every mod in the suite needs MySix Core, which adds the in-game mysix command for reading and changing settings. Settings are kept in the world itself, so a world plays the same on any computer or server: a setting for everyone is changed once, by the host or a server admin, and each player's own choices are kept in the world for that player.

Installing

Install with a mod manager - the Thunderstore Mod Manager, Gale and r2modman all work - and it fetches BepInEx and MySix Core for you. To install by hand, install BepInExPack_Valheim first, then unzip the DLL of MySix Core and of each MySix mod you want into BepInEx/plugins. Everyone playing together should run the same versions.

Settings

The Settings wiki page lists this mod's 4 settings: what each does, its choices and default, who can change it, and the exact command to type. In short: press F5 in game to open the console (if nothing opens, add -console to Valheim's launch options) and type mysix to list every setting, mysix set <setting> <value> to change one.

Languages

What the MySix mods show you in play - the names and descriptions of their items and portals, their messages on screen, and the Cartographer's map tab and marks - is in the language you play Valheim in, in every language the game offers except Abenaki, which shows English for now as we could not find a translation we trust. The mysix console command, the setting descriptions it prints, the Settings wiki pages and the warnings before a server restart are in English only. We mainly test in English; if something reads wrong in your language, please let us know.

Note on achievements

Valheim switches achievements off for anyone with a mod installed. MySix Mods Not Cheating, part of the MySix bundle, keeps them working.

Version 1.0.18. The Changelog tab lists what changed in each release.

Changelog - Core

What changed in Core, newest release first. Each MySix mod has its own version number, and only a release that changed Core is listed here.

1.0.18

• A dedicated server can keep out players who lack its mods (off by default). Set Core.RequireMods to true and a player whose game lacks a mod the server needs, or has an older version of one, is turned away before entering the world; with Core 1.0.18 or later their game tells them, in their language, which mods to install or update and to what version. Newer versions are let in, and so are mods the server does not have. Mods that run only on the server, Mods Not Cheating, and any named in Core.NotRequired are never asked of players. While it is off, the server's log says whom it would turn away, so you can see who is ready before switching it on; a file named joincheck.txt in BepInEx\config\MySix.Core, its first line on or off, switches it from outside the game.

1.0.16

• A world's own setting, set alone: a mod can now move a world's value for everyone (say, off an old default it has since changed) without touching this computer's settings file, which every world on it shares. The Cartographer uses it to give worlds its new sight distances.

1.0.15

• Settings go wherever your world goes: settings for everyone, and each player's own choices (kept for that player), are now kept inside the world save, in one small record far past the world's edge. A single-player world played on another computer through Steam Cloud, or moved onto a server, plays by the same rules and keeps each player's choices. A world from before this version takes the host's settings, and each player's own, at its next save. A change made in a settings file while the game is closed is still taken into the world the next time it loads on that computer.

1.0.14

• Warned restarts, for server admins: a file named restart.txt in BepInEx\config\MySix.Core on the server restarts it with warnings. Its first line is how many minutes' warning to give, any further lines a message of your own. Everyone is told in the middle of their screen at 10, 5, 2 and 1 minutes, 30 and 10 seconds; then the server saves the world and quits, for its host to start it again. restart-cancel.txt calls it off.

1.0.2

• Settings can be reached from the console by a short name, such as Lights.Mode. The full name contains a space, which the console splits on, so some settings could not be changed in game at all.
• The two server-side forerunners, LightFuel and Dyrnwyn Reset, are retired. The client-side mods were shown to cover their cases, including a fire the server itself placed.

1.0.0

• First release.