AutoMapPin

This mod serves as a kind of "radar" for your Valheim map, automatically creating temporary and persistent pins for various in-game objects.

Features

• Server Synced
• Will create pins on Map and Minimap
  • WARNING: do better not configure too many to be active, it will flood your map!
• Pins will only show in areas where the player did already discover the map
• Pins created are using custom icons, see Available icons
• Pins can be configured, see Pin configuration
• Pins can be temporary (just visible when in area) or permanent (once discovered added permanently to map)
  • Permanent pins needs to be removed manually, so think twice about using this too widely
• Pins can be configured with color as you like
• Pin are loaded/created for game objects of Valheim types:
  • Destructible
  • Leviathan
  • Location
  • MineRock (ore)
  • MineRock5 (ore)
  • Pickable
  • TeleportWorld (portals)
  • PickableItem
  • Container (chests)
• Unknown (missing config) pins will be added to a temporary list that can be printed to a file to simplify configuration.
• Config file watchers (updated config file will be releaded)
• Pins are part of an object in the game. If the object is destroyed / removed, the pin is also removed.

Configuration

• The mod generates a short BepInEx config file FixItFelix.AutoMapPins.cfg
• Most configuration is provided via YAML files, see data model

Pin configuration

• A default configuration for vanilla objects is shipped with the mod. The setting of active categories and pins is from my own experience of how I prefer to play (not flood my map). But you can edit and change those as you prefer.
  • Remark: I actually do not play vanilla Valheim much, if there is something missing or someone wants to provide better configs, feel free to reach out. I am happy to also share more or different configs.
• If you play with objects beyond the vanilla ones, you might need to create your own configuration file, the following sections will explain how to.

Debugging effective configuration

There is a console command 'print_effective_config' to print the effective config of (only active) configs. This can be used to help debugging what actually was loaded.

Config data model

• all category and pin configuration is provided using YAML files

YAML schema

Some statements to explain the intent of the schema:

1. The top level is the name of a category that you choose yourself to group configs and share certain settings in between the pins configured inside this category.
2. Each Category can (optional) have either or both of "individualConfiguredObjects" and "categoryConfiguredObjects", and each category does have the ability to also configure values for the whole category like you can configure for any individual config object entry.
3. individualConfiguredObjects: does contain a dictionary, the key is the game object "name" field content the value is the set of fields for configuration, see below.
4. categoryConfiguredObjects: does only contain a list of game object "name" field contents that are NOT configured individually, but all are only configured by any value set at category level.
5. Many configuration options are inherited from category down to categoryConfiguredObjects (they inherit all settings) and individualConfiguredObjects (they can inherit "name", "iconName" and "iconColorRGBA").
6. Any value that is not set will either be set with some default value or be inherited if available.

Config options per object:

1. "name" -> the name shown on map, can be omitted to not show a name
2. "iconName" -> the name of the icon to use, see available icons in the respective section of this readme
3. "iconColorRGBA" -> contains the fields "red", "green", "blue", and "alpha"; the values need to be set as int type ( per channel, from 0 to 255, where 255 is full color); alpha sets the intensity of the color (also 0 to 255)
4. "isPermanent" -> pins with this flag set to true (default false) will not be removed when the player walks away from the area, and they will be persisted in the player save file
5. "isActive" -> activates the mod to use the config for this pin if set to true (default false)
6. "groupable" -> activated if set to true (default false) will enable pin grouping that will create one pin (counting the number of occurrences of the same object around it in the name)
7. "groupingDistance" -> the distance to be used to build groups of pins (default 30.0)

Yaml example

seeds:
  individualConfiguredObjects: # using this option will let you define individual pins, like if you want to name each of them differently, or activate grouping just for some of them
    Pickable_SeedCarrot:
      name: Carrot
      isPermanent: false
      isActive: true
      groupable: true
  isActive: true
  iconName: seed
crypt:
  categoryConfiguredObjects: # using this option will apply same settings for all those pins
    - Crypt2
    - Crypt3
    - Crypt4
    - SunkenCrypt4
  name: Crypt
  isActive: true
  isPermanent: true
  iconName: dungeon
  iconColorRGBA:
    red: 120
    green: 255
    blue: 255
    alpha: 200

Yaml internal name parsing

Rules:

• removes (Clone)
• removes (123)

Example: in-game loaded gameObject.name entry like Mistlands_DvergrTownEntrance1 (2) or Mistlands_DvergrTownEntrance1 (Clone) will be parsed to: Mistlands_DvergrTownEntrance1

Create config file

• You can create multiple additional config files, the mod will load every file matching the pattern inside any sub folder of the .../BepInEx/config/ path.
• Pattern for new files: FixItFelix.AutoMapPins.categories.*.yaml (replace "*" with your choice of name)
• There is a mechanic provided by the mod that will record any kind of pin that has a missing config while running through the world.
  • You can output all found config files using the console command amp write_missing_configs_file
  • All configs created by that will have defaults set n_a and booleans set to false, change those according to the data model (see data model)

Available Icons

These custom icons were made available with CCBY license, see attributions section.

Miscellaneous