Jump to content

[mod] Voices of the Court: Roleplay Expanded


DaddyD1999

Recommended Posts

Posted

Voices of the Court: Roleplay Expanded


Voices of the Court: Roleplay Expanded

Voices of the Court: Roleplay Expanded (VOTC-RE) is a standalone AI conversation and roleplay application for Crusader Kings III.

VOTC-RE is a derivative work built from Voices of the Court / AliChat, Voices of the Court 2.0, and Voices of the Court - Community Edition.

The project originally started as World Cards and slowly grew into something much larger. VOTC-RE now includes World Cards, Character Cards, conversation controls, retries, continuation, Scene Cast, Conversation Director, Global Messages, Letters, additional CK3 actions, conversation history tools, scene controls, prompt customization, and many other changes built around making AI roleplay in CK3 feel more persistent and useful.

The main goal is simple: I want conversations to feel like they are actually part of your campaign instead of every interaction feeling completely disconnected from the last one.

VOTC-RE uses current CK3 information alongside things like World Cards, Character Cards, summaries, previous conversations, memories, diaries, Letters, and other saved information so the AI has much more to work with when interacting with your characters.

You do not need VOTC-CE installed separately.


Download

All VOTC-RE 1.5 application downloads are available here:

https://daddyd1999.itch.io/votcre15

Available files include:

  • VOTC_RE_1.5.0_Setup.exe — recommended installer
  • VOTC_RE_1.5.0_Portable.zip — portable application
  • VOTC_RE_1.5.0_CK3.zip — CK3 component
  • VOTC_RE_1.5.0_Source.zip — corresponding source

The CK3 component and source are also available with the LoversLab release.

Use Setup OR Portable, not both.


Why VOTC-RE Is Also on LoversLab

I have several adult CK3 projects and ideas that I may experiment with over time.

Some may remain completely separate mods. Where it makes sense, I may create optional compatibility patches or integration so VOTC-RE can recognize or work alongside them.

The same applies to existing adult CK3 mods made by other authors.

VOTC-RE already has systems such as World Cards, Character Cards, AI actions, conversation history, summaries, and custom prompts that make this kind of integration possible when I decide to support something.

Suggestions are welcome, but a suggestion is not a promise. I will add integrations when they are technically reasonable, useful, and something I actually want to maintain.


Current Adult Content Support

The current base release does not include dedicated sex-mod integration.

VOTC-RE can already handle mature, sexual, violent, vulgar, or otherwise explicit roleplay depending on the AI provider and model you choose.

I do not create, train, host, or distribute AI models.

Different models have very different restrictions, quality, context sizes, writing quality, and instruction-following ability, so model choice matters heavily for adult roleplay.

One model may handle explicit dialogue, violence, complicated relationships, and long scenes perfectly fine while another may refuse the exact same thing.

If a model refuses certain content, VOTC-RE cannot force that model to generate it.

Dedicated integration with adult CK3 mods may be added later through optional compatibility work.


World Cards

World Cards preserve important campaign information and bring it into the AI's context when it becomes relevant.

Cards can cover:

  • Characters
  • Events
  • Locations
  • Relationships
  • Items
  • Factions
  • Religions
  • Secrets
  • Old wars
  • Bloodlines
  • Artifacts
  • Sexual relationships
  • Personal history
  • Political situations
  • Custom campaign lore
  • Pretty much anything else you want the AI to remember

Character Cards can also be linked directly to CK3 Character IDs.

World Cards work alongside conversation summaries rather than replacing them.

Summaries are useful for remembering what happened during previous conversations, while World Cards are better for information that should remain part of the campaign for much longer.

VOTC-RE can also automatically create Character Cards after you interact with characters.

The automatic system is meant to give you a good starting point. If a character, relationship, event, or other piece of information is especially important to your campaign, you can edit the card yourself and make sure it says exactly what you want it to say.

