NoMapDiscordAdditions

Two map workflows on Valheim's large map:

1. SEND MAP / COPY MAP — capture the visible map and either post it to a Discord webhook or paste it directly into Discord, Slack, or an image editor.
2. MAP COMPILE — visit cartography tables one by one and stitch every reading into a single high-resolution PNG you can save, copy, or send to Discord.

Cartography-table pins are decorated with distance/bearing-from-spawn captions baked into the captured image, and every potentially-noisy setting (capture method, message templates, output size, pin labels) can be server-synced so a host enforces the same look for everyone.

SEND MAP / COPY MAP

The bottom-right of the large map gets a Show Biome Text toggle, a SEND MAP button (default F10), and a COPY MAP button (default F11).

• SEND MAP posts the capture to your Discord webhook with a configurable message template
• COPY MAP writes the PNG to the system clipboard — paste straight into Discord, Slack, or an image editor
• Hold Left CTRL (configurable) when clicking COPY MAP to bypass the Discord-friendly cap and copy at up to 4096px on the long edge — useful when you want full quality for image-editor work
• The bound hotkey is shown in each button label (SEND MAP (F10) / COPY MAP (F11)) and updates automatically when the keys are re-bound
• The SEND MAP button is hidden until a webhook URL is available (locally or server-pushed); COPY MAP is always available
• Captures hide every UI overlay (panels, buttons, hints, hotbar) — only the map and (optionally) the biome label remain

Discord post	Spoiler-tagged

MAP COMPILE

A second panel appears on the bottom-left of the large map. The intent: walk between cartography tables, add each reading as a tile, and on COMPILE the mod composites every tile into a single PNG that preserves world coordinates. The session is never lost when you save/copy/send — pause your mapping adventure and resume it at the next table or after a restart.

Idle — START COMPILE / RESUME COMPILE (N)	Compiling — ADD TILE (N) / COMPILE (N) / SHARE (N) / CANCEL / CLEAR

• ADD TILE is enabled only when the map was opened at a cartography table (no M-key adds, no portable map items)
• Re-adding within ~8m of an existing tile replaces that tile in place — re-shoot a table without ending up with duplicates
• The session is saved to disk after every add, scoped to the current world + character. If you crash, disconnect, or just go on an adventure, click RESUME COMPILE (N) the next time you open the map
• CLEAR wipes the whole session — every in-memory tile and the on-disk session folder — and drops you back to idle. It sits next to CANCEL but stays greyed out and labelled CLEAR (L-CTRL) until you hold Left CTRL, so this destructive reset can't be hit by accident. Also offered next to RESUME COMPILE (N) in idle to discard a saved session without resuming it
• COMPILE opens the result panel:

• SAVE writes a full native-resolution PNG to disk — it recomposes so the sharpest tile maps 1:1 and no tile is downscaled below what it was captured at (a 2000×500 capture stays 2000×500 in its region), giving you a zoomable, editable map. Capped at 8192px on the longest axis; the status line says whether you got native resolution or hit the clamp, and the filename includes the dimensions. The button then morphs into COPY DIR so a second click puts the containing folder on the clipboard
• COPY writes the PNG to the clipboard at the Discord-safe size (CTRL+COPY raises the cap to 4096px, same as COPY MAP)
• SEND TO DISCORD posts the composed image (Discord-safe size) with the compile message template ({player}, {tileCount} placeholders)
• SAVE / COPY / SEND / DONE are all non-destructive — your session is kept on disk and stays resumable. DONE drops you back into compile mode with every tile intact so you can keep adding tables. Only DISCARD (or CANCEL while compiling) deletes the session
• Closing the map while the result panel is open doesn't strand the session — on the next map open you get a RESUME COMPILE (N) button that drops you straight back into compile mode with every tile intact (it does not reopen the result panel; the transient compiled PNG is discarded — just click COMPILE again when you want a fresh result)

Sharing tiles between players

In a no-map world each player only reveals the area around the tables they visit. SHARE lets a group pool coverage:

• SHARE (N) (shows EXPORT (N) if no webhook is set) exports every tile in your session as an individual PNG with its world rectangle embedded in the image itself. With a webhook configured the tiles are posted to Discord (one per message); copies are always saved to BepInEx/config/NoMapDiscordAdditions/compile-share/out/<world>/ so you can drag them in manually.
• To receive: save the PNGs a teammate shared into BepInEx/config/NoMapDiscordAdditions/compile-share/incoming. The next time you open the large map during a compile session, tiles for your current world are merged into your active session automatically — then COMPILE composites yours and theirs together. (A Discord webhook is send-only, so import is folder-based rather than read back from Discord.)
• Re-importing or re-sharing the same tile updates it in place; tiles for a different world are skipped. Handled files move into incoming/processed or incoming/ignored.
• Tile sharing can be turned off entirely with Map Compile.Enable Map Sharing (server-synced) — the SHARE/EXPORT button disappears and nothing is auto-imported, so compile mode stays purely local.

