Jatify Jatify UI 0.3.0: from a stack of bug reports to a release All notes
← Back

Jatify UI 0.3.0: from a stack of bug reports to a release

A batch of player reports, the fixes they led to, and the checklist every release goes through before it reaches Thunderstore.

Alexandru Martalogu · 31 October 2026

Jatify UI 0.3.0 is 83 commits on top of 0.2.1. Many of them started as a report from someone playing with it: one player’s batch of reports became GitHub issues #15 to #38. This note is what happened to those reports, and what a release has to get through before it ships.

The reports

A UI mod gets reports that are mostly about small things in odd places, and the batch was like that. A few of them, with what they turned into:

  • The trash didn’t take items (#15). You could pick an item up, but letting go of it over the trash did nothing. Two fixes: the trash now takes an item you let go of over it, not only one you click it with, and its tile sits above the bag grid so the bag no longer swallows the click. Destroying things should be undoable, so the trash also got an Undo: click it again within 15 seconds and the item comes back.
  • Recipes you can’t craft yet were hard to read (#16), and the crafting list had no way to tell how far down you were (#35). They now read like the rest, and the list has a scroll thumb.
  • The build menu stalled when every piece was unlocked (#18), and its region filters didn’t fit the panel (#17). Both fixed, and the menu gained an Everything category and the piece’s name beside the cursor (#34).
  • Deleting a cloud character or world didn’t work (#19). It does now, including worlds that Valheim stores in several chunks, which a review pass found after the first fix.
  • Find servers (#20) now opens Valheim’s community server list, drawn in the same look as the rest.
  • The Mods settings list didn’t scroll (#21), the minimap’s clock ran under the wind arrow (#22), and the game logged missing-character warnings for its fonts (#23).
  • An effect with no timer showed nothing (#25). It now shows the effect’s own text.
  • A horse’s saddlebag offered Rename (#26). It doesn’t any more.
  • Weapons and Armour were one long list (#38). They have a second row of kinds now: Swords, Axes, Helmets and so on.

All of them were fixed by 30 October. Each fix is its own commit with the issue number in it, so the history reads as a list of what was reported and what was done about it.

Listening past the reports

Some of the biggest changes in 0.3.0 didn’t come from an issue, they came from looking at screenshots and saying what was wrong with them. The commit messages keep those notes:

  • The bottom was mostly empty. Tools, Food and Meads became one strip across the whole inventory panel.
  • They overlapped. Ailments move under the buffs when there are many.
  • They looked smudged. The minimap lost its panel, and its text and wind arrow got a solid dark edge so they read over snow and sky.
  • They only repeat the action bar and the figure. The hand slots left the character column.

The Food and Meads change needed care: those rows went from six slots to three. Anything in slots 4 to 6 moves into your bag, or drops at your feet if the bag is full, so nobody loses an item to an update.

Another fix came from testing a fresh character rather than a report. Valheim never resizes a new character’s inventory on its first spawn, so the extra rows and the Tools, Food and Meads rows only appeared after a relog. A new character now has them from the start.

What’s new, in the game

Most players never read a changelog, so 0.3.0 brings its own. After an update, a What’s new window appears when your character enters the world, with pictures of what changed and where the new settings are. Close unlocks once you have scrolled to the end, and the window keeps coming back at each world load until you tick Don’t show again. After that it is one click away: Esc, then What’s new! on the world card, or on the title screen.

The other visible change is the colour. Orange is the new default. Anyone who had picked their own colours in theme.json keeps them; only the old green defaults move to orange.

The release checklist

Every release follows the same checklist, and 0.3.0’s is written down in the repository as it happened. The steps that matter most:

Only finished work ships. Ideas that were discussed but never built stay out, even when they’re close. For 0.3.0 that meant three: tools for AdventureBackpacks’ chest, Alt + click with Quick Stack Store, and a keyboard fallback for the crafting station card. They can come later.

The release build is checked. The DLL that ships carries no developer tools, no paths from my machine and no other UI mod’s name. The packaging script refuses a DLL with developer tools in it. That check found one problem in the companion release: MapTeleport’s debug file still held a home path, so its build now strips paths too.

Testing, mostly by script. Testing a UI mod means playing the game, so most of it is automated inside the game itself. Development builds of Jatify UI carry a test kit that never ships in a release, and it runs in three ways:

  • Compatibility checks. In a profile with every supported mod installed, a set of checks runs against a throwaway character, each logging a pass or a fail with the reason. They cover every modded item’s tooltip, wearing and removing every modded item of gear without dropping anything, the hover text of every crafting station, backpacks, Quick Stack Store’s sorting, and a real save and reload. One command runs them all.
  • Scripted scenes. The kit takes commands from a script: spawn a creature, fill a chest, hover a slot, then take a screenshot. That’s how the pictures in the README and in What’s new are made, and how layout bugs get caught before a player sees them.
  • A smoke test of the real release. A script installs the actual release zips into a clean profile with nothing but their own dependencies, starts Valheim, loads a test character, opens the HUD, inventory, map and pause menu with a screenshot of each, and prints every error from the game’s log. It runs once per combination: Jatify UI alone, with MapTeleport, and MapTeleport alone.

Data safety is also checked by hand, the way a player would meet it: a brand new character fills the extra rows, saves, loads without the mod, dies and picks up the grave, and nothing may go missing. A fix only counts once it has been re-tested in the game, not just built.

The words match the code. A review agent (an AI reviewer) checked the README against what the code actually does, and the README was fixed where they disagreed. The changelog, the What’s new notes and the README all describe the same release.

Fresh screenshots. The pictures on the mod page and in What’s new were retaken in a rebuilt standalone profile with a clean save, a test character and a flat test world, so they show the mod as you’d install it, not next to whatever else is in my own profile.

Publishing. A secret scan over the repository, a normal merge (not a squash, so every fix keeps its own commit), version tags, then Thunderstore, Nexus, Hexium and a GitHub release. The Discord gets the changelog, and the pinned mod-compatibility list is updated.

Why bother

Jatify UI replaces the interface you look at the whole time you play. When it’s wrong, you notice every minute. The checklist is slow on purpose: a bug in a release costs every player who installs it, while an extra day of testing costs only me.

If you find something, the GitHub issues and the Discord are the places to say so. The changelog has every change in 0.3.0, sorted by part of the game.