Valheim’s latest hotfix notes contain two different kinds of information: repairs shared across platforms and extra changes in the Steam build. They also carry an important exception for Switch 2. Iron Gate says an upload failure prevented that platform from receiving the update, leaving crossplay with Switch 2 unavailable under the published notice. Players arranging a shared session need to check the platform exception as well as the headline version number.
Table of Contents
The platform numbers do not all mean different content
The common hotfix is listed as version 1.0.10, with Xbox receiving the equivalent changes as 1.0.11. Steam also has additional fixes under 1.0.12. An Xbox player and a Steam player can therefore see different version labels without every difference representing missing gameplay content. The developer’s platform notes are more useful than comparing the numbers alone.
The Switch 2 situation is different. Iron Gate added a notice explaining that the upload failed, and that crossplay involving Switch 2 was not supported as a result. That exception should not be ignored because an earlier part of the announcement describes changes for all platforms. Before a group starts a shared world, the Switch 2 player should check for a later successful update and the host should confirm compatibility.
Check stored equipment before removing it from a stand
One of the Steam fixes concerns equipment displayed on item stands. The notes say the affected items should keep their durability and upgrade level. However, the protection is conditional: the location must not already have been visited since version 1.0. That qualification matters for a long-running world, where a player may have returned to an old base before installing this hotfix.
If the area has already been loaded in version 1.0, do not assume that installing 1.0.12 will repair every stored item’s state. Back up the world before taking valuable equipment off a stand. A backup preserves an option to recover from a problem; it is not evidence that a particular item is already damaged. Checking a less valuable displayed item first is also more cautious than immediately removing a fully upgraded piece.
| Platform | Version information | Important distinction |
|---|---|---|
| Xbox | 1.0.11 | Equivalent to the shared 1.0.10 fixes |
| Steam | 1.0.12 | Includes additional item, crafting and stability fixes |
| Switch 2 | Upload failure reported | Crossplay exception remains in the published notice |
Deep North repairs and crafting corrections
The shared fixes include a repair problem affecting Deep North heavy armour. Players who were unable to repair that equipment should test it again after updating their platform. This is a correction to maintenance of existing gear, not an announcement of a new armour set. The hotfix also addresses shaman damage and healing, along with snow effects and sounds associated with punching or landing.
Steam’s additional list includes a correction involving unintended recipes and Forge Potential. That change is another reason to avoid treating results from the first 1.0 build as a permanent crafting rule. When an old recipe no longer appears, check the corrected recipe list before assuming that materials have disappeared or that a save is broken. The notes do not support claiming that all crafting costs have changed.
World stability and server administration
A crash associated with an unloaded zone is included in the Steam fixes. An unloaded area is not necessarily somewhere a player has never explored; it is an area not currently active in the relevant game state. The patch note describes a specific crash correction, not a promise that all sources of instability have been eliminated.
The developer also addresses old and new forms of player identifiers used for bans. Server administrators should be aware of that distinction when checking their moderation records. It does not justify clearing a ban list or removing restrictions from every account. Preserve existing records and investigate a specific failed ban against the updated behaviour. A server restart and compatible game versions should be checked before more disruptive troubleshooting.
Players who use developer commands can choose achievement tracking
The Steam changes include achievement notifications and an explicit opt-in route for players who have used developer commands. The important point is that this is a deliberate choice provided by the developer. It should not be confused with a general statement that every modified session automatically grants achievements after the hotfix.
Players who want that option should follow the exact current instruction in Iron Gate’s notes rather than type an approximate command copied from a discussion. Keep routine world maintenance separate from achievement troubleshooting. The repair of an item stand, the compatibility of a multiplayer session and achievement eligibility are different problems even though their fixes appear on the same update page.
A short check before the next shared session
For a returning group, the practical order is straightforward. Update each platform, check the host’s version, preserve a world backup and then inspect any valuable equipment affected by the item-stand issue. If the group includes Switch 2, confirm that the published crossplay exception has actually been lifted before committing to a shared session.
The hotfix reduces several risks around the 1.0 transition, but it does not erase the conditions in the notes. In particular, the history of a loaded area matters for stored equipment, and the platform upload matters for crossplay. Treating those details as part of the update, rather than as small print, is the best way to avoid losing time or valuable items.
