Valheim
You are viewing a potentially older version of this package. View Latest Version
Install with App

Details

Date Uploaded
Downloads
32
Size
180KB
ADDatHost Valheim hosting
30% off

Leviathan Hall

Build your base on the back of a sleeping sea beast, and call it to you from anywhere on the map.

The hall at sea


⚠️ This mod is in testing

This is an early release. It has been played and tested extensively in single player, and barely at all in multiplayer. Things will be found. Please read Known issues and limitations below before you build anything you would be sad to lose, and back up your world — %APPDATA%\LocalLow\IronGate\Valheim\worlds_local, or your server's worlds_local.

If you hit something, a bug report with your LogOutput.log is worth ten descriptions. The mod logs a STATE line on every world load that says whether your hall is intact.


How this was built

Written with AI assistance, and tagged accordingly. You would have found out eventually; better that you hear it here.

What that does not mean is generated and thrown over the wall. Every engine behaviour this mod depends on was read out of Valheim's own assembly rather than guessed at — how portals are saved, how a fire registers the heat a cooking station looks for, how ash damage decides what to burn, how a shield works out what it is protecting. Several entries in the changelog are fixes for latent bugs in the game itself that only surface because a hall moves and nothing in Valheim was built to move. The known issues below are the real ones, and they were found by playing it.

Judge it on whether it works.


⚠️ The hall protects nothing from the world

Taking it somewhere dangerous is taking your base somewhere dangerous. The leviathan moves your build; it does not shield it. Everything you have put on its back is still an ordinary Valheim structure with ordinary health.

The Ashlands will destroy it. Falling meteors and the biome's fire damage hit your pieces exactly as they would on land, and a hall parked there unattended is a hall being dismantled. The same applies anywhere hostile: a raid finds you wherever the hall happens to be floating.

A shield generator is not a fire shield, and this is the part that catches people out. It does two real things: it stops ash decay on pieces inside it, and it silences ember sources inside it. What it does NOT do is stop embers thrown from OUTSIDE the dome — the check that suppresses them tests the ember SOURCE's position, not yours. So they fly in, land on your build, and start a fire on it, which then burns merrily inside your bubble.

What protects a build in the Ashlands is material, not coverage. Fire only takes hold on things that burn, and ash decay spares pieces that are ash-resistant or under an ash-proof roof. Stone shell, ash roof, wooden things inside it. A workbench under an open sky with a shield over it will still burn down, and you will watch the damage numbers while it happens.

This is deliberate. The mod removes the support rules on a hall, so nothing sags or collapses for want of a beam — but damage is damage, and a piece that is destroyed is destroyed. Visit the Ashlands by all means. Do not moor there and log out.

What it is

Find a leviathan at sea. Clean the barnacles off its back without angering it, and if it does not mind, it settles and stays. What you build on it is a hall: an ordinary Valheim base, on a creature that moves when you tell it to.

Equip the Binding Horn and the hall surfaces where you are standing. Put the horn away and it sinks out of sight until you want it again.

How it moves, and why that matters

The hall does not sail. It submerges, relocates, and rises — a discrete move, not continuous motion.

That is a deliberate design choice rather than a limitation. A base that sails needs every piece's physics synchronised across every player, every frame, which is the hardest problem in this genre and the reason moving-base mods tend to be unstable. Relocating discretely removes that entire class of problem.

The second choice behind it: nothing on your hall is ever read, copied, serialised or rebuilt. The pieces you built are moved, exactly as they are, with their contents untouched. That is why a chest full of modded items arrives full of modded items, an item stand keeps an enchanted weapon with all its enchantments, and a crop keeps its growth timer. The mod does not know what is in your chest and never needs to.

Farming: the dirt block

Crops need cultivated ground, and cultivated ground is paint on the terrain heightmap — there is no terrain on a creature's back. So the mod adds a Dirt block: a cube of real earth you build and carry aboard. Cultivate it, pave it, path it, or let it go to grass, with the same tools you would use on the ground. Crops grown in it travel with the hall, growth timers and all.

Building big: sea foundations, and no support rules

Two things make a hall larger than a leviathan's back possible.

