Wings of the Valkyrie

Wings of the Valkyrie

By the grace of the Allfather, the skies of the Tenth World are no longer out of reach.

Wings of the Valkyrie is a massive, physics-based flight overhaul for Valheim. Why trudge through the muddy swamps or sail across treacherous oceans when you can claim your birthright and take to the skies like a true Norse god?

Four craftable tiers of glowing runic wings await — and with 2.0.0, flight stopped being a thing you craft and became a thing you learn. 2.0.1 finishes the thought. The numbers printed on a set of wings are no longer what you get the moment you put them on; they are what mastery buys. A novice in Dragon wings is a novice. The sky is earned one wingbeat at a time — and now the mod keeps a logbook of every one of them.

2.1.0 makes the wings themselves worth keeping. They are no longer cape clones wearing a new icon — they are the mod's own items, with their own armour, their own resistances and their own upgrade path, and they no longer need Jotunn to exist.

2.1.4 gives the skill its memory back. From 2.1.0 to 2.1.2 the game quietly discarded your Valkyrie Flight level every time it loaded your character. It keeps it again — and if you lost one along the way, there is now a console command to put it back. Update the server and every client together: a 2.1.4 server will not let those three builds connect, because a client that is still deleting its own player's levels is not something a server can protect anyone from.

2.2.0 lets the wings ride as a trinket. Valheim 1.0 gave every Viking a trinket slot, and the wings can live there now instead of on your back — which leaves the back free for a real cape. Whether they may is the server's call (WingsSlot: automatic, the player's choice, trinket only, or back only), and the wings carry their full armour and resistances in either slot. See Where the Wings Go below.

⚠️ Upgrading

Your config upgrades itself — again. The mod stamps a layout version on its config file and migrates old files on first launch, whether they come from 1.1.x, 2.0.0, or anywhere in between. Any setting still sitting at its old default moves to the new balance; anything you or your server admin actually changed is kept exactly as you set it. A backup is written beside the config before a single value is touched, and the log lists what moved and what stayed. No config deleting, no lost admin work.

Coming from 1.1.x? A 2.0.x client cannot join a 1.1.x server and vice versa — that is deliberate, since recipes, balance, and the skill all changed shape.

Coming from 2.0.0? Patch releases still talk to each other, so a 2.0.1 client will connect to a 2.0.0 server. It just won't fly by the same rules: the 2.0.1 balance knobs don't exist on a 2.0.0 server to be synced, so update both ends together if you want everyone earning the sky at the same rate.

Coming from 2.1.x? Nothing in your config changes and nothing on your character is touched; one new section, [9. Wing Slot], appears at its default (Auto). A 2.1.6 client still connects to a 2.2.0 server — it simply keeps its wings on its back and logs one line about a setting it does not know — but update the two together anyway, as always. If your server should behave exactly as before, set WingsSlot to BackOnly.

Coming from 2.0.2? Nothing in your config changes, and a 2.0.3 client still connects to a 2.0.2 server. One behaviour does change: transforming some other back item into the wings through AzuExtendedPlayerInventory's vanity slots used to hand over real flight. It no longer does — flight comes from the wings you actually have equipped, and from nothing else. Real wings worn underneath a vanity cape still fly exactly as they always have.

Coming from 2.0.3? The boat fix is decided entirely on your own machine, so updating your game is enough — a 2.0.4 client behaves itself on a 2.0.2 or 2.0.3 server, with nothing to change at the server end. Shipmates still on an older build will keep opening their wings on the swell until they up