LORKHAN

Home Overview Installation Configuration Roleplay Settings Morrowind Settings Large Language Models Local LLM Guide Text-to-Speech Speech-to-Text Modders Guide FAQ Remote Hosting Logs and Debugging

Beta downloads Discord Patreon Mod Code Server Code

Roleplay Settings

Configure character development and context through profiles, then inspect individual NPCs when needed.

LORKHAN NPCs Menu

Open Configuration → LORKHAN NPCs, search for the character, and open its editor. Check Ref ID, Base ID and profile assignment before changing a character with a common name.

  • Identity: The base record describes the actor type. The reference distinguishes that actor in the world.
  • Biography: Describes background and personality. It is not the complete event history.
  • Profile: Supplies shared model and behaviour choices.
  • Voice ID: Chooses the character’s voice. Preview after changing it.
  • Prompt Head Override: Adds an individual exception to the usual guidance.

If the actor is missing, load the relevant area and check activation settings before creating duplicate records. Important supported characters can be represented as creatures; do not assume a humanoid-only search includes them.

Inventory and World Awareness

LORKHAN can describe observed characters, equipment and events to the model. The player-facing context is intended to use equipped items rather than reveal the player’s entire inventory.

Use Global Settings’ Context and Context Selections to control included observations. Descriptions and blacklists can further limit noisy item or location information. The recorded event history and the filtered prompt are different views; an event can exist in the log without being sent to the model.

For a wrong claim, inspect the current NPC, equipment and recent event context first. Adding a stronger personality prompt cannot correct a stale target or missing observation.

Memories and Dynamic Profiles

What this does: Gives characters access to relevant past events and allows their written profile to develop over time.

  1. Open the NPC and check its assigned profile.
  2. In Profiles, choose the memory tiers to include and set Context History Event Count.
  3. For automatic profile evolution, review Dynamic Profile and its field controls.
  4. Use the in-game Dynamic profiles menu to request a deliberate update, then inspect the result in the web editor.

Regular recent history, retrieved memories, a diary entry and generated profile text are separate inputs. Increasing a history count does not instantly rewrite all of them. Summaries and profile tasks also need their own working model assignments in Global Connectors.

For an existing NPC, check its own update choice: changing the default profile’s Dynamic Profile switch is not a bulk reset of previously discovered actors. Keep stable biography facts separate from generated interpretations.

Relationships

Morrowind disposition is on a 0–100 scale. In-game persuasion and bribes can change it, and supported AI interactions can also affect it. Treat the live game value as the reference when checking a mismatch.

Inspect the NPC’s relationships and recorded interactions in the server. A biography’s initial relationship descriptions are not the same as a history of conversations with your current character.

Diaries

What this does: Generates an NPC’s account of witnessed events, optionally as a readable book.

  1. Assign a working Diary LLM in the NPC’s profile.
  2. Enable Auto Diary for sleep-triggered entries. Enable Auto Diary Wait if waiting should also trigger them.
  3. Set Diary Cooldown to avoid repeated entries too close together.
  4. Review Diary Prompt and Context History Diary Event Count.
  5. Inspect the server diary view after an eligible event before troubleshooting the in-game book.
  • Physical Diary: Maintains a readable book in the NPC’s inventory using the latest five saved generated entries.
  • Include Latest Diary Entry: Adds the latest entry to response context; it does not generate an entry itself.
  • Diary event count: Zero uses the regular context-history setting.

An NPC cannot write a useful diary from events it never witnessed. Check its identity and history if the result seems to describe another actor.

Narrator and player

Open Configuration → Narration to configure the narrator separately from ordinary NPCs. Review its prompt, voice and event settings before enabling frequent narration. Use Configuration → Player for player speech; changing an NPC profile’s voice does not configure the player voice.

Oghma Infinium

What this does: Adds relevant world knowledge to conversations without placing the entire lore collection in every prompt.

  1. Open Configuration → Oghma Infinium and inspect the available knowledge.
  2. Choose a topic that should be relevant to your test conversation.
  3. In Global Settings, enable Oghma and review Topic Count and Result Limit.
  4. Ask about that topic, then inspect the response context to confirm the expected article was selected.
  • Oghma Topic Count: Limits extracted topics for a request.
  • Oghma Result Limit: Limits matching articles included in the prompt.
  • Force Racial Oghma / Force Location Oghma: Adds matching race or location lore when available.
  • Oghma Extractor Fallback: Allows a bounded model-assisted fallback when deterministic selection abstains. It has its own connector and timeout.

Example

A short article explaining a Great House’s public customs belongs in world knowledge. A guard’s private recollection of your last argument belongs in that guard’s history. Mixing these can make unrelated NPCs appear to know private events.

Use the modders guide when importing new articles. More articles per prompt is not automatically better: irrelevant material makes responses less focused and can increase latency.

Repeated names and reference groups

Two actors called Hlaalu Guard do not need to share a profile. Check reference IDs when reviewing their memories. Reference groups are for deliberate exceptions, such as several game references representing one named character.

Do not group all guards together simply because their displayed names match.

Director Mode and Actions

Open Text Chat and Interact, choose Dialogue mode → Director, and give a short instruction involving a nearby actor. The server’s dedicated Director connector must be configured; the four conversation slots are not a substitute for it.

Start with one supported action and a clear target. Check the Action Editor’s permissions and answer any Yes/No confirmation. Use Stop AI Actions if you need to halt activity.

Cheat is a separate execution mode. It still depends on the actions implemented by LORKHAN. These controls do not provide CHIM’s Skyrim quest, brawling or room-rental systems.