VOTC-RE 1.5 also adds World/Story Card Book export, so books can now be exported instead of remaining tied to one installation.


Character Cards

Character Cards are World Cards made specifically for individual CK3 characters.

They can store information such as:

  • Personality
  • Character history
  • Relationships
  • Important conversations
  • Motivations
  • Opinions
  • Titles
  • Political position
  • Secrets
  • Rivalries
  • Friendships
  • Romantic relationships
  • Sexual relationships
  • Important campaign events
  • Character development that happened during roleplay

Character Cards can be linked directly to CK3 Character IDs, helping the application keep that information connected to the correct person.

They do not replace CK3's actual game information. They give the AI additional roleplay information that CK3 itself normally has no reason to keep track of.


Conversation Memory

VOTC-RE does not rely on one endless chat log for everything.

Depending on the conversation, the AI can be given information from things such as:

  • Current CK3 character information
  • Current game information
  • Recent conversation history
  • Conversation summaries
  • Memories
  • World Cards
  • Character Cards
  • Conversation Director
  • Diaries
  • Letters
  • Scene Cast
  • Other saved roleplay information

This allows characters and events to carry forward much more naturally between conversations.

The amount of information the AI can actually use at once still depends on the model you choose and how large its context window is.

More context is not always automatically better. If bad or outdated information is being kept around, giving the model even more context can sometimes make that worse instead of better.


Major Roleplay Features

VOTC-RE includes:

  • Writing Style controls
  • Saveable Response Retries
  • Continue This Response
  • Same-Day Conversation Continuation
  • Live message editing and deletion
  • Manual NPC Rounds
  • Choose Who Responds
  • Response Length controls
  • Conversation Director
  • Scene Cast Manager
  • Conversation Scene controls
  • Global Messages
  • World Cards
  • Character Cards
  • World/Story Card Book import and export
  • Generate Starter Book
  • Better World Card Activation
  • Conversation History management
  • Searchable saved conversation history
  • Editing saved conversations
  • Deleting saved conversations
  • Persistent summaries
  • Memories
  • Diaries
  • Additional CK3 actions
  • Reworked private Letter system
  • Standalone provider/application configuration
  • Custom prompts
  • Custom Prompt Presets
  • Expanded localization support

What's New in VOTC-RE 1.5

VOTC-RE 1.5 adds several new features while also fixing and improving parts of the application that needed more work.

World/Story Card Book Export

World and Story Card Books can now be exported.

This makes it much easier to:

  • Back up your books
  • Move them between installations
  • Save different campaign books
  • Share books with other users
  • Keep important World Cards without having to rebuild them manually

Existing book importing still works alongside the new export option.


Generate Starter Book Improvements

Generate Starter Book has been improved for much larger campaigns.

Very large campaigns with a lot of characters and accumulated information could previously cause problems when trying to generate a Starter Book.

That system has been improved so it can better handle campaigns that have grown far beyond a simple new game.

Character handling during generation has also been improved so existing characters are less likely to be handled incorrectly or unnecessarily recreated.


Relationship Improvements

Additional work has been done to reduce cases where the AI could save a relationship backwards.

For example:

  • A liege being described as the vassal
  • A vassal being described as the liege
  • A parent and child being reversed
  • The person performing an action being confused with the target
  • Other relationships where direction actually matters

This is especially important because once incorrect information gets saved into a World Card or summary, the AI can continue seeing that bad information later.

The changes in 1.5 are meant to make these relationships more reliable when new information is being saved.

AI can still make mistakes, especially if the conversation itself already contains incorrect information, but the application should now do a better job of keeping directional relationships clear.


Conversation History Editor

Conversation history can now be managed much more easily from inside the application.

You can:

  • Search old conversations
  • Find conversations by character or save
  • Edit saved conversation history
  • Delete individual conversations
  • Delete multiple conversations
  • Clean up old or incorrect roleplay information