Nothing on a hall needs support. The game's structural integrity is suspended for hall pieces — no sagging, no blue-to-red strain, no wall collapsing because the beam under it broke. This is a concession rather than a feature, and it is deliberate: a support system on a structure that teleports would disown half your build the first time one plank failed. So build out as far as you like, cantilever what you want, and put the workshop where it looks right rather than where physics allows.

The sea foundation is the other half. It is a build piece that sits on open water, extending outward from the creature, and anything connected to it joins the hall and travels with it. Bridges, docks, a flight deck — the leviathan's back becomes the keel rather than the whole footprint.

The practical limit, and it is not rendering

The limit is membership reach, not graphics. Hall Radius (48 metres by default), HeightAbove (100m) and DepthBelow (25m) define a volume around the creature, and pieces outside it never join the hall — so they stay behind when it moves. A carrier wider than 96 metres end to end will leave its wingtips floating in the ocean. These are server-owned settings, so if you want a bigger hall, raise Radius rather than discovering the edge the hard way.

Rendering is not the constraint it sounds like. Valheim streams objects in around you, so distant parts of a very large hall simply are not built yet — but relocation moves the RECORD of every member, not the objects, so parts you cannot see still travel correctly and appear when you walk over to them. The rise animation only plays for pieces currently loaded, so on a very large hall the far end may simply be there rather than rising out of the water. Cosmetic.

What has genuinely not been tested is scale: moving three hundred pieces is instant, and nobody has yet tried three thousand.

What travels

Everything built onto the hall, plus anything standing on its own deck: tamed animals, dropped items, carts, ripe crops. The rule for loose things is directly above one of this hall's own pieces — being merely nearby is not enough, so parking against someone's longhouse does not carry off their chests.

The hall refuses to leave with a player standing on it, and refuses to submerge with anything alive aboard, because it would drown them.


The same hall, wherever you take it

On the deck

In the Ashlands

Snowed in


Dependencies

Required — the mod will not load without these:

Dependency Version
BepInExPack Valheim 5.4.2360 or later
Jotunn 2.30.2 or later

Optional — detected at runtime, not required:

  • PlantEasily — if you have it, grid planting works on the dirt block. If you do not, the two patch classes that support it simply do not load and everything else is unaffected.

Multiplayer: this mod is EveryoneMustHaveMod with Minor version strictness. The server and every client need it, and their minor versions must match — so 0.1.0 and 0.1.3 can play together, but 0.1.x and 0.2.x cannot. Patch releases deliberately do not force a coordinated update.

All settings except Verbose are server-owned: admins set them, and connecting clients receive them. This is not cosmetic — the server and clients time the rise animation from the same numbers, and a disagreement causes real bugs.


Known issues and limitations

Stated plainly, because finding these yourself is worse.

A hall answers only to those who have bound a horn to it. The server keeps a list of players permitted to command each leviathan, and grants a place on it when you bind a horn while standing beside the creature. Other players cannot call, move or submerge your hall. This stops ordinary players from interfering with each other; it is not armour against someone running deliberately modified code, and nothing in Valheim is. A hall settled before this release is unclaimed, and the first person to command it becomes its keeper.

A shield generator's bubble is invisible until the area reloads. After the hall moves, a shield's dome is put back over its generator and protects correctly — the game's own check agrees — but the bubble is not redrawn in place. Walk far enough away for the hall to unload and come back, or reload the world, and it reappears. Cosmetic only: you are protected the whole time, you just cannot see the dome. If you want to confirm it rather than trust it, lh_dump shield reports the real radius and whether the game considers you inside.

Multiplayer is largely untested. Single player is well tested. A dedicated server has not been through a full session. Specifically unverified: whether the sink and rise animations play correctly for other players, whether the "someone is standing on it" refusal behaves with two players, and whether taking a chest someone is actively using along for the ride causes a hiccup.

Pieces never lose membership. Once something is part of your hall it stays part of it, even if whatever connected it is destroyed. This is on purpose: the alternative is a support system that quietly disowns half your build when one plank breaks. The cost is that a piece you deliberately separated is still carried along until you remove it.

Everything on the hall is structurally supported. There is no integrity calculation on a hall — pieces do not sag or break from lack of support. A concession, and one most players will consider an improvement.

