Norse Personality Construction System
A questing framework for servers. Create your own NPCs and give them purpose!
Last updated | 2 weeks ago |
Total downloads | 1990 |
Total rating | 1 |
Categories | Mods Server-side Client-side NPCs Ashlands Update Bog Witch Update |
Dependency string | VentureValheim-Norse_Personality_Construction_System-0.0.7 |
Dependants | 16 other packages depend on this package |
This mod requires the following mods to function
denikson-BepInExPack_Valheim
BepInEx pack for Valheim. Preconfigured and includes unstripped Unity DLLs.
Preferred version: 5.4.2202ValheimModding-Jotunn
Jötunn (/ˈjɔːtʊn/, 'giant'), the Valheim Library was created with the goal of making the lives of mod developers easier. It enables you to create mods for Valheim using an abstracted API so you can focus on the actual content creation.
Preferred version: 2.21.3README
Norse Personality Construction System
A questing framework for servers. Create your own NPCs and give them purpose!
Disclaimer!
This mod is not finished! There are many features that still need to get added. Feedback on current supported features will be greatly appreciated. See the list of possible future improvements and contributing information at the bottom of this readme.
Features
- Create your own custom NPC characters and assign them different functions including:
- Information: Give the player information or a quest.
- Reward: Give a reward to players for speaking with them or giving them an item.
- Sellsword: Hireable and will fight for the player. (Not finished)
- SlayTarget: Defeat this NPC for rewards. (Not finished)
- Trader: Runs a store similar to Haldor/Hildir. (Not finished)
- NPCs can have random movement and actions such as sitting in chairs. (Not finished)
- NPCs come back to life once killed by default.
- NPCs can be set to permanently die and players can choose when to bury the body.
Global and Player Keys
What is a key and what is controlled by them? In vanilla Valheim there exists a "global key" list that is a bunch of strings shared by all players. There also exist vanilla "player keys"; These keys are saved separately for each player. Worldly spawns, raids, dreams, and Haldor's items are all controlled by the presence of specific keys. Each boss, select creatures in the game, as well as Hildir's quests each have keys associated with their completion. This mod also adds keys and uses the existing vanilla systems to control game behavior.
This mod can add to both the Global Key and Player Unique Key systems. Quest rewards can be customized to either apply to all players, or the individual that completed the action. When this mod checks for the existence of keys it will check both of these lists. This will be pointed out in the examples provided below.
World Advancement & Progression Mod
This mod will pair nicely with WAP's private key system. If an NPC is configured to use Global keys then only the players within the radius (about 100 meters) of the receiving player will get the keys. If you wish all player in the area receive the key, then use the "Global" setting for your NPC configuration. Otherwise use the "Player" setting to have true individual progress. The mod will default to "Player" when not specified.
If you desire that some keys are allowed to be Global you can use the advanced configurations for the progression mod to allow for these keys to be added to the global list. This is useful for quests that you only want one player to be able to complete, or if you only want to require one player to perform an action to unlock a certain quest line for the entire server.
Getting Started
Currently there are four ways to spawn NPCs: Using RightCtrl + E on either a Bed or Chair, the npcs_spawnrandom
command, or from a configuration with the command npcs_spawnsaved
. Random NPCs will all be of the default NPC type none and will have random styles. They have no functionality other than adding clutter and life to the world. To customize NPCs and give them functions you need to first define them using the YAML file. The next section explains this process.
All NPCs act like players by respawning automatically upon death at their original spawn point. If you want an NPC to truly die you must set them up with either the "true death" command or in your yaml config for the NPC. During a true death NPC ragdolls do not disappear until a player removes them.
By default all NPCs will move around randomly, you can use the console command to make them stop moving, or edit the yaml config to have them stand still once spawned.
See all available commands in the Commands section below.
Using the YAML file
There is a file that comes with the mod called Example.VV.NPCS.yaml in the config folder with examples. This file must be manually renamed to VV.NPCS.yaml to load in the mod, this prevents mod updates from overriding your configurations. This file is where you can define your custom NPCs to be able to spawn them in game. You can also update existing NPCs from these configurations without needing to remove them from the game. When you update an existing NPC it will get overwritten and lose all data previously tied to it.
This file does not automatically live update if you change it while the game is running, but there is a command npcs_reloadconfig
to force reload it. If there is information missing from your NPC configurations it will be set to the default value and should not throw errors. If you see errors check you have used the correct data type for the config and do not have any spelling mistakes. The error should tell you which line is causing the problem.
The yaml file is local and will not sync to others. This file is not required on the server nor is it needed for the mod to function. It is purely for setup if you want to customize NPCs.
You can always reach out for support if you have trouble setting things up (see contributing at bottom).
NPC Types
Acceptable types include: None, Information, Reward, Sellsword, SlayTarget, Trader
Information
These NPCs simply say something when interacted with.
interactText
information will only display when the NPC meets both theirrequiredKeys
andnotRequiredKeys
criteria. These will check for the key presence in both the Player and Global key lists.interactKey
is awarded to the player(s) speaking with them.interactKeyType
field can be set to "Player" or "Global" depending on how this key should be awarded.defaultText
will be said whenever key requirements for theinteractText
are not met.
Example
Here is an example of a pair of NPCs. Ragnar1 will give the key "ragnarbrave" when interacting with them, which Ragnar2 requires to tell you a secret. Ragnar1 will only tell you their secret once, so you better pay attention! This key is set to "Global" so only the first player to access the NPC will be able to see the interactText for Ragnar1.
Note both of these are set to stand still on spawn, which can be very helpful when setting things up.
npcs:
-
id: Ragnar1
name: Ragnar The Brave
standStill: true
type: Information
notRequiredKeys: ragnarbrave
defaultText: "Did you say you had mead?"
interactKey: ragnarbrave
interactKeyType: Global
interactText: "Here's some gossip about Ragnar The Bold!"
-
id: Ragnar2
name: Ragnar The Bold
standStill: true
type: Information
requiredKeys: ragnarbrave
defaultText: "I love a good mead."
interactText: "He said that? Let me tell you a secret about Ragnar The Brave."
Reward
These NPCs have all the functionality of an information NPC plus the ability to accept an item in exchange for a reward item.
giveItem
,giveItemAmount
, andgiveItemQuality
are the quest requirements that a player must give the NPC.rewardText
,rewardItem
, andrewardItemAmount
are used for the physical reward once the NPC receives thegiveItem
.rewardKey
withrewardKeyType
(Player or Global) is given when the player successfully completes the quest.rewardLimit
ornotRequiredKeys
are two different methods to control how often a quest is completable:rewardLimit
: when set to 10 this will allow the quest the be completed 10 total times; when reaching 0 it will lock the quest. By defaultrewardLimit
is set to -1, which allows for unlimited completion.notRequiredKeys
: when set to the same key as the reward key will lock the quest the first time it is completed.
The difference between the interactKey
and rewardKey
is important to note here since interactKey
will always be given to the player when the Reward NPC is spoken to, where the reward key will only be given when reward conditions are met.
There are two "keywords" you can use when setting up your NPC text: {giveitem} and {reward}, which will be automatically replaced with the corresponding prefab and amount so you don't have to type it out.
Example
Here's an example of four NPCs that require you speak to them and complete their quests in order. Liv will give out a reward of a 2 star Flint Knife, which Vivica will accept and give the Rahshahs quest to bring him Deer Stew in exchange for Coins. The Jarl then rewards you for helping them all with an Iron Sword.
Liv is set up in a way that only the first 5 players there will get the Knife and the rewardText. Other players when talking to this NPC will still be able to receive the "liv" key but will not be given the reward and will only see the defaultText once the limit is reached. Again, note the difference between rewardKey and interactKey. Since Liv does not have any requiredKeys nor require a giveItem to give a reward you will never see the InteractText used, so it is not specified here.
Vivica is set up such that you must speak first to liv before you can see her interactText. When giving her the requested item she will say the rewardText. After this quest is completed Vivica will return to saying her defaultText. Since the interactKeyType
is not specified it will default to "Player". So every player will be able get the reward key.
Similar to Vivica, Rahshahs will also require a key to unlock the interactText, then return to saying his defaultText once the quest is completed.
Finally, the Jarl will give you a reward for helping all his people. Since the Jarl does not have a giveItem requirement the interactText will be displayed until the requiredKeys conditions are met. The only time you will see the defaultText is after receiving your reward.
This can be a bit confusing, so try spawning these examples and interacting with them in game to see how they work.
npcs:
-
id: Liv
name: Liv the Wise
type: Reward
notRequiredKeys: liv
defaultText: "Did you bring {reward} to Vivica?"
interactKey: liv
interactKeyType: Player
rewardText: "Can you give this to Vivica? She's too shy to admit she needs my help."
rewardItem: KnifeFlint
rewardItemQuality: 2
rewardLimit: 5
-
id: Vivica
name: Vivica
type: Reward
requiredKeys: liv
notRequiredKeys: vivica
defaultText: "I'm too busy to talk."
interactText: "Liv sent you? I guess I could use some help. I need {giveitem}."
giveItem: KnifeFlint
giveItemQuality: 2
rewardText: "My husband Rahshahs could use some help too, can you find him?"
rewardKey: vivica
-
id: MrHamHands
name: Rahshahs
type: Reward
requiredKeys: vivica
notRequiredKeys: rahshahs
defaultText: "What do you want? Go away."
interactText: "Vivica sent you? She didn't pay you!? I need {giveitem}, I will give you {reward} in exchange."
giveItem: DeerStew
giveItemAmount: 1
rewardText: "Thanks, I was hungry! Sorry about my wife, this should be more than enough to cover your help."
rewardItem: Coins
rewardItemAmount: 10
rewardKey: rahshahs
-
id: Jarl
name: Jarl Halsin
type: Reward
requiredKeys: liv, vivica, rahshahs
notRequiredKeys: thaneofvalheim
defaultText: "Good day citizen."
interactText: "Help my people and I will give you {reward}."
rewardText: "You actually did it, I'm impressed!"
rewardItem: SwordIron
rewardKey: thaneofvalheim
Sellsword
Not Finished.
SlayTarget
Not Finished.
Trader
Not Finished.
NPC Style
There are fields for setting the NPC appearance using item prefab names. Anything not specified will be left blank or randomized. Skin and Hair color require all r,g,b values to be defined to override; they are float values between 0 and 1. Overriding colors can allow you to make some very strange characters. When left blank these colors will be randomized to any possible vanilla customization value. There are commands to get these values from existing NPCs, so you can spawn a group of randomly generated ones to find possible vanilla values rather quickly.
When spawning an npc from the yaml file it will automatically clear all usual default items that exists on the original prefab. This can cause them sometimes to not have attacks. To allow npcs to keep their original items and attacks you can use the GiveDefaultItems
set to true. (This feature will get more attention and better support in the future).
npcs:
-
id: Ragnar3
name: Ragnar The Dressed
model: Player
modelIndex: 0
hair: Hair1
beard: Beard1
helmet: HelmetHat1
chest: ArmorTunic1
legs: ArmorLeatherLegs
shoulder: CapeLinen
shoulderVariant: 2
utility: BeltStrength
rightHand: KnifeFlint
leftHand: Torch
leftHandVariant: 1
-
id: Clown
name: Creepo The Clown
type: None
model: Player
modelIndex: 0
hair: Hair19
chest: ArmorTunic6
legs: ArmorRagsLegs
skinColorR: 0.9
skinColorG: 0.8
skinColorB: 0.1
hairColorR: 0.2
hairColorG: 0.3
hairColorB: 0.9
-
id: Boar
name: An Exquisite Specimen
model: Boar
giveDefaultItems: true
type: Information
interactText: "Feed me human!"
Supported Models
This mod currently only supports the following vanilla models. If a model is not specified the type Player is assumed:
- Player
- Asksvin
- Boar
- Charred_Melee
- Deer
- Draugr
- Dverger
- Fenring
- Fenring_Cultist
- Ghost
- Goblin
- GoblinShaman
- Greydwarf
- Greyling
- Lox
- Neck
- Skeleton
- Troll
- Wolf
Commands
You can spawn a random NPC on a chair or bed with RightCtrl + E (Subject to change in the future).
Command | Arguments | Description |
---|---|---|
npcs_reloadconfig | Reloads any changes to your yaml file | |
npcs_spawnrandom | [name] [Model] | Spawns a random NPC (only for supported models) |
npcs_spawnsaved | [id] | Spawns an NPC from the yaml config |
npcs_remove | Deletes the closest NPC, use with caution! | |
npcs_info | Lists the closest NPC's items | |
npcs_randomize | Randomizes the closest NPC | |
npcs_set | [id] | Updates the closest NPC from the yaml config |
npcs_set_move | Updates the closest NPC to walk around | |
npcs_set_still | Updates the closest NPC to stand still | |
npcs_set_sit | Updates the closest NPC to sit in the closest chair | |
npcs_set_calm | [radius] | Calms all hostile NPCs in the specified radius |
npcs_set_truedeath | Updates the closest NPC to not respawn upon next death | |
npcs_set_faceme | Makes the closest NPC turn toward you | |
npcs_get_skincolor | Returns the skin color of the closest NPC | |
npcs_get_haircolor | Returns the hair color of the closest NPC |
Possible Future Improvements
- NPC option to drop items on death.
- NPC options to perform more kinds of things than just sitting/standing/walking.
- Randomly generated NPC names.
- More NPC model options.
- Graves with signs so you can properly mourn your fallen NPCs.
- Cooldown timer on completing quests.
- Player quest tracker in the UI.
- Easier ways to list/save/change/copy NPC information.
- Necromancy options for fallen NPCs.
- Translation options.
- More complex data:
- Questlines: ability to have multiple dialog options and quest paths on one NPC.
- Items/Attacks: ability to assign multiple weapons and attacks ot one NPC.
Installation
This mod needs to be on both the client and server; the mod will enforce installation. Players without the mod will NOT be able to connect to the server.
If the mod is removed from the server after NPCs have been generated they will disappear.
Changelog
Moved to new file, it will appear as a new tab on the thunderstore page.
Contributing
All issues can be reported on the project Github. To report issues please be as specific as possible and provide the following:
- Version of this mod you are using.
- List of the other mods being used.
All feedback, ideas, and requests are welcome! You can message me at my discord Venture Gaming.