Previously, editing old conversation history could require manually going into the application's files and changing the text yourself.

That should now be needed far less often.


Better Data Management

Several parts of the application now have better options for selecting and deleting saved information.

This includes systems such as:

  • World Cards
  • Summaries
  • Diaries
  • Conversation History
  • Letters
  • Global Messages
  • Custom Prompt Presets

This is especially useful for long campaigns where a large amount of information can build up over time.


Localization Fixes

A large amount of newer VOTC-RE interface text was previously still English-only.

That has now been corrected so the newer VOTC-RE features work properly with the application's supported languages.

Supported languages include:

  • English
  • German
  • Spanish
  • French
  • Japanese
  • Korean
  • Polish
  • Portuguese
  • Russian
  • Turkish
  • Chinese

This includes newer controls and menus that had been added after the original application but were never properly connected to the existing language system.


Conversation Director

Conversation Director gives you another way to tell the AI how the current roleplay should be handled.

It can be used for things such as:

  • Important campaign context
  • Long-term situations
  • Relationship information
  • Current political situations
  • Character motivations
  • Important instructions for a scene
  • Information you want the AI to consistently keep in mind

This is useful when something matters to the current roleplay but does not necessarily belong inside normal dialogue.


Scene Cast

Scene Cast gives you more control over who is actually part of a conversation.

Characters can be added or removed from the current scene so the AI knows who is currently involved instead of simply assuming every nearby or relevant character should participate.

Scene Cast works alongside:

  • Choose Who Responds
  • Manual NPC Round
  • Conversation Director
  • World Cards
  • Response Length
  • Conversation continuation

Large conversations can become increasingly difficult for AI models as more characters are added, so the model you use still matters heavily here.


Choose Who Responds

Choose Who Responds lets you decide which character should answer next during conversations involving multiple people.

This gives you more control over group scenes and prevents every response from being left entirely up to the model.


Manual NPC Round

Manual NPC Round allows the NPCs currently involved in the scene to speak without requiring the player character to say something first.

This is useful for arguments, council meetings, group conversations, reactions, or scenes where you simply want the other characters to continue talking among themselves.


Saveable Response Retries

If the AI gives you a response you do not like, VOTC-RE allows responses to be retried.

Retries can be saved instead of immediately replacing the previous version forever.

This makes it possible to generate different versions of a response and decide which one you actually want to keep.


Continue This Response

If the AI stops before finishing a response, you can tell it to continue instead of starting an entirely new reply.

This is particularly useful with longer responses or models that sometimes stop early.


Same-Day Conversation Continuation

Conversations can be continued later during the same in-game day while keeping the earlier conversation available.

This makes it easier to temporarily leave a conversation and return without treating it like the characters completely forgot what just happened.


Response Length

VOTC-RE includes controls for how long you want model responses to be.

Available options include:

  • Short
  • Medium
  • Long
  • Custom
  • Default

Different models interpret response length differently, but these controls give you a much easier way to tell the model roughly how detailed you want conversations to be.


Writing Style

Writing Style lets you control the general style you want the AI to use when generating conversations.

This can help push the model toward a certain type of dialogue, prose, tone, or roleplay style without having to repeatedly explain it inside the conversation itself.


Global Messages & Letters

VOTC-RE includes communication systems outside normal face-to-face conversations.

The Letter system is designed around private correspondence between characters and has been heavily reworked compared to the older implementation.

Global Messages provide another way for messages and information to move between characters.

These systems help roleplay continue without requiring every interaction to happen through a normal conversation scene.


CK3 Actions

VOTC-RE supports AI-interpreted CK3 actions so conversations can sometimes result in actual changes inside the game.

This allows roleplay to interact with CK3 instead of everything happening only through narration.

Supported actions include both inherited actions and additional actions added through Roleplay Expanded.

Because actions are interpreted from natural language, the AI model you use still matters.

Clear instructions and clearly named targets usually work better than vague wording.