Composed PNG (4 tables stitched)	Sent to Discord	Spoiler-tagged

Cartography-table pin labels

Every visible cartography-table pin in a capture is decorated with {distance}m {Direction} ({bearing}°) — e.g. 1240m NorthEast (45°). Labels render only during the capture, never in the live UI, and respect Valheim's icon filters, viewport, and shared-map fade. The Discord message template gets a matching {spawnDir} placeholder; if your map is opened via the M key (no table involved), {spawnDir} falls back to the player's current position so Discord captures always include a direction.

Naming a table

A table can carry a human-readable name that flows into the Discord message ({table} placeholder) and the compiled-map captions ({name} — {distance}m {Direction}). There's no separate naming UI — the mod reads the closest named map pin sitting on the table (within ~8m):

• ZenMap auto-pins every cartography table with the vanilla "house" icon. Rename that pin and you've named the table.
• Or drop a Town pin on the table and name that.

Leave the pin unnamed and nothing changes — captions and messages fall back to just the direction, exactly as before. The name is captured the moment you add a tile in MAP COMPILE and stored in the session, so it stays correct even when the table is far away or unloaded at compile time.

Map styles

Map Style.Style (client-only) replaces the live in-game map look with a stylized render for SEND / COPY captures and MAP COMPILE tiles, reconstructed from Valheim's own map data — explored areas show full detail, unexplored areas stay fogged. Five settings:

• None — the normal in-game map look (no styling)
• Old Map — aged-parchment chart: biome wash, Perlin grain, height-contour and biome-edge lines (a faithful reimplementation of ASpy's MapPrinter GenerateOldMap look)
• Chart — flat topographic chart, contour and biome-edge lines, no parchment grain
• Topographical (default) — shaded-relief terrain with hillshading, contours and biome-edge lines
• Satellite — naturalistic shaded terrain, no line work

A selected style forces the texture-capture path for that capture (the screen-capture path screenshots the unstyled live map, so styling has to go through the offscreen render). MAP COMPILE tiles render through the same pipeline at tile resolution and the composite stitches stylized terrain together. The per-pixel passes run on a background thread so the game doesn't stall during a capture.

Configuration

Discord

General

Map Style

Map Compile

Pin Label

Controls

Server behavior

Config sync is handled by Jotunn's SynchronizationManager (Jotunn is a required dependency). On connect, the server pushes its value for every synced setting to all clients, the entry is locked client-side, and each client's local value is cached and restored on disconnect. There is no separate ServerSync install or RPC protocol version to keep in step.

These settings are server-synced (a host enforces one look for everyone):

• General.Capture Method
• General.Capture Super Size
• Discord.Spoiler Image Data
• Discord.Hide Clouds
• Discord.Send Max Dimension
• Discord.Message Template
• Discord.Webhook URL — synced so sending works for everyone, but hidden from the in-game ConfigurationManager window so non-admin players can't read it from the settings UI
• Map Compile.Max Output Dimension
• Map Compile.Compile Message Template
• Map Compile.Enable Map Sharing
• Map Compile.Share Message Template
• Pin Label.Enabled
• Pin Label.Include Distance
• Pin Label.Include Direction from Spawn
• Pin Label.Include Map Item Sources
• Pin Label.Show on Compile Mode

Show Biome In Capture, Enable Logs, hotkey bindings, and the modifier key are always local to each client (bound synced: false).

Dependencies

• BepInEx Pack for Valheim 5.4.2333 (declared in the manifest)
• JsonDotNET 13.0.4 (declared in the manifest) — used to persist compile sessions to disk
• Jotunn 2.29.0 (declared in the manifest) — provides the server-authoritative config sync (SynchronizationManager). ZenMap already depends on Jotunn, so most setups already have it
• ZenMap ≥ 1.7.6 (declared in the manifest) — required for MAP COMPILE. Recent ZenMap also fixes a Graphics.CopyTexture size-mismatch error on expanded worlds (e.g. a 4× map); update ZenMap if you see that error

Support & questions

Found a bug, have a question, or want to request a feature? Reach me as virtualbjorn on either of the Valheim modding Discord servers:

• OdinPlus — https://discord.gg/mbkPcvu9ax
• ValheimModding — https://discord.gg/MJWtxQs

Ping virtualbjorn in the relevant modding/support channel and include your BepInEx/LogOutput.log if you're reporting an issue. You can also open an issue on the GitHub repo.