Project Balance
- Thread starter Meneth
- Start date
-
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.
Perhaps VIET, but as we do characters history files in SWMH too, might rather be our job to do. Answer is here
This mod destroys my saves, and also the duel event (5556000) doesn't start properly. Is there any way to fix these?
It would only work if you're only running VIET events, actually. Running VIET traits or immersion with old saves that didn't use them would cause issues, particularly for the latter.
The old save was with VIET Traits so that's not a problem, though now when I load that game up my emperor is a Sayyid because ???.
So it's never going to be possible to play PB with old saves? And why doesn't the battlefield duel event chain work? It will start in battle, but after clicking "Charge!" it doesn't continue.
So it's never going to be possible to play PB with old saves? And why doesn't the battlefield duel event chain work? It will start in battle, but after clicking "Charge!" it doesn't continue.
How old was that save with VIET traits? If it was old enough it might be causing some wonkiness with old saves. Additionally if you started playing with any other mods that add in new traits afterwards it might mess up the traits in your old saves.
.png){kind=avatar}
The New Duel Engine, responsible for the (normally) cool battlefield duels, doesn't appear to be working correctly 80% or more of the time since it was last updated. Since NDE (jordarkelf) is yet to fix this issue or comment on it as far as I know, in theory we could try to revert the directly-integrated version of NDE to its state prior to its last integrated release. The ease of doing that may be quite difficult or quite easy, all depending. We'd have to try. I don't know if we're ready for that drastic of an action, but it has been a long time without a fix now.
EDIT: And I really miss advancing my combat skills on the battlefield, a new feature of PB (and then NDE itself) that came out just slightly before the duel engine stopped working! Which reminds me, I need to turn-up the odds of combat XP advancements in battle for the next release (will need to coordinate with VIET to update their on_actions as well, since they override ours in HIP), as the random chance factor used for the past few months has apparently been way too conservative.
Last edited:
Someone in an AAR I'm reading has been having it work fine as of a few days ago, which is weird as heck.
Anyway, the VIET traits save is fairly old, I can't recall how much so but somewhere in the "months" category at least. It's possible the traits added by SoA messed with the ones in the save, like that patch a while back that fucked up everybody's traits because Siege Leader was put in the wrong place.
Anyway, the VIET traits save is fairly old, I can't recall how much so but somewhere in the "months" category at least. It's possible the traits added by SoA messed with the ones in the save, like that patch a while back that fucked up everybody's traits because Siege Leader was put in the wrong place.
Like a lot of things in the PB version of VIET we take the PB code as the base (rather than the vanilla code like in vanilla VIET) and then add in the VIET stuff, so you won't have to worry about the on_actions.
We have plans to future-proof at least PB (and probably get all other HIP mods which touch traits at all to adopt the same standard too) from this crap. We will be carefully allocating a number of "placeholder" traits at the beginning and end of various mods' related trait files, the largest reserved allocation going into a file named such that it will always reasonably load right after vanilla traits but before any mods' traits. This will give us a bunch of "trait ID space" buffer against vanilla updates. As vanilla fills the space with new traits (similar process for save-compatible mods adding/removing traits), we will remove the corresponding number of placeholders from the beginning of that buffer zone, allowing all of our extended traits to continue to be save-compatible despite vanilla trait additions, across different mod combos.
However, to put the system in place, trait compatibility has to be broken at some point, and since PB itself hasn't broken save compatibility in a long time, we don't intend to break it until we absolutely have to: when Rajas of India is released. At that time, we'll take the opportunity to future-proof the system.
Do you guys just manually check whether we've changed on_actions / other shared stuff right before a release and then patch them into (or patch your stuff on top of it, however you'd like to look at it)? If so, with what kind of timeline do you check/merge? It seems like we should have a more formal hand-off for those troublesome shared files so that we're always sure changes are in sync before a new HIP release (else, we may claim to have added/tweaked a feature that will not function at all if it was missed). Without yet again besieging you with how GitHub could solve this naturally-- I accept that's not going to happen soon, I guess this is one of those things with which a private HIP forum and a release merge checklist would assist us (much more generally for HIP than the on_actions).
I don't know if this is a PB problem or a problem at all (I only play PB.) but I need some help. I was changing characters via console ('play' xxx) during my save and I noticed some of my characters don't have the option to Feast, Hunt or Fair any more. Like the option is completely removed from the menu. Anyone know about this?
Nevermind, found solution. Characters were flagged as 'do_not_disturb' for whatever reason.
Nevermind, found solution. Characters were flagged as 'do_not_disturb' for whatever reason.
Last edited:
EDIT:
< essay obsoleted by you figuring out it was the do_not_disturb flag, followed by ... >
... but I'd damn well better get one soon [a clue]. You truly play PB alone? So you do a HIP install and say yes to Project Balance but no to everything else? Or do you download the PB beta from GitHub? In either case, please check for the file "ProjectBalance/PB ChangeLog.txt" relative to your mod folder, and check the version number at the top (should be 3.4.x or so). Let us know what that is.
Hint: It's probably the New Duel Engine. That's the only non-Vanilla code in pure PB or PB+SWMH that sets do_not_disturb.
Last edited:
For fart's sake, I composed a frickin' essay in response to this.
I still think this is a bug. I've heard more than a few otherwise unrelated reports of behavior that can only really be attributed to the do_not_disturb flag being set very often when it should not be and at least one confirmed case of some event code somewhere routinely setting this flag and never clearing it, which would presumably eventually lock all characters out of those decisions (and a lot of events). I guess I just need you to answer the questions at the bottom of the post below this one that I'm about to edit, and that will be another data point. I already have a suspect in mind, so if I can just confirm that you're only playing PB...
EDIT2: Also, are you using PB VIET Events by chance? I would like to rule them out, otherwise I'd have to confirm they don't set the flag anywhere (after all, it would be very useful to their event chains, so I could see its appeal).
Last edited:
Meneth, still encountering a bug from before the merge into HIP: vassals in a faction who are discouraged from factionalism receive the opinion modifier...but don't actually leave the faction.
With the autonomy faction, that's intended. Instead they always vote in your favor, which is a lot better than them leaving entirely.
Does it happen with any other faction?