• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
Showing developer posts only. Show all posts in this thread.


Senior Programmer - Crusader Kings 3
Paradox Staff
78 Badges
Aug 28, 2013
  • Crusader Kings III
  • Stellaris: Federations
  • Battle for Bosporus
  • Stellaris: Nemesis
  • Hearts of Iron IV: No Step Back
  • Europa Universalis IV
  • Crusader Kings III: Royal Edition
  • Europa Universalis 4: Emperor
  • Stellaris: Necroids
  • Crusader Kings II
  • Crusader Kings II: Holy Fury
  • Imperator: Rome - Magna Graecia
  • Crusader Kings II: Charlemagne
  • Crusader Kings II: Rajas of India
  • Crusader Kings II: Sons of Abraham
  • Crusader Kings II: The Old Gods
  • Europa Universalis IV: Rights of Man
  • Europa Universalis IV: Cradle of Civilization
  • Stellaris: Synthetic Dawn
  • Surviving Mars
  • Europa Universalis IV: Mandate of Heaven
  • Crusader Kings II: Monks and Mystics
  • Tyranny: Archon Edition
  • Europa Universalis IV: Rule Britannia
  • Crusader Kings II: Reapers Due
  • Hearts of Iron IV: Colonel
  • Stellaris Sign-up
  • Hearts of Iron IV: Expansion Pass
  • Stellaris: Apocalypse
  • Stellaris: Lithoids
  • Stellaris: Distant Stars
  • Europa Universalis IV: Dharma
  • Shadowrun Returns
  • Imperator: Rome Deluxe Edition
  • Prison Architect
  • Imperator: Rome Sign Up
  • Stellaris: Ancient Relics
  • Age of Wonders: Planetfall
  • Crusader Kings II: Conclave
  • Crusader Kings II: The Republic
  • Victoria 2
  • Cities: Skylines
  • Europa Universalis IV: El Dorado
  • Crusader Kings II: Way of Life
  • Stellaris
  • Mount & Blade: Warband
  • Crusader Kings II: Horse Lords
  • Europa Universalis IV: Common Sense
  • Crusader Kings II: Sunset Invasion
Hello everyone and welcome to the 37th CK3 Dev Diary!

I’m Matthew, one of the Programmers on the CK3 team, and today I am going to talk to you about the modding in Crusader Kings III!

Mods are something very important to the team and something especially close to my heart. I got started at Paradox as a Content Designer due to my modding work on Crusader Kings II, so being able to make sure the sequel has lots of modding opportunities and trying to give back to the community that aided me in getting into this industry is something I am very passionate about, and I know others on the team had similar starts in modding as well.

We’ve aimed to make the game a lot more open in terms of what can be achieved in modding: we’ve got over 80 database object folders (some even with sub-folders), a very versatile event system structure, a GUI system that can be fully changed, history files, localization, sound, music, and more! So huge parts of the game can be changed to suit your needs!


[screenshot of common database folders]

In the rest of this diary I’ll talk less about what you can do overall and more spotlight some things I think modders of CK2 will be excited about, as otherwise this diary would be huge and I need to get back to coding at some point.

At its core our scripting language in Imperator and Crusader Kings III is based on an in-house grand strategy library called Jomini, which acts as a more GSG focused layer used on top of our Clausewitz engine.

When Imperator released I posted a lot of information about the things that come directly from Jomini and which are shared between both games, so I would recommend checking out my Grand Jomini Modding Information Manuscript thread if you are an interested modder.

If you’d like to know more about event scripting then Dev Diary 30 had a very good coverage of that which you should check out!

Feel free to ask questions about both the linked threads in this one as well!

Character Interactions
To focus more on game level things, one of the biggest things changed from CK2 is the character interactions.

For a brief history lesson in CK2 modding, most of these core interactions were hardcoded, things like arranging marriages, declaring war, alliances etc. It was only after quite a few patches that the ability to add custom “targeted decisions” was introduced, and it’s worth noting that it was only the ability to add or modify those targeted decisions - the older hardcoded core interactions were still not particularly moddable.

