Suggestions for Improved Moddability

[ngppgn]

Let Root point to the caharavter being viewed for locaalisations in items in domestic_dynastic.gui. You can create new icon_types and text_boxes there but the inability to use relative localisation hadicaps what couls be do in interface modding.

For example, it would allow to display variables as custom stats.

 

[Zarathustra_the]

What do you mean by that? @Zarathustra_the Which wiki? You meant ckiiwiki.com? This command is documented however example is given only for relative amount of troops.

Is it already in the game?

Also I noticed vanille uses trigger like this:
2.6.2

troops = {
  who  = troops
  value = 9
  enemy = yes
}

Is it a bug or it really checks if there are 9 of people ?
Anybody checked it?

I mean on the wiki list for things to add. Also which trigger uses that command?

 

[Zarathustra_the]

Let Root point to the caharavter being viewed for locaalisations in items in domestic_dynastic.gui. You can create new icon_types and text_boxes there but the inability to use relative localisation hadicaps what couls be do in interface modding.

For example, it would allow to display variables as custom stats.

We can almost do this already, using the get_variable locale function. The issue is that the localisation will not update in real time, so even if the value is stored in a modifier or trait, or on a custom ui element, it doesn't update properly.

 

[ngppgn]

We can almost do this already, using the get_variable locale function. The issue is that the localisation will not update in real time, so even if the value is stored in a modifier or trait, or on a custom ui element, it doesn't update properly.

Yeah, but we need the traits of modifiers for those. Being able to put them in an icon placed elsewhere would be more appropriate.

While we are on it, what is the problem exactly. I mean, is it like they only update omce a year or something? May be would be worth reporting to Divine...

 

[blackninja9939]

Added:

• In trigger_switch allow an else = { effect } option which fires if one does not meet any of the other conditions of the on_trigger

 

[Agnoz]

It would be nice to see more moddability when it comes to twins. An impregnate_with_twins command, some way to scope a character's twin, some way to actually define characters as being twins...

 

[ngppgn]

Currently, the province embellishment (the on map sprites tied to province and depopulation) seem to be hardcoded to these modifier tags. It would be really really handy to be able to tie custom embellishments to custom major provinces modifiers.

 

[Zarathustra_the]

is there any way we could get the character_modifier versions of local_movement_speed fixed? Currently the modifier appears on the character, but it does nothing. Alternatively, could we get some way to add an army speed modifier to a character, and perhaps damage, morale and defense modfiers as character modifiers not command modifiers? This would let us have events to boost an armies performance, rather than having to mess around with traits.

 

[ngppgn]

is there any way we could get the character_modifier versions of local_movement_speed fixed? Currently the modifier appears on the character, but it does nothing. Alternatively, could we get some way to add an army speed modifier to a character, and perhaps damage, morale and defense modfiers as character modifiers not command modifiers? This would let us have events to boost an armies performance, rather than having to mess around with traits.

Don't traits like organiser have something like this already?

Couple more suggestion:
-make same_realm condition useable between provinces
-allow trade_route =yes, to return true if a province is in any trade route.

 

[Zarathustra_the]

Don't traits like organiser have something like this already?

Couple more suggestion:
-make same_realm condition useable between provinces
-allow trade_route =yes, to return true if a province is in any trade route.

Traits do not stack @ngppgn and I want effects that can stack and interact with each other, much like attribute modifiers from events.

 

[ngppgn]

Traits do not stack @ngppgn and I want effects that can stack and interact with each other, much like attribute modifiers from events.

I see. Then allowing command_modifier in character modifiers would be optimal, right?

 

[Zarathustra_the]

I see. Then allowing command_modifier in character modifiers would be optimal, right?

That was looked at before by @Divine but was found to be too onerous a check. that said gods willing that would be the dream

 

[ngppgn]

An on_settlement_destroyed would be handy for some purposes, specially for economically-minded mod. ROOT could be the province the settlement was in, and FROM the last holder.

 

[blackninja9939]

Added:

• Allow <religion>_opinion to be dynamic and not just work for vanilla religions like christian_opinion or muslim_opinion

 

[theStormWeaver]

Added:

• Allow <religion>_opinion to be dynamic and not just work for vanilla religions like christian_opinion or muslim_opinion

Doesn't it though... ?

 

[blackninja9939]

Doesn't it though... ?

Nope, it only works for vanilla religions from my testing with it. Says same thing about it on the wiki on the modifiers page

 

[Romulien]

Nope, it only works for vanilla religions from my testing with it. Says same thing about it on the wiki on the modifiers page

+1, what can be confusing is that the tolerates_<religion_group> of traits (which also has an impact on opinion) is dynamic.

 

[theStormWeaver]

+1, what can be confusing is that the tolerates_<religion_group> of traits (which also has an impact on opinion) is dynamic.

That must be what I was thinking of.

 

[Zarathustra_the]

@Divine could we perchance get a any_ and a random_ scope for marked persons of interest? It would be very useful to be able to use the person of interest marking as a means to affect chosen characters with script effects.

 

[ngppgn]

A minor addition in terms of syntactical sugar to allow more succint code:

Let random_(scope) = limit = { (conditions) count = n } (effects) }

be a shorthand for n copies of random_(scope) = limit = { (conditions) } (effects) }