Need More Info Crash on multple differnet playthoughs

Users who are viewing this thread

Version number
e1.8.0
Branch
Main
Modded/unmodded
Yes, I used mods.
Summary:
crashes alot at a certain point after starting a new campaign or sandbox, here is the callstack error
at TaleWorlds.CampaignSystem.CharacterDevelopment.DefaultSkillLevelingManager.OnHeroHealedWhileWaiting_Patch0(DefaultSkillLevelingManager this, MobileParty mobileParty, Int32 healingAmount)
at TaleWorlds.CampaignSystem.Hero.HealByAmountInternal(PartyBase party, Int32 healingAmount, Boolean addXp)
at TaleWorlds.CampaignSystem.CampaignBehaviors.PartyHealCampaignBehavior.HealHeroes(MobileParty mobileParty, Single& heroesHealingValue)
at TaleWorlds.CampaignSystem.CampaignBehaviors.PartyHealCampaignBehavior.TryHealOrWoundParty(MobileParty mobileParty, Boolean isCheckingForPlayerRelatedParty)
at TaleWorlds.CampaignSystem.CampaignBehaviors.PartyHealCampaignBehavior.OnQuarterDailyPartyTick(MobileParty mobileParty)
at TaleWorlds.CampaignSystem.MbEvent`1.InvokeList(EventHandlerRec`1 list, T t)
at TaleWorlds.CampaignSystem.CampaignEvents.QuarterDailyPartyTick(MobileParty mobileParty)
at TaleWorlds.CampaignSystem.CampaignEventDispatcher.QuarterDailyPartyTick(MobileParty party)
at TaleWorlds.CampaignSystem.CampaignPeriodicEventManager.PeriodicTicker`1.PeriodicTickSome(Double timeUnitsElapsed)
at TaleWorlds.CampaignSystem.CampaignPeriodicEventManager.TickPeriodicEvents()
at TaleWorlds.CampaignSystem.Campaign.Tick()
at TaleWorlds.CampaignSystem.GameState.MapState.OnMapModeTick(Single dt)
at TaleWorlds.CampaignSystem.GameState.MapState.OnTick(Single dt)
at TaleWorlds.Core.GameStateManager.OnTick(Single dt)
at TaleWorlds.Core.Game.OnTick(Single dt)
at TaleWorlds.Core.GameManagerBase.OnTick(Single dt)
at TaleWorlds.MountAndBlade.Module.OnApplicationTick_Patch1(Module this, Single dt)
How to Reproduce:
play for a little while
Have you used cheats and if so which:
not in this playthough but lots of mods, here's my modlist, it relates to native files
Bannerlord.Harmony
BetterExceptionWindow
Bannerlord.ButterLib
Bannerlord.UIExtenderEx
Bannerlord.MBOptionScreen
Native
SandBoxCore
Sandbox
CustomBattle
StoryMode
RBM
DistinguishedService
ServeAsSoldier
PocColor
zzCharacterCreation
zzCharacterCreation_AdditionalSliders
ForgeForMe
TakeBoth
RTSCamera
RTSCamera.CommandSystem
MoreHairColors
CharacterManager
AdonnaysTroopChanger
AutoTrader
DismembermentPlus
BannerColorPersistence
Bastards
BattleSize
BetterHUD
BetterTime
BirthAndDeath
BloodMod
CommandFactionParties
EquipBestItem
Fourberie
Haloarmor
KaosesTweaks
KillBanditsRaiseRelations
KingdomDestruction
LetMeFight
MyLittleWarband
NoLimitBundleUpdated
PartyAIOverhaulCommands
PerfectFireArrows
RaiseYourBannerPlus
RaiseYourTorch
SortedIncome
TroopSort
TrueBattleLoot
TrueController
TrueItemValues
TrueNobleOpinion
TrueRansoms
TrueRelations
TrueTownGold
UsefullCompanions
WorkshopsAdvanced
XorberaxLegacy
YetAnotherCheerMod
zCaptivityEvents
zTBCaptivityEvents
Leveling_rebalance
zCulturedStart
Bannerlord.Diplomacy
Vexillum
hotbutter
SurrenderTweaks
Overhead Shieldwall
CA_WeaponShield
KnockEmDown
ChangingCulture
Spartan
NeekiosDonateFoodToTownsAndCastles
FormationSorter
ProfitableWorkshops
Gladiators.Cataphracts1.6
CA_EagleRising
Multiplayer
Scene Name (if related):
Media (Screenshots & Video):
Computer Specs:
OS: W 10
GPU: GTX 1050
GPU Driver Version:
CPU:
RAM:
Motherboard:
Storage Device (HDD/SSD):
 
ServeAsSoldier exacerbates this bug. There's an unofficial fix mod on Nexus, but the most surefire way is to alter your settings.xml file inside the ServeAsSoldier folder.

Where it reads
<AIRecruitWanders>true</AIRecruitWanders>
change the true to false, and start a new campaign as an old save will already have parties that have already recruited wanderers and continue crashing.
 
ServeAsSoldier exacerbates this bug. There's an unofficial fix mod on Nexus, but the most surefire way is to alter your settings.xml file inside the ServeAsSoldier folder.

Where it reads
<AIRecruitWanders>true</AIRecruitWanders>
change the true to false, and start a new campaign as an old save will already have parties that have already recruited wanderers and continue crashing.
you should do both, kill the XML option, add the patch - on top of that, must backtrack into a previous save before it started happening (a nightmare, I know)
 
This crash did not happen in any vanilla build. Only occurred when mod count (including Native) is greater than 5. Probably a mod crash. If you can reproduce the issue in a new, un-modded and verified campaign please let us know!
Please note that we can’t support any modding-related issues. You can find more information about how to remove modifications here and more information about what we think about issues related to modding here.
Thanks for reporting and sorry for any inconvenience!
 
Back
Top Bottom