The AI saying something happened in dialogue also does not automatically mean the corresponding CK3 action actually happened. Narration and game actions are separate things.


AI Providers

VOTC-RE does not come with its own AI model.

I personally use OpenRouter, although other supported providers can be configured.

Different models behave differently with:

  • Writing quality
  • Sexual content
  • Violence
  • Profanity
  • CK3 actions
  • Multi-character conversations
  • Long conversations
  • Scene awareness
  • Character consistency
  • Summaries
  • World Cards
  • Context size
  • Instruction-following

If a model refuses certain content, VOTC-RE cannot force that model to generate it.

VOTC-RE provides the connection between CK3, your campaign information, and the model. The actual writing still comes from whichever AI model you decide to use.


Installation

You need:

  • Crusader Kings III
  • VOTC-RE application
  • VOTC_RE CK3 component
  • A supported external AI provider/model

You do not need VOTC-CE separately.

Download:

https://daddyd1999.itch.io/votcre15

The Setup version is recommended for most users.

Portable users must install the supplied CK3 component separately and enable it in the CK3 launcher.

Before install if you'd like to see it working and in order check out this short, shitty, demo video. : 

 

 


Support / Suggestions / Integration Requests

For bugs, installation help, feature requests, adult integration ideas, or recommendations for mods you would like to see supported:

https://discord.gg/wNmGZQtyJJ

The Discord is also the best place to ask questions about VOTC-RE, World Cards, models, prompts, installation, CK3 actions, or anything else involving the application.


Credits, Attribution & Project Lineage

VOTC-RE is a derivative project and would not exist without the projects and contributors that came before it.

Original Voices of the Court / AliChat

Full credit goes to the original Voices of the Court / AliChat creators and contributors, including Durond / Demeter29, for establishing the original CK3-to-AI conversation framework.

Original source:

https://github.com/Demeter29/Voices_of_the_Court

Voices of the Court 2.0

Credit goes to the contributors who continued and expanded that work through Voices of the Court 2.0.

Source:

https://github.com/Voices-of-the-Court/VOTC

Voices of the Court 2.0 - Community Edition

A large amount of credit goes to MrAndroPC, Lisiyuan233, zhaowendao2005, the Chinese VOTC development community, and the wider VOTC-CE team and contributors.

Roleplay Expanded originally existed as an add-on/derivative of VOTC-CE 2.1.1-alpha.1. Standalone VOTC-RE no longer requires CE separately, but it remains derived from that codebase.

machiavelli — VOTC-CE maintainer/developer.

VOTC-CE source and contributor history:

https://github.com/Z-Jianxin/Voices_of_the_Court_Community

VOTC CK3 mod source:

https://github.com/Voices-of-the-Court/votc_mod

Voices of the Court: Roleplay Expanded

I do not claim ownership over original VOTC/VOTC-CE code, systems, prompts, interface work, backend architecture, CK3 integration, provider systems, game-data handling, or other upstream material.

My work covers the additions, modifications, fixes, and Roleplay Expanded systems introduced through World Cards, VOTC-CE Roleplay Expanded, and standalone VOTC-RE.

Where those systems modify or extend upstream material, the applicable upstream rights and license obligations remain in effect.

If I have missed an upstream contributor whose work is actually present in VOTC-RE, contact me and I will correct the attribution.


Licensing / Source

VOTC-RE is distributed according to the licenses applicable to the material from which it is derived, including GNU GPLv3 and CC BY-SA 4.0.

The corresponding VOTC-RE 1.5 source is available alongside the release:

https://daddyd1999.itch.io/votcre15

VOTC-RE 1.5 also includes the legal, copyright, attribution, and ownership information applicable to this release.

Upstream material remains governed by its original ownership and license.

GPLv3:

https://www.gnu.org/licenses/gpl-3.0.html

CC BY-SA 4.0:

https://creativecommons.org/licenses/by-sa/4.0/


