• 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.

CK3 Dev Diary #37 - Making Mods

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!

common_folder.png

[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!

lunatic_override.png

[screenshot of a file overriding the lunatic trait]

lunatic_override_in_game.png

[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!

custom_alert.png

[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.

murder_button.PNG

murder_confirmation.PNG

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

murder_script.PNG

murder_gui.PNG

[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
Reactions:
Hi, I'm currently working on a mod focusing on the British Isles for CKII and I was wondering how easy it would be to port a map to CKIII?
Would it require a lot of work and an entirely new set of images?
Also, I had planned to rework the holdings to fit more of a manorial system (Since the map is split into a tonne of baronies it wouldn't make sense for each one to have a castle) Do you have any idea how moddable the holdings would be? Could we perhaps create entirely new holding types?
 
  • 1Like
Reactions:
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.
View attachment 610259
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 :)

View attachment 610263
Can it be changed to a rectangle or must it be a square?
 
Can it be changed to a rectangle or must it be a square?

He showed a rectangle, so that should be fine. The square just gives you more chance to blend along 2 axes equally rather than mostly just one axis. If you were to make the normal skin tones on a rectangle, you'd lose out on a lot of the possibilities. Of course, if you're just using fake skin tones or you only want specific ones, a rectangle may work better for you.

I think the bigger question is... can you use more than one palette? For a fantasy mod, for example, you might want orcs to have a brownish set of skin tones, trolls to have a blue to green range of skin tones, elves to have a normal "pinkish" to blue or purple skin tones, etc. I suppose you could put these on the same palette and since the child will be somewhere between the skin tones of the parents, you could just have each race set in the right part and go from there. But it might be easier to work with and adjust the skin tones if you could do so with multiple palettes.
 
  • 3
  • 2Like
Reactions:
IS that a Mitch Hedberg quote? I applaud your good taste sir :p

It is indeed, my good man! Thank you! I was hoping someone would recognize it for what it was. :)
 
He showed a rectangle, so that should be fine. The square just gives you more chance to blend along 2 axes equally rather than mostly just one axis. If you were to make the normal skin tones on a rectangle, you'd lose out on a lot of the possibilities. Of course, if you're just using fake skin tones or you only want specific ones, a rectangle may work better for you.

I think the bigger question is... can you use more than one palette? For a fantasy mod, for example, you might want orcs to have a brownish set of skin tones, trolls to have a blue to green range of skin tones, elves to have a normal "pinkish" to blue or purple skin tones, etc. I suppose you could put these on the same palette and since the child will be somewhere between the skin tones of the parents, you could just have each race set in the right part and go from there. But it might be easier to work with and adjust the skin tones if you could do so with multiple palettes.
Even if you can't have multiple pallets (because the DNA system can only use one?) you could hijack the 125 shades of black and white by flipping the main axis of the gradient to add some colours. Would need to rework every race DNA color in game to ocupy a new area on the gradient map, and if a greenish and a pinkie has a child it would be human color. Someone more creative might try to jam in more color dimensions.
Alt.png
 
  • 4Like
Reactions:
Even if you can't have multiple pallets (because the DNA system can only use one?) you could hijack the 125 shades of black and white by flipping the main axis of the gradient to add some colours. Would need to rework every race DNA color in game to ocupy a new area on the gradient map, and if a greenish and a pinkie has a child it would be human color. Someone more creative might try to jam in more color dimensions.
View attachment 610349
Potentially a 3D colour space?
 
Potentially a 3D colour space?
Likely not full 3D color space. More, how to flatten the 3D color space to 128x128 2D and have the DNA system still produce offspring with sensible colors (choose any two points as parents and every point on a straight line between those two points should make sense as a child). Another possible option is decals if they are available, assigning race as a trait and the trait applies a decal over the character skin, slightly similar as how ck2 handles fantasy races modded in.
 
  • 1
Reactions:
In modding CK2, if you wanted to 'unlock' certain events or chains of events, it was generally necessary to edit all of the events to change the conditions checked in their triggers. For example, if you wanted to enable Seduction events and decisions for a character that doesn't have the Seduction focus, you'd have to search through the script and decision files for instances of "has_focus = focus_seduction" and make many changes.

Has there been any restructuring in how such prerequisites are implemented in CK3 that could streamline that and allow accomplishing the same with fewer elements edited? For the above example as an illustration, if the game applied a character flag on choosing a focus, and the vanilla events checked for the presence of that flag instead of the presence of the focus, then the modder would have the freedom to add that flag in other ways to enable the Seduction content.

I'm thinking specifically of what would be involved in modding in new lifestyles, focuses, and perk trees. One might wish to add content like this, but re-use events from pre-existing ones rather than needing to create entirely new sets of events.
 
I'm saying it might be possible but TBH I'm not completely sure so I can't make any guarantees. We haven't tried to use the system in that way.

Would implementing static character models be significantly easier then, such as swapping out assets for still-images of dragons via Google search?

Perhaps the modder can create multiple dragon traits with each trait devoted to a unique static image that substitutes out the in-game model for the image. I'd have to play around with where the best place to store each image would be though.
 
Last edited:
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.
Is the gender of the child still determined at birth? If not, can we get/set the gender of an unborn child? Otherwise, can we do so before the birth is announced to the player?

I imagine certain total conversion mods might find this very useful.
 
Why won't the Dev's answer whether baronies will be able to be modded in? If we can't remove the restriction to play baronies as they are, we'll just have to bump the titles down by one so baronies are just counties with only the capital barony attatched, making the base baron level title obsolete, or possibly having it as a sort of off-world title for knights in your realm.
 
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?
I realize I'm answering a week-old question (which already has multiple simple, if solid, answers, including one from a Paradox programmer), but there are good reasons (certification requirements, mostly) for a fix made late in development to be put into an early patch and not in version 1.0, and if nothing else I want to link to a guy who knows what he's talking about. Also, I am of the opinion that more details are always better, as long as they're presented clearly.

To summarize: Games need to go through a process called certification before they can be released on any platform. The exact process varies a lot by platform, but it's invariably a significant expense, so you don't want to go through it twice. This means that A. you don't submit games for certification before you're confident they'll pass, and B. you don't change games after submitting them for certification except to fix bugs that will make the game fail certification.
Patches also need to be certified, but the process is much easier (and cheaper) than certifying a whole game. If you find a non-cert-breaking bug after the game has been submitted for certification, you fix it in the first patch, because that's cheaper and easier. Then, if everything goes according to plan, you release the patch on day 1 so nobody ever notices the broken aspects of 1.0.


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.
View attachment 610259
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 :)

View attachment 610263
A clever artist should be able to find a better way to arrange the colors, of course. My first point of reference is the paint.net color wheel thingy:
colorswindow.png
Here, a red/blue hybrid child would be magenta-ish.

It should go without saying that having technicolor people and ordinary skin tones on the same palette would be...tricky.


Why won't the Dev's answer whether baronies will be able to be modded in? If we can't remove the restriction to play baronies as they are, we'll just have to bump the titles down by one so baronies are just counties with only the capital barony attatched, making the base baron level title obsolete, or possibly having it as a sort of off-world title for knights in your realm.
My intuition says that they can't be modded like that, because the levels of title which are playable (and hence are fully engaged in the world around them) is presumably central to how the code is structured. (And, moreover, that such a hypothetical mod would probably cause serious performance issues, because there are squillions of baron-level nobles.) But I can't think of any way to reply to this kind of question well from Paradox's perspective, especially if providing more than a simple "No" requires understanding technical issues that the people running these threads don't understand (which they probably do, because again, this is presumably central to how the code is structured).

TL;DR: It's a surprisingly complicated issue, but the overall answer is probably no.
 
  • 2
  • 1Like
Reactions:
I realize I'm answering a week-old question (which already has multiple simple, if solid, answers, including one from a Paradox programmer), but there are good reasons (certification requirements, mostly) for a fix made late in development to be put into an early patch and not in version 1.0, and if nothing else I want to link to a guy who knows what he's talking about. Also, I am of the opinion that more details are always better, as long as they're presented clearly.

To summarize: Games need to go through a process called certification before they can be released on any platform. The exact process varies a lot by platform, but it's invariably a significant expense, so you don't want to go through it twice. This means that A. you don't submit games for certification before you're confident they'll pass, and B. you don't change games after submitting them for certification except to fix bugs that will make the game fail certification.
Patches also need to be certified, but the process is much easier (and cheaper) than certifying a whole game. If you find a non-cert-breaking bug after the game has been submitted for certification, you fix it in the first patch, because that's cheaper and easier. Then, if everything goes according to plan, you release the patch on day 1 so nobody ever notices the broken aspects of 1.0.

I may be wrong here, because this is not my area of expertise, but I thought the certification requirements were only for consoles? I.e. you have to get certified by Nintendo for Nintendo, by Microsoft for Xbox, and so on?
 
Why won't the Dev's answer whether baronies will be able to be modded in? If we can't remove the restriction to play baronies as they are, we'll just have to bump the titles down by one so baronies are just counties with only the capital barony attatched, making the base baron level title obsolete, or possibly having it as a sort of off-world title for knights in your realm.
You can almost certainly mod it in so that "counts" run what would otherwise be baronies, and everyone moves down one - the problem comes that unless you do something about it, your four "playable" tiers now run out at what would normally be king tier. This may or may not be solvable by adding more tiers - or the number of tiers may be fixed.

There is a problem as well that since barons have severely abbreviated courts, you've now taken the number of potential comital courts and multiplies it by 5 or so - increasing the number of characters that will be around.

Then not all baronies are feudal holdings.
"Single holding counties" are often relatively poor, and without the tax income from the barons it would be quite hard to get any momentum going.
It also brings back the problem from CK2 of "control X kingdom entirely" becoming a chore once again as you have to hunt down far, far more title holders in the process.
 
  • 2
  • 1
Reactions:
I may be wrong here, because this is not my area of expertise, but I thought the certification requirements were only for consoles? I.e. you have to get certified by Nintendo for Nintendo, by Microsoft for Xbox, and so on?
I'm pretty sure, though not 100%, that Steam also has some certification requirements. Not as stringent as the consoles', of course, but still extant.

Maybe we should look for someone with firsthand knowledge instead of guessing at each other.
 
  • 1
Reactions:
I'm pretty sure, though not 100%, that Steam also has some certification requirements. Not as stringent as the consoles', of course, but still extant.

Maybe we should look for someone with firsthand knowledge instead of guessing at each other.

I think you might be right.

I looked and I found, well, Steam themselves. :)
 
  • 1
Reactions:
  • 1
Reactions:
Oh. Right. Steam would need to put their requirements somewhere public, because everyone's making Steam games.

Yup! Every guy and gal who knows a little code is hoping to become the Angry Birds of Steam. :)