For CK3 we wanted to open all of that up to go through one unified character interaction system, so every action goes through our script system now. This gives many benefits: with script being able to change it we can now change weights for the AI’s use of these actions with just a few text file changes instead of needing code time, we can change who can do them, and what people are considered good matches etc. And of course that opens it all up for modders as well.

The AI can also be scripted to use all of these custom interactions, tell them who’s a good target, as well as how often they should evaluate it (which is important for performance).

There are still some hard coded links with the interactions, specifically when it’s an interaction that’s needed to be used by the AI in a non-trivial manner. These interactions are all marked clearly, though, and if you attempt to remove them then the game will give you a warning when loading that it really needs this interaction so put it back please. This behaviour in fact applies to almost all hard coded database objects, not just those which are interactions.

For reference here is a full list of all the options interactions can use that impact how they are taken, received, responded to, shown graphically and used by the AI:
my_interaction = {
interface_priority = number # Used by interaction menu
common_interaction = yes/no # Used by interaction menu
category = interaction_category_hostile # Used by interaction menu
is_highlighted = trigger # Should the interaction be highlighted in the menu
highlighted_reason = loc_key # Tooltip if highlighted in menu
on_decline_summary = dynamic description # Flavor text that is shown under acceptance widget. Use it when you need to draw more attention to the on decline effect
special_interaction = type # This interaction uses specialized GUI
special_ai_interaction = type # This interaction runs specialized code that identifies the interaction by this
interface = call_ally/marriage/grant_titles/etc. # What interface does the interaction use?
scheme = elope/murder/etc. # The type of scheme the interaction starts
popup_on_receive = yes # Have the interaction pop-up for the recipient when received
force_notification = yes/no # Force diplomatic item if interaction is auto-accept
pause_on_receive = yes/no # Pause the game on receive. It usually makes sense to combine it with popup_on_receive
ai_accept_negotiation = yes/no # If the interaction is declined negotiations will start. We don't show "won't accept", etc. because there is still a possibility that the interaction will be accepted via negotiation event chain
hidden = yes # Is the interaction hidden?
use_diplomatic_range = yes/no/trigger # Does this interaction check diplomatic range? Yes by default
can_send_despite_rejection = yes # Interaction can be sent and the ai might reject
ignores_pending_interaction_block = yes # If the actor is a player and the recipient already has received an interaction from them pending a response, can this interaction be sent anyway. Defaults to no
send_name = loc_key # The name of the interaction in context of it being seen once sent. Defaults to database object key
needs_recipient_to_open = yes # Does the interaction need a recipient set to be able to be allowed to open and be shown. Defaults to no
show_answer_notification = no # Does this show a response info pop up when an interaction is answered if the actor is a player. Defaults to yes
show_effects_in_notification = no # Should the effects of the interaction be shown in the notification window when an interaction is sent. Defaults to yes

icon = texture_path # Icon used in various places. Default is gfx/interface/icons/character_interactions/my_interaction.dds
alert_icon = texture_path # Default is gfx/interface/icons/character_interactions/my_interaction_alert.dds
icon_small = texture_path # Default is gfx/interface/icons/character_interactions/my_interaction_small.dds
should_use_extra_icon = { always = yes } # When to show an extra icon. Tooltip key is <key>_extra_icon
extra_icon = "gfx/<...>/hook_icon.dds" # Icon to show when should_use_extra_icon is true

target_type = type # Possible types: title, none (default)
target_filter = type # See FAQ for possible types

ai_maybe = yes # The ai can reply maybe
ai_min_reply_days = 4 # Minimum days before ai replies
ai_max_reply_days = 9 # Maximum days before ai replies

desc = loc_key # Short description of the interaction
greeting = negative/positive # Sets tone in request text
notification_text = loc_key # Request text
prompt = loc_key # What text should be shown under the portrait? (For example: "Pick a Guardian")

show_effects_in_notification = yes/no # Should the effects be shown in the notification?

cooldown = { years = x } # How long until the decision can be taken again?
cooldown_against_recipient = { years = x } # How long until the decision can be taken against recipient again?

is_shown = trigger # Is the interaction available and visible between scope:actor and scope:recipient
is_valid_showing_failures_only = trigger # Is the interaction valid to be selected in it's current setup, trigger only displays failures
is_valid = trigger # Is the interaction valid to be selected in it's current setup
has_valid_target_showing_failures_only = trigger # TODO
has_valid_target = trigger # TODO
can_be_picked = trigger # TODO
can_be_picked_title = trigger # TODO
auto_accept = yes/no/trigger # Is the interaction automatically accepted, or can recipient decide
can_send = trigger # Can the interaction be sent
can_be_blocked = trigger # Can the interaction be blocked by the recipient (i.e. by a hook on the actor)
is_highlighted = trigger # Should the interaction be highlighted in the menu
can_send = trigger # Can the interaction be sent?

redirect = {} # This changes the redirection of characters using the scopes actor, recipient, secondary_actor and secondary_recipient
populate_actor_list = {} # Everyone sorted into the list 'characters' has the potential of being shown to be selected. Uses the scopes actor, recipient, secondary_actor and secondary_recipient.
populate_recipient_list = {}

localization_values = = {} # To be able to use values in loc (for example: RANSOM_COST = scope:secondary_recipient.ransom_cost_value lets you use $RANSOM_COST|0$ in loc)

options_heading = loc_key # Text shown above options block - describes all options in general
send_option = { # Adds an option
is_shown = trigger # Is option shown
is_valid = trigger # Is option selectable
current_description = desc # Tooltip
flag = flag_name # If selected then scope:flag_name will be set to yes
localization = loc_key # Loc_key for option label
starts_enabled = trigger # Trigger for whether this should be on when the window opens. If not defined, defaults to off
can_be_changed = trigger # Trigger for whether this option can be changed from its default
can_invalidate_interaction = bool # If yes then when the AI picks an interaction it will do the full can send this entire interaction check instead of the more performance saving checking of recipient refusal and ai will do, use with care and profile it
# Options should avoid preventing an interaction from sending (except by the recipient refusing), as we assume that to be the case in the AI for performance reasons, use can_invalidate_interaction if you need it to be re-checked
send_options_exclusive = yes/no # Are the options exclusive?

on_send = effect # Executes directly the interaction is sent
on_accept = effect # Executes when accepted by recipient
on_decline = effect # Executes when declined by recipient
on_blocked_effect = effect # Executes when blocked by recipient
pre_auto_accept = effect # Only executes if the interaction was auto accepted. Done before any other side effect (E.G., hard coded ones like marriage)
on_auto_accept = effect # Only executes if the interaction was auto accepted

reply_item_key = loc_key # The key to the loc to show in the interaction item tooltip. Receives the name of the interaction in $INTERACTION$. Default value "INTERACTION_REPLY_ITEM"

# These loc keys are shown to the player when sending the interaction. The meaning is what is going to be the answer from the target.
pre_answer_yes_key = loc_key # The key to the loc when the interaction is going to be accepted. Default value "ANSWER_YES"
pre_answer_no_key = loc_key # The key to the loc when the interaction is NOT going to be accepted. Default value "ANSWER_NO"
pre_answer_maybe_key = loc_key # The key to the loc when the interaction maybe is accepted. Receives the acceptance value in $VALUE$. Default value "ANSWER_MAYBE"
pre_answer_maybe_breakdown_key = loc_key # The key used to localize the chance of acceptance of an interaction with provided chance value. Defaults to ANSWER_SUM_MAYBE

# These loc keys are shown to the player when answering an interaction.
answer_block_key = loc_key # The key to the loc to block the interaction. Default value "ANSWER_BLOCK"
answer_accept_key = loc_key # The key to the loc to accept the interaction. Default value "ANSWER_YES"
answer_reject_key = loc_key # The key to the loc to reject the interaction. Default value "ANSWER_NO"
answer_acknowledge_key = loc_key # The key to the loc to reject the interaction. Default value "ANSWER_ACKNOWLEDGE"

cost = { # Scripted cost for the interaction. The interaction will be disabled if the actor can't pay up, and the cost will be subtracted from the actor when the interaction is sent. Renown can only be spent by the dynast.
piety = {}
prestige = {}
gold = {}
renown = {}

ai_set_target = {} # Set scope:target to make the AI target something specific. Title targeting interactions don't need this
ai_targets = {
ai_recipients = type # Which characters does the ai consider as recipient for the interaction, can be scripted multiple times to combine lists
# Available lists are in the "ai_targets" section of this file (trying to add an invalid list will trigger an error message with all available )
chance = 0-1 # A low chance, such as 0.25, randomly excludes that number of characters from being checked - this is useful for saving performance
ai_target_quick_trigger = { # Quick triggers for the ai_targets
adult = yes # The target needs to be adult
attracted_to_owner = yes # The target needs to be attracted to owner
owner_attracted = yes # Owner needs to be attracted to the target
prison = yes # Target must be in prison

ai_frequency = months # How often should the ai consider doing this interaction
ai_potential = trigger # Will the ai consider trying this interaction
ai_accept = mtth # Will the ai accept a request for this interaction
ai_will_do = mtth # How interested is the ai in sending this interaction (tested after selecting targets) 0-100 percent chance, will be clamped.
# Note that for title interactions, each individual target title will get evaluated, and the one giving the highest ai_will_do will get used. If the interaction has options, the combination of options that gives the highest ai_will_do will be used.

Combining Mods
Combining multiple mods together has always been a bit tricky but I wanted to try and make some gains with compatibility so that it doesn’t require as many manual patches.

To aid in this a bit I’ve made it so database entries can be overridden by key even if that new entry is in a different file. This means if you want to override what the lunatic trait does then instead of needing to copy the entire traits file just to change one entry you can just make your own file just containing your new definition of what the lunatic trait does, such as giving it a boost in learning, prowess, and attraction opinion like I have done below!


[screenshot of a file overriding the lunatic trait]


[screenshot of the new lunatic trait]

This also applies to files from other mods, as long as yours is loaded first, so you can overwrite traits and other database elements from other mods

Currently we do not support appending to a definition instead of fully overwriting, as we’d need to rework a good chunk of things and test it extensively though it is something I am keeping in mind for the future.

Alerts, Issues and Notifications
As I mentioned in Dev Diary 16, all of the new interface utilities we have for explaining the game are moddable. Which means you can add, remove, and modify any of these things through script instead of them being hard coded like in CK2.

I’ll start with the notifications and toasts as they are the simplest. You simply make a database entry in the common folder for your notification and then wherever you want to run it from you use the send_interface_message or send_interface_toast effect.

Those effects take the type of message as well as optional overrides for the title and text instead of using what was scripted in the database. They can also take any number of effects to run which will then be included as text when displayed, though it is often recommended to use a custom tooltip instead of bloating the message with a lot of mechanical text.

For alerts, advice and current issues they all go through the same “important actions” system, the core difference between them is which type they are specified to use which controls their visual appearance and location.

These important actions have a check_create_action and effect block, both run interface effects (specially marked effects that do not modify the game state across MP but just local UI things) to see if they can be created and what to do when clicked.

The main interface effect to run in check_create_action will be the try_create_important_action which attempts to create a UI element for this action type and this will usually be behind an if check.

In the effect block for when the UI element is clicked there are a couple of things which are a good idea to run, if its a piece of reactive advice then using the start_tutorial_lesson is a great idea, and for alerts or issues then the open_view_data effect is the way to go to open the window that can help address whatever is causing the alert or issue!


[a custom alert]

Note: Whilst making this dev diary I actually found out that in 1.0 adding a custom icon like you see via a mod is actually not functional, it's already been fixed for 1.1 but I thought I should note that here quickly for people coming back to this dev diary to tell me off when it doesn’t work right away.

The suggestions are similar to the important actions, but also have fields for the weight which checks how important the suggestion is to the player and a score which checks which potential target of a suggestion is best.

For example, in the fabricate claim suggestion the weight is based on if there is anything nearby you could fabricate on, how many claims you already have, and if you are already fabricating a claim. The score for which title to suggest you fabricate is based on a much larger list of values such as the development level of the county, how easy it’ll probably be to conquer, if you share a faith or culture, etc.

Scripted GUIs
Like with Imperator the interface is incredibly moddable, the GUI scripting language whilst different from the normal database and event script is still very versatile and lets you change both the appearance and positioning and full functionality of almost all the GUI elements in the game. We also have a GUI debug mode in game which allows viewing through the hierarchy and opening to the file and line of where elements are defined which makes working with the interface a lot easier.

Currently we do not support creating your own new windows GUIs (though it is on my never ending to do list), but the easy work around there is just to make them as children of the main HUD window, which is always shown, and then you can have anything.

As is listed briefly in the Jomini Modding info I linked it is possible to make scripted GUIs, which allow a link to exist between the GUI system to the normal script system so you can test for if different triggers evaluate true or false and to run effects in the game state safely across multiplayer.

I am very excited to see what people end up doing with this especially, there should hopefully be a massive reduction in the number of hacks needed to display information now that real interfaces can be made for mods to show things about their unique mechanics.

Here is a very small example of a custom interface I put together to give you a little button you can press for “fun” aka for murder against another adult character of a different faith.



[screenshot of a custom interface button and its confirmation pop up]



[screenshot of the script and gui entry for the button]

Thanks for tuning in folks! I know this diary might have some more niche appeal, for those of you looking for a look at more gameplay then make sure to tune in for our next gameplay stream!
  • 76Like
  • 49Love
  • 31
  • 4
  • 2Haha
I will take a guess and say that marriage is still (mostly) hardcoded?
Not really, it is one of the ones that if you remove the game will yell at you for but it is mostly decided in script who can marry who, the various extra effects of the interaction, who the AI can and prefers to marry etc.
  • 18Like
  • 12
  • 10
  • 1Love
  • 1Haha
Will there be an on_action that triggers at the start of pregnancy instead of when the trait shows up, or any way of altering the 'unborn' segment? I tried to make a mod to make more fertile and tall etc characters have more twins in CK2, but couldn't find a method that worked.
There is not one for the start of pregnancy I don't think, we have one for the mother and father when the pregnancy is revealed which adds the trait. We do have effects to modify the unborn character though such as setting if they are a known bastard, changing the assumed father, and setting the number of children.

What about mods changing localisation files (like improved localisations for other languages)? Will they affect checksum?

EDIT: Also, will the localisation files include things like character or dynasty names (like Imperator)?
Localization and gui still effects the checksum yes as both need to be checked otherwise using the new more powerful gui and localization system mods could cause cheating and out of sync issues.

As a modder too, I really liked this DD! Thank you :) Howewer, I'd like to ask two questions:
1. About title localisations, the game'll handle it in the landed_title folder, just like in CK2 or in a similar way, like in EU4?
2. How can the game handle special characters, like č, š, ž ? CK2 had some limitation with that.
1. Not sure what you mean with that question to be honest
2. We should be able display those just fine

How will map modding work? One of my biggest gripes with Imperator Rome modding was that the map, country, and history setup was all in a single massive setup file.
We have a similar split of files like CK2 did with various map, province and history folders containing the files to change. Not a handful of massive csv files like Imperator has.
  • 13
  • 4Like
  • 2Love
  • 1
  • 1
One of my favorite features in Imperator was the GUI array/list feature you added later. Is that also supported in CK3 or not yet?
Yep, I probably could've made an example GUI using that as we share that functionality with Imperator. Any things added to a variable list on a scope can be retrieved in the gui via Scope.GetList( 'name' ) and then worked with.

Has the character id system been changed?

Currently in CK2 it seems you can't use namespaces in events or characters (not in eu4) like in EU4. So every character has an id in certain ranges.

I know you reworked events entirely, but what about this?
Historical Character IDs can be any string now.

How moddable are succession laws? In that screenshot of the game directory there is only a folder for elective...
You can mod in new ones but they will need to pick a specific rule to use which does have a hardcoded number, you can make your own partition law with extra requirements or fancy names but you cannot make a new type of succession as that is in code.

This is great. I had a lot of joy modding CK2 and I'm really glad to see that modding CK3 will be even more flexible. Looking forward to working on it! I have gone through the linked Jomini page and it looks very nice.

I have the following questions:
  1. Will there be a documentation of all the available conditions, commands, scopes etc. on release?
  2. Is there any plan to make an official tool like the Validator for CK2 to check for scripting errors in mod code?
  3. Will there be color-coded language available for Notepad++ or any IDE?
These tools will be really helpful in making the process of modding efficient.
1. There is a script_docs console command which outputs all triggers, effects, scope types, event target links, modifiers, and on actions to log files.
2. In theory the game is the validator, the game aims to catch and log any errors already as we want our in house Content Designers to get those same errors, we've put a lot of work in to make sure CK3 is a lot better at logging various types of errors so I doubt an external tool like the Validator will be something we work on. If the community does then anything we fail to error on I'd love to see posts about so we can try to catch them as well.
3. I don't know on that, I know some people in house have stuff and there are various community tools as well. So I'm sure something will come out from some source eventually!
  • 17
  • 1
Making it easier to mod just one small element of a file instead of having to replace the entire one is huge and should help with compatibility. In fact I'd say it's one of the biggest changes to modding if not the whole game over CK2.

Of the folders listed in the screenshot, I'm particularly interested in what ethnicities, flavorization, genes, and story cycles might do.
Ethnicites are the range of how various portrait genes are distributed, for example the usual skin tone range or facial features more or less promiment in different parts of the world.

Flavorization is how we name titles and characters, for example based on culture and government whether someone is a Count or an Earl or if a title should be a County or Earldom.

Story cycles are a sort of event container that can hold variables and run updates intermittently. For example, when owning a cat is a story cycle which when setup will store various variables for the cat age, eye color, gender, and fur and add some modifiers. Then in various intermissions it will do things like every 365 days increase the age counter, prompt you to name it if you have not already, trigger some random events, or have the cat die of old age. It then has a cleanup effect to remove the various modifiers and things it may have applied. It can also handle what to do if the owner of the story dies, for the cat one it then attempts to pass the pet on to a family member or friend etc.
  • 15Love
  • 14
  • 3Like
  • 1
Thanks for diary. Has a question about the calendar.
How much is it moddable? Can i change names of [days] into [hours], change number of months? in other words, for example make 30 days into 24 hours, and 12 months into 365 days. So every year would x24 times slower. If yes, then it could be possible to make calendar like in hoi4, so all modders could make deep role play game of some interesting historical period. Just curious, thanks for any answer.
You can relocalise them but other than that they are hardcoded, changing the time scale would need more support on the game end to do and I'd argue its a fairly niche modding need.

I have no idea what most of this is, but I like it. Seems strange to me that the fix for that one issue is being pushed back to the 1.1 release if it's already done, though. Is that a "We don't have time to implement this because we're in hardcore crunch time" thing, or is it just a game dev thing?
As @ShadyGuy_SuspiciousGoal said, the 1.0 version is frozen from any changes unless they are of the severest impact and very critical as we do not want to risk introducing other issues into the build that could be worse than the one we fix.
So for something low impact and that does not effect the vanilla game like this issue it is not considered a worthwhile risk to take.

This one seems to have got lost and I'm curious as to the answer. Are cultural landed title name changes handled like CK2, like EU4 or in some other way?

To extend that question, how about titles themselves? e.g. CK2's "city_empire_of_basque;...;", "tribal_duke_female_bohemian;...;" system or something more like EU4's system?
I answered in response to someone else, its handled by our "flavorization" system which deals with both the names of titles and the styling of character names as Count or Earl etc.

I can see how that would be a concern for multiplayer, but on the other hand I am annoyed how in Stellaris for example something like a ship name list mod makes my game ineligible for gaining achievements.

Any chance the game might calculate two checksums? One for the purpose of playing multiplayer and another for the purpose of achievement eligibility that will ignore anything that doesn't actually affect game mechanics?
It is something I have thought of, splitting into a hard and soft checksum but I've not had time to do this as its not really a high priority compared to features, bugs or performance work. It is one of the things on my list of things to investigate during our personal development time but that list of things to look at is pretty massive so no promises.
  • 20
  • 7Like
Is there a reason why you're avoiding answering any questions about modding character models?
Mainly cause I don't know the system too much in depth and our artists are busy so we covered other things in the dev diary. I know it is possible to mod the models, we use the same basic system as Imperator and they have multiple fantasy mods so I know its definitely feasible to do a variety of stuff there.

But I do not know enough of the syntax or files needed to change to do much of those things.
  • 12
  • 11Like
  • 1Love
  • 1
This isn't directly linked to the content of either this dev diary or #30, but it's a question about modding, so...

Perhaps my favorite mod for Crusader Kings 2 is the Game of Thrones mod, which (among other features) has dragons. As many of you on the forum likely know, the mod tracks dragons like characters—just like Chancellor Glitterhoof, Spymaster Mittens, and Sir Bearington. All of these nonhuman characters were possible with 2D portraits because you can just draw an animal or dragon and stick that in the project folder.

However, CK3's portraits are human-shaped character models, and while there are many ways to alter proportions, facial structure, texture, etc, there's no indication that you can simply replace that model with another one (not that modeling and rigging a dragon model is a trivial task in the first place!) How do you see mods with nonhuman characters as a central feature, whether they be rulers' accessories (as with the GoT mod) or rulers in their own right (as with the Faerun mod and Pope Glitterhoof) faring in Crusader Kings 3?
I had hopes the DD would feature character model modding. Will there be possibilities to add/change textures, meshes and morphs (assuming morphs are used)? And the format/tools used.
I see that there's a dna_data directory in the database. Will that let us mod the character meshes and textures? If so to what extent? Could we mod in playable Orks and Elves? What about horses and bears?
What about modding character models, either introducing new variables for existing models (pointy ears, etc.) or adding new models of nonhumans altogether?
Hi Matthew another question, hopefully this one is good enough: Can you mod animation? Can we add new animations ourselves? How complicated is it?
how moddable are character models? will it be possible to replace the character models with something entirely different or are they required to be humanoid?
How user-friendly is editing character models/portraits, or is that hard-coded?

So a lot of questions about 3D character modding (understandably!). I'll try to explain a little bit more about it here.

The good news is that most aspects of the portraits should be moddable. The easiest to change are things related to genes and ethnicities. Quite a lot can be done without editing any meshes or textures at all. Adding a new ethnicity is actually very simple. The same goes for historical and custom characters. You can use the portrait editor available from the console to design a DNA, add it to dna_data script files and then just add a reference to it in the history entry for that character. Making everyone look like monstrous caricatures is also very easy by just ramping up the values for extremes in the ethnicity script files.

Now for more ambitious modding projects, like adding new races and species. I know there is a tool to import .mesh files from the game (by ross-g somewhere on these forums). So what you would need to do to create elves or orcs or any other humanoid is to import the male and female head models and rigs into Maya and do whatever changes to them by adding blend shapes and then export it using our Maya exporter tool that we have released publicly. If you make bigger changes you're likely going to have to edit the rig as well. And this is where things become tricky. While it should be perfectly possible to change the rig the game uses predefined portrait types for male, female, boy and girl. It isn't really built around the concept of several different species. But it might still be possible with some creative modding. I could imagine implementing dragons for example as an "attachment". Essentially a dragon suit :D (It would not have to match human proportions or anything). It may or may not be possible to give it it's own rig and animations, I'd have to look into that to be sure. But a static dragon should at least be doable as an attachment.

Smaller things, like adding new clothing and headgear (for humans), is much more straight forward and is essentially following the procedure outlined above.

All textures are very easy to edit. And it's easy to add new ones as well. They're all in .dds format which is possible to edit in Photoshop with the free plugin from NVIDIA. The same goes for the color palettes we use. So adding outlandish skin colors and hair colors for example is again very easy.
  • 21
  • 5Love
  • 3Like
  • 1
Is it possible to add custom "Currencies"? I imagine fantasy overhauls or any other mod with magic will want to add an Mana system (not EU mana, actual magical Mana), and similar things for other kinds of mods. In CK2, most mods had to misappropriate piety or introduce some placeholder-offmap to use its grace mechanic, which are rather hacky workarounds. By comparison, Stellaris has a rather extensible (even if problematic compatibility-wise) resource system, will there be anything like that?
You can store it as a numeric variable on the characters then just grab that number out in the interface somewhere, so that should be entirely fine to do.
  • 13
  • 1Love
Can you elaborate at all on what that system looks like? We'll know soon enough, but is it a localisation-based csv system like CK2 or a common file-based system like EU4?
It is a folder in common though I don't know how EU4 does it/

For us its key with a priority and various options such as checking culture, faith, government, independence, council position, and more which will pick whatever conditions are met of the highest priority and use that one.
  • 12
  • 1Like
Is the ethnicity skin tone handled in straight line (dark-light spectrum) or can you add new ones that blend with them? Like normal black, white, and mixed humans, who can also breed with blue or green humans to produce offspring with new shades? Would it work so that we can have ALL the vanilla skin colors AND a number of custom ones able to freely exchange genes in-game?

So the skin color palette that we use is a square image with gradients from light to dark on the y axis and from reddish to yellowish on the x axis.

Skin color is simply defined as a coordinate on this palette. Children that are born will get a skin color that is picked somewhere along the line between the parents' coordinates.

So you could definitely add more colors to the palette but you would have to put some thought into which colors are next to each other. If you would have all the colors of the rainbow in the palette, for example, a child between a red skinned person and a blue skinned person might get green skin :)

  • 14
  • 8Love
  • 3Like
  • 2Haha
Hi Blackninja - sorry to resurrect a post that's a few weeks old, but regarding the flavorization system... I would like to leverage this to port over my mod "Rank & File" from CK2 to CK3. However, there are some gaps with the new system that is preventing me from doing so.

1. It doesn't appear to be possible to use custom conditions in the flavorization titles.
2. We can't use custom scopes in flavorization titles - the only ones available (ruler_child and queen_mother) are hardcoded :/.

Is there a chance we could see that functionality restored in the near future? I'd love to be able to port over my mod, and I don't think I'll be able to enjoy CK3 without it.
Correct, for performance reasons the things we check are limited to specific checks instead of going through the entire trigger system as that overhead is too high.

Sorry that your mod is now harder to implement for these flavour names like that, is there a subset of triggers that you specifically need to check as it may be possible for us to add them as other specific check options?

I'm sure you'll be able to find some fun and enjoyment in the rest of the game though.
  • 2Like
Hi blackninja - I appreciate the prompt response :).

A "has_character_flag" condition would be good, since I can hand those out via events. If that's done, I think I could solve the other half of my issues by using custom localization to emulate the "of <realm>" part of the title. I did a similar thing in CK2.

I wrote a bit about my struggles with the new system in this post here: https://forum.paradoxplaza.com/foru...the-minor-title-system.1414940/#post-26854847

I think other modders will have similar challenges, specifically the AGOT team with their "Ser" title.
I'll look at adding a flag entry for a future patch.
  • 1
  • 1Like
  • 1