Future Adult Integrations

If I create compatibility work for another author's mod, that does not give me ownership over that author's mod, code, assets, writing, or systems.

Their work remains theirs and remains governed by their own license and permissions.

I am open to future adult integrations where they make sense and where I have the time to maintain them properly.

That may include support for existing adult CK3 mods, compatibility patches, or separate projects I create myself.

The goal of any compatibility work would be to let VOTC-RE understand and interact with the relevant mechanics or roleplay information where possible, not to replace the original mod.

Add things that are actually useful without getting in the way of what already works.

 

 

If you enjoy VOTC-RE and want to help me keep building more weird, fun, adult-friendly CK3 stuff, I now have a Patreon for DaddyD1999's Mods and Content. There’s absolutely no pressure to support, but if you do, I genuinely appreciate it a lot. ❤️

https://patreon.com/DaddyD1999


  • Submitter
  • Submitted
    09/16/26
  • Category
  • Requirements
    https://github.com/DaddyD1999/VOTC-RE-1.0/releases/tag/VOTC

 

Posted

Quick Discord note: please keep things chill and respectful. Adult discussion is obviously fine, but don’t spam porn, flood channels with explicit images, or make the server miserable for everyone else.

If you need help, run into a bug, have an integration request, or think of a feature that could improve VOTC-RE, feel free to reach out. Recommendations are welcome.

Constructive criticism is also completely fine and genuinely useful. Just keep it constructive — explain what is wrong, what could be improved, and why. Random hostility, spam, or starting arguments over feature choices is not helpful.

Posted

When I saw that you had integrated AI into CK3 so that it can respond based on the events and circumstances of the current game, my first reaction was, “This is amazing!”

Unfortunately, I’m a Chinese-speaking player, so I can’t fully experience the strengths of your mod right away.

I really look forward to seeing a Chinese version of your mod in the future. Thank you for creating such an interesting and innovative mod!

Posted
3 hours ago, neomidd said:

When I saw that you had integrated AI into CK3 so that it can respond based on the events and circumstances of the current game, my first reaction was, “This is amazing!”

Unfortunately, I’m a Chinese-speaking player, so I can’t fully experience the strengths of your mod right away.

I really look forward to seeing a Chinese version of your mod in the future. Thank you for creating such an interesting and innovative mod!

Thank you! I really appreciate that. Chinese support is already built into the underlying VOTC application, and the AI itself should absolutely be capable of holding conversations in Chinese as long as the AI model/provider you are using supports Chinese properly.

However, after checking this, I believe some of the newer interface text that I personally added for Roleplay Expanded may still be English-only. If that is the case, that is on me — localization should have been properly carried through when I made the standalone release.

I’m putting a full localization check near the front of the next update. I want to go through the new Roleplay Expanded features and make sure the existing translations, including Chinese, are actually being applied everywhere they should be. So, you should not need to wait for Chinese AI conversation support itself, but the VOTC-RE-specific UI may still have some untranslated areas in the current release.

Thank you for bringing it up, because otherwise this is exactly the kind of thing I could have overlooked while focusing on all the new systems.

Posted
7 hours ago, Redhawk1111 said:

Hello!
How many languages does the application interface support?

Hello! The underlying application currently supports 11 interface languages:

English, Chinese, Russian, French, Spanish, German, Japanese, Korean, Polish, Portuguese, and Turkish.

One thing I do want to clarify is that Roleplay Expanded adds quite a lot of new UI on top of the original VOTC application. I am currently checking whether every one of my newer VOTC-RE-specific additions was properly connected to the existing localization system. Some of those newer labels may still appear in English in the current release.

I’m making that one of the priorities for the next update so the new Roleplay Expanded interface is properly translated alongside the rest of the application.

Posted

This is actually one of the more interesting AI-in-game approaches I've seen lately.

 

