Skip to content

SteamCMD Helper 1.7.0

Choose a tag to compare

@github-actions github-actions released this 21 Oct 11:11
· 39 commits to main since this release
  • SteamCMD Helper is now Modwright, with two sides: the Workshop uploader and the Drop Pod for RimWorld players. The name in the window, the brand bar (which also says which side is open) and the messages changed; the program file, the settings folder and the download page stay the same, so updates and settings carry on. The Drop Pod's buttons and lists are translated into German, Russian and Simplified Chinese.
  • The Drop Pod: a new tab for the RimWorld mods you play with. It finds RimWorld through your Steam libraries (or a folder you pick), reads every mod from the base game and DLC, the Mods folder and the Workshop, and lists each one's name, author, package ID, where it came from, the game versions it supports and its place in the current load order. Mods with a broken About.xml show in the warning colour with what is wrong, mods made for another game version are greyed out, and package IDs installed twice are named at the top. Ctrl+Tab now steps through Upload, Drop Pod and Options.
  • The Drop Pod sorts and saves your load order. Tick mods to make them active, move them with Up and Down (Alt+Up/Down), and Sort orders them so each loads after what it needs and its loadAfter list and before its loadBefore list (the version-specific lists for your game version included), with the base game and DLC first. Where no rule decides it keeps your order, or goes A to Z. Mods whose rules go round in a loop are named instead of silently dropped. Save to game writes ModsConfig.xml, keeping the old one as a backup, and refuses while RimWorld is running (it would overwrite the list when it closes). You can add your own rules file (More > Use my own load-order rules file) to put mods after or before others, or first or last; nothing is bundled.
  • The Drop Pod finds problems before you start the game. Under the mod list it shows, errors first: mods that need a mod that isn't installed or isn't active, needed mods that load too late, rules the order breaks, two active mods that say they don't work together (in their About.xml or your rules file), mods for another game version, list entries that aren't installed, a package ID installed twice (and which copy the game uses), and broken About.xml files. Double-click one to find its mod. Activate needed mods ticks the installed ones that are missing from the list, each before the first mod that needs it. Download missing gets the missing ones that link a Workshop item with SteamCMD and your saved login, straight into RimWorld's Mods folder (an older copy is only replaced once the new one is complete). Check for updates asks Steam which installed Workshop mods have a newer version, and which are no longer public.
  • Modlists. Save the active mods as a named modlist and switch between them in one click. Export one to a file, import a file (also RimWorld's own saved .rml lists), or share it as a single line of text that starts with DROPPOD1: and paste one in. Mods a list names that aren't installed are listed when you switch.
  • A closer look at About.xml before uploading. Besides a missing or malformed packageId, the RimWorld check now warns when About.xml has no name, author, description or supportedVersions, when a version is written as "1.5.4104" instead of "1.5", when a dependency has no packageId, no Workshop or download link, or an id RimWorld can't use, and when loadAfter, loadBefore or incompatibleWith name the mod itself, something that isn't a packageId, a mod that is also a dependency, or the same mod both before and after. Options > Uploading can make these warnings block the upload too, and the new SteamCmdHelper lint command runs every check without uploading (--strict for the same rule). The check reads About.xml with the same parser as the Drop Pod.
  • A new Kats theme, and the theme is now a drop-down. Options > Appearance lists Dark, Light, Kats and Match Windows in one drop-down instead of a row of buttons, so more themes fit. Kats pairs gunmetal grey with a vivid orange (#FF5C00) for buttons, ticks and selection, with dark text on the orange so it stays easy to read. The brand bar follows a dark theme's own colours; only the light theme keeps the dark bar.
  • Send your modlist to a Steam collection. Drop Pod > More > Send the active mods to a Steam collection creates a Workshop collection of the ticked Workshop mods, in load order, or updates one you made before so it matches exactly: inactive mods are taken out and new ones added. The base game, DLC and local mods that aren't on the Workshop are left out (and named). Each modlist remembers its collection. It goes through the Steam client, so Steam must be running and signed in.
  • Instances: separate RimWorld setups. Drop Pod > Instance > New makes one with its own options, mod list, saves and log, so a test list or a heavy modded run never touches your normal game. It can start from the active mods, only the base game and DLC, or a saved modlist, copies your game options and key bindings if you like, and can run another RimWorld install (an older version, say). Pick it in the Instance list to edit its mods, and press Play to start RimWorld with it (RimWorld's own -savedatafolder switch). More exports an instance to a zip, with or without its saves, imports one, opens its folder or deletes it.
  • Saves know their mods. Drop Pod > Saves lists the saves of the normal game or the picked instance, newest first, with the game version and how each save's mods differ from the active ones: not installed, installed but not active, extra, or in another order. Use this save's mods makes the active list match it (and offers to download the missing ones from the Workshop); Save as a modlist keeps it for later. Only the top of each save is read, so even very large saves open at once, and a damaged save says so instead of failing.
  • Test a mod list and read the log. Drop Pod > Test starts RimWorld (or the picked instance) and watches its log as it plays; Problems > Read the log reads the last one. Errors and warnings are grouped (the same failure in the same code counts once, however many pawns it hits), and each names the mod most likely at fault: its code in the stack trace (read from the mod's DLLs, never run), its Harmony patch on a method there, a file in its folder, or its package ID in the text. Untick the mod at fault takes it off the list to try again; Copy a report gives a short summary to paste in a bug report. Logs of any size are read a line at a time.
  • Insight into clashes and speed. Drop Pod > Problems > Insight reads the active mods' DLLs (without running them) for the Harmony patches they declare and points out methods two mods both rewrite with transpilers, prefixes that can stop other mods' changes from running, and mods that change many per-tick methods. It also names mods with a lot of textures or definition files (they add to loading time) and lists your rules file's notes. These are hints, not measurements.