MJOLNIR Tag Editor changelog
MJOLNIR Tag Editorv0.3.0

Author, test and publish mods without leaving the editor

Mods become saved projects rather than one-off exports: keep a list of your edits, test them in the game, and publish to the MJOLNIR Hub from inside the editor.

A mod is now a recipe of edits rather than a pile of baked bytes. Because each edit records what it changes rather than where it happened to sit, a project survives a game update: it re-applies against whatever you have installed, and anything that no longer matches is flagged instead of silently dropped.

Added

  • Mod projects. A folder holding your mod's name, version and summary, plus every edit you have made. Edits autosave as you accept them, and reopening a project resumes where you left off.
  • A change list showing the shipped value beside your modded value, with per-line revert.
  • Test, which builds the project, installs it into the game so you can try it, and removes it again cleanly afterwards.
  • Export to a .mjolnir archive.
  • Publish to the MJOLNIR Hub, with the results reported in the panel.

Publishing needs an account key with publish permission. A paired launcher deliberately cannot publish on your behalf.

Security

  • Published archives are signed. The signature names the mod, version, author, key fingerprint and the hash of every file in the archive — so re-zipping an archive cannot break its signature, but changing any byte inside one does, and nothing can ride along unsigned. Your signing key is generated on your machine, kept in Windows-protected storage, and never leaves it. Launcher 0.5.3 verifies these on install.

Fixed

  • Starting the editor showed a flash of the setup form before the real window. It now shows a spinner while it looks for your game.