We've run into a very similar problem while building persistent characters in Virtual Twilight: retrieval alone isn't enough. Once a character can actually change relationships, opinions, location, motivations etc. you need a canonical state outside the prose, otherwise after enough conversations the model slowly invents its own version of the save.

 

CK3 feels like a brutal but very good stress test for this because there are so many actors and events moving at once.

 

I'm curious how you're resolving conflicts when a World Card / summary says one thing but the current CK3 state says another. Do you always treat game state as authoritative, or can the AI-side state override anything?

 

Not trying to hijack the thread, I'm genuinely asking because this exact state-vs-memory problem has eaten a stupid amount of our dev time.

Posted
16 hours ago, mardigain said:

This is actually one of the more interesting AI-in-game approaches I've seen lately.

 

We've run into a very similar problem while building persistent characters in Virtual Twilight: retrieval alone isn't enough. Once a character can actually change relationships, opinions, location, motivations etc. you need a canonical state outside the prose, otherwise after enough conversations the model slowly invents its own version of the save.

 

CK3 feels like a brutal but very good stress test for this because there are so many actors and events moving at once.

 

I'm curious how you're resolving conflicts when a World Card / summary says one thing but the current CK3 state says another. Do you always treat game state as authoritative, or can the AI-side state override anything?

 

Not trying to hijack the thread, I'm genuinely asking because this exact state-vs-memory problem has eaten a stupid amount of our dev time.

Don't mind answering at all friend, 

It’s a bit of both, really. CK3 still supplies the current live state, but VOTC-RE also carries persistent context from World Cards, summaries, conversation history, relationships, etc. I don’t hard-force one side to completely overwrite the other in every case; the system is more built around reconciling the live game state with the accumulated RP state and letting the model work from both.

There are places where the game obviously has to remain authoritative for actual CK3 mechanics, but on the roleplay/context side it’s intentionally less rigid than a pure “game state always wins” setup.

Posted

That makes sense, thanks for explaining. Keeping CK3 authoritative for the mechanics while letting the RP layer carry softer history is a much more interesting design than flattening everything into one source of truth.

 

The bit that kept biting us was when a softer fact becomes an actual state change. If a character decides they no longer trust someone during a conversation, do you persist that as a relationship change right away, or leave it in the summary/World Cards for later scenes to interpret?

 

I'm asking because we had characters convincingly act out a change in one scene and then quietly revert three sessions later. Fixing that meant being much more explicit about what gets written back, not just what the model can read. Curious how you're handling that boundary.

Posted
7 hours ago, mardigain said:

That makes sense, thanks for explaining. Keeping CK3 authoritative for the mechanics while letting the RP layer carry softer history is a much more interesting design than flattening everything into one source of truth.

 

The bit that kept biting us was when a softer fact becomes an actual state change. If a character decides they no longer trust someone during a conversation, do you persist that as a relationship change right away, or leave it in the summary/World Cards for later scenes to interpret?

 

I'm asking because we had characters convincingly act out a change in one scene and then quietly revert three sessions later. Fixing that meant being much more explicit about what gets written back, not just what the model can read. Curious how you're handling that boundary.

Yeah, that boundary is pretty much where I draw the line too. If it’s a soft RP change like trust, resentment, affection, suspicion, etc., I generally let that live in the summaries/history/World Card side and carry forward as persistent context.

If it maps to an actual CK3 mechanic or one of the supported actions, then it can become a real game-state change. I don’t let normal prose silently rewrite CK3 state just because the model decided somebody “trusts you less” in one scene.

That does mean the persistence quality depends heavily on the summaries/cards being good enough to keep that change alive later, which is exactly why I’ve spent so much time on the memory/World Card side of VOTC-RE. I’m actually auditing some of that again for 1.5 right now, especially relationship direction and how those facts are carried forward.

So basically: hard mechanical changes get written back when there’s an actual supported game action; softer relationship development stays in the RP persistence layer unless/until it becomes something concrete.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...