Yes, I assumed he didn't want his custom COA, intended for his own dynasty, to pop up on random other dynasties. That seemed implicit in his question.
-
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.
Additional question, same settings as above, what would cause buildings that are supposed to have been built 1000 years earlier, not to be built on game start?
extra_tech_building_start = 10.0
Anything above the highest tech level will ensure that the building is never present at any game start.
Here's the code, I don't have that, it's set to be built early in the province history with b_**** = ca_***** but every game start it isn't built and because of the always = no it's not buildable.
ca_***** = {
desc = ****_desc
potential = {
FROMFROM = { title = b_**** }
}
trigger = { always = no }
gold_cost = 500
build_time = 730
liege_prestige = 5.0
ai_creation_factor = 150
}
So to clarify, you want the building to always be present at start? If a building meets the potential list, it merely means it appears in the building tab, trigger means if it's actually build-able. Remove that always = no condition and insert extra_tech_building_start = 1.0 to the code which should give it a hundred percent chance of spawning in a province in which the potential matches as long as you put a tech condition into the trigger.
Yeah but that also makes the building rebuildable if it's ever destroyed, since it's intended to be a unique building that's not what I'd want. Thanks though.
For that, you should be able to set the potential to "has_building = [BuildingID]", that was it's potential is only met (and it only appears) when the Building already exists. If it's destroyed, there should be no way to rebuild it.
If I make a new Hersey, do I need to do anything 'special' to get it to form randomly, or will it just be automatically added to the list of 'potential heresies' whenever the game checks for one occurring?
Nope, as long as you set the "parent" religion (to make it a heresy in the first place) it'll show up when your Chaplain researches technology or MA drops too low.
- 1
That's an interesting method I'll use it, thank you, though sadly, didn't solve the unbuilt issue.
How about an on_action for on_startup? Fire an event, scope to the intended Province and use add_building; then add an invisible Modifier to make sure you don't get it re-added every time you load a game?
Use on_chronicle_start instead, in only fires when the game 1st starts, not every load.
But events on_chronicle_start only fire for the olayer though. He'd need to take that into account when scripting the event.
Well to be entirely clear, I know how to setup the events and on actions, I was hoping to avoid using events to place them by using the normal method of province history. But when I've tried that the buildings weren't built properly and none of the error checking methods available(the error logs and Validator) have come up with anything, so I posted here to see if anyone knows of more reasons why the history would be ignored like that, which seems no one does.
Last edited:
If I want to change a character's name via event, what piece of code do I use? Is it name = within a character_event or something else?
So i have tried to add a opinion modifier to a event option. the end result should be members of a faction getting a opinion bonus with vassals when a civil war begins it does not seem to be working can someone help
Here is the relevant code from the file plot_events
option = {
name = "EVTOPTB8005"
opinion = {
modifier = opinion_rebellove
who = any_faction_backer
months = 12
}
ai_chanc.....
Here is the relevant code from opinion modifiers
opinion_rebellove = {
vassal_opinion = 35
}
Here is the relevant code from the file plot_events
option = {
name = "EVTOPTB8005"
opinion = {
modifier = opinion_rebellove
who = any_faction_backer
months = 12
}
ai_chanc.....
Here is the relevant code from opinion modifiers
opinion_rebellove = {
vassal_opinion = 35
}
That is not how scopes work, the RHS of a who = for opinion modifiers needs to be ROOT, FROM, PREV or an event target. So what you want to do is something like:
Code:
any_plot_backer = {
ROOT = {
opinion = {
modifier = opinion_rebellove
who = PREV
months = 12
}
}
}Your modifier should be:
Code:
opinion_rebellove = {
opinion = 35
}
born_in_the_purple is a hard coded trait, referenced in the executable, and defined in 02_traits.txt.
Code:
any_plot_backer = {
reverse_opinion = {
who = ROOT
...