The engine assumes the ground does not move. Dozens of Valheim systems ask the terrain where the floor is, and over open ocean the answer is the seabed. The ones known to matter are handled — crops no longer delete themselves, ripe produce no longer falls through the hall, fires still count as lit after a move, portals keep their position across saves. Others may surface, usually as "something behaved as if it were eighty metres lower than it looks." Report those; they are a known family and are usually quick to fix.

Mass-building and blueprint mods are untested. If a mod places pieces without going through the game's normal placement, they may not join the hall. If a build does not travel, lh_adopt re-derives membership and fixes it.

Biome hazards still apply, and the Ashlands are worse than they look. Covered above, and repeated here because it is the one that can cost somebody an evening's building: meteors and fire damage your pieces normally. The hall is transport, not armour.

Very large builds are untested at scale. A relocation moves every piece at once. A modest hall is instant; a thousand-piece fortress has not been tried.

Crops that ripened before 0.1.0 may be sitting below the deck from an older bug. lh_rescue puts them back.


Support schedule

Honest expectations, so nobody is guessing:

Testing — the next few weeks. Expect bugs. Expect to report them. Back up your worlds. Fixes will come quickly and often, as patch releases that do not force everyone to update at once.

Active bug fixing — several months to a year. Reported problems get investigated and fixed. This is the period in which it is worth telling me about anything odd.

Maintenance afterwards — as needed. Once it has settled, support becomes keeping it working: compatibility with new Valheim versions and with Jotunn, and fixing anything that breaks. Not new features, unless something obvious turns up.


Commands

Open the console with F5. Commands marked DEV need devcommands first.

Command What it does
lh_check Every hall member, its offset, and any stale records.
lh_rescue Put crops back that are stuck below the deck.
lh_adopt Register what is built on the hall. lh_adopt reset re-derives from scratch.
lh_anchor Anchor the leviathan you are standing on.
lh_catalogue Write everything the game has loaded to a file beside the config.
lh_dump <what> Look up clutter, shaders, pieces, prefabs, items, materials. Tab completes.
lh_summon [willing] DEV: surface a leviathan nearby.
lh_tame DEV: settle the one you are standing on.
lh_ripen DEV: make the hall's crops ripen now.
lh_racetest DEV: stage the ripen-during-the-rise race deliberately and report pass/fail.

Configuration

Everything is in BepInEx/config/com.angelwraith.leviathanhall.cfg, grouped into Summoning, Hall, Horn, Surfacing, Discovery and Debug. The defaults are the tested ones.

Every setting except Verbose is server-owned. Admins set them and connecting clients receive them, because most of these numbers are an agreement between machines rather than a preference — the server times the arrival from the same seconds the clients animate from. Verbose only decides how much your own machine writes to its log.

The ones worth knowing about:

Setting Default What it decides
Hall / Radius 48 How big a hall can be. Horizontal reach around the creature; anything outside never joins and will be left behind. Raise this before building something enormous.
Hall / HeightAbove 100 How far up still counts as part of the hall.
Hall / DepthBelow 25 How far below the creature still counts.
Hall / CarryPassengers true Whether tamed animals, dropped items, carts and ripe crops standing on the deck travel with it.
Hall / VerifyPositions true The self-healing pass that puts back anything not where the hall says it belongs. Leave it on.
Surfacing / RiseSeconds 9 How long the hall takes to rise on arrival. 0 disables the effect.
Surfacing / SinkSeconds 4 How long it submerges before departing. The move waits for this.
Horn / StowDepth 60 How deep it rests while stowed.
Horn / NearEnough 60 Within this distance, equipping the horn raises it where it lies instead of asking.
Horn / StowWithLivingAboard false Allows submerging with players or tamed animals aboard. They drown. Off for a reason.
Summoning / MinimumDepth 15 How deep the water must be for it to surface. Lower it if it keeps arriving further out than you want; the guard exists to stop a leviathan loading inside the terrain.
Discovery / WillingChance 33 Percent of leviathans that do not mind being settled.
Debug / Verbose false Detailed logging. The first thing to turn on when something behaves oddly, and the only client-side setting here.

Credits

Built with Jotunn. Thanks to Iron Gate for a game whose engine rewards reading.

Thunderstore development is made possible with ads. Please consider making an exception to your adblock.