At the time of writing this i realized i possibly  made a mistake during my PAHE 8.0.2 testing.

 

My PAHE Testrun in 8.0.2 version and 8.0.1 concentrated conform or deny naked bandit bug is fixed.

 

To those who dont know: naked bandit bug happens af you capture a bandit, something happen in skyrim spawn system. Skyrim use same "base look" of characters that not uniqes. So one can encaounter multiple times same looking enemys. Problem is after capturing a respawning enemy all the similar loking spawning ones lose the chest armor pice.

This is the naked bandit bug, one known work around radicly incrase number of possible looks using pretier bandits or other mods that incrase diversity of bandit population help a lot.

 

PAHE 8.0.2 fix this bug finaly. At least at this time point i not found way to break the fix if not use any "dont use" dialoge option( " strip now and set naked as default" dialoge option) during talking slaves.

 

During the testing i focused only this aspect of the mod, ignored cheking most of the other functions. 

This alone not cause problems right?

 

Then i started tetesting Diary Of Mine (DOM) 2.0.1 version. This mod a extensation for PAHE, a fantastic one to be honest. That fills lot of life and personality the slaves.

Important point is this one based on PAHE.

 

I found a bug: after capturing a slave if you restart PAHE mod using mcm option, nasty i mean realy realy nasty error spam happen in papyrus log.

This one the starting message:

 

ERROR: Cannot divide by zero
stack:
    [PAHBootStrap0_7_3 (0800CF32)].pahbootstrapscript.RestartQuests() - "PAHBootstrapScript.psc" Line ?
    [PAHBootStrap0_7_3 (0800CF32)].pahbootstrapscript.Boot() - "PAHBootstrapScript.psc" Line ?
    [PAHConfig (0E009157)].pah_mcm.OnOptionSelect() - "PAH_MCM.psc" Line ?
    [PAHConfig (0E009157)].pah_mcm.SelectOption() - "SKI_ConfigBase.psc" Line ?
    [SKI_ConfigManagerInstance (0A000802)].SKI_ConfigManager.OnOptionSelect() - "SKI_ConfigManager.psc" Line ? 

 

That fallowed by someting like this:

ERROR: Cannot access an element of a None array
stack:
    [PAH (0801FAEF)].pahcore.updateSlaveArray() - "PAHCore.psc" Line ?
    [PAH (0801FAEF)].pahcore.AddSlave() - "PAHCore.psc" Line ?
    [PAHBootStrap0_7_3 (0800CF32)].pahbootstrapscript.RestartQuests() - "PAHBootstrapScript.psc" Line ?
    [PAHBootStrap0_7_3 (0800CF32)].pahbootstrapscript.Boot() - "PAHBootstrapScript.psc" Line ?
    [PAHConfig (0E009157)].pah_mcm.OnOptionSelect() - "PAH_MCM.psc" Line ?
    [PAHConfig (0E009157)].pah_mcm.SelectOption() - "SKI_ConfigBase.psc" Line ?
    [SKI_ConfigManagerInstance (0A000802)].SKI_ConfigManager.OnOptionSelect() - "SKI_ConfigManager.psc" Line ? 

 

i dont know how bead this for save game or game stability i not a programer. i know only this: 

unmodedd original state skyrim one hour play estiamted generate 80 - 130 kByte papyrus log with lowest loging settings.

This one with 10 minute play generate 210-240 kByte paparus log with modded setup and USSEP fixes lot of bugs.

 

Moving to the point:

i thinking and realized i not tested this function i mean PAHE restart function with the base mod, in bigger scale i not tested many of the functions of PAHE.

Only few very basic ones.

 

as no programer and dont know what happening inside behind the scanes i dont know if a bug inside pahe effect dom or not? maybe this case this is the happening?

 

So i decided at the minimum i can do. I run same test run using same mod everiment that used in DOM 2.0.2 to PAHE 8.0.2 to see what is the end product.

 

Testrun very basic:

load a save game tha clean,

setup mcm menu

capture one slave, tie it up

save game

restart pahe

save game

kill slave

restart pahe

quit and see the log

 

and screem with full of pain...

with one slave restarting pahe i get this message:

 

ERROR: Cannot divide by zero
stack:
    [PAHBootStrap0_7_3 (0800CF32)].pahbootstrapscript.RestartQuests() - "PAHBootstrapScript.psc" Line ?
    [PAHBootStrap0_7_3 (0800CF32)].pahbootstrapscript.Boot() - "PAHBootstrapScript.psc" Line ?
    [PAHConfig (0D009157)].pah_mcm.OnOptionSelect() - "PAH_MCM.psc" Line ?
    [PAHConfig (0D009157)].pah_mcm.SelectOption() - "SKI_ConfigBase.psc" Line ?
    [SKI_ConfigManagerInstance (09000802)].SKI_ConfigManager.OnOptionSelect() - "SKI_ConfigManager.psc" Line ? 

 

by the way no error spam! like DOM case.

 

after killing the slave i get error messages it expected and normal.

After that i see the canot divaded by zero line agin.

 

SO my suspition turned out be correct....

Source of problem or at least the first error message exist in PAHE as exist in DOM.

 

To add some chery to top of cake:

i discovered this bug by accident.

As playtesting DOM and trying use new function the thug slaves. this slave need to be very broken... i mean realy realy broken basicly in love to slave master. ( yes this can be done in DOM! )

to reach this point some cases takes 1 hour of play time, i trained one slave this point and tryed turn thug. This one tiggered some strange error i canot talk to thug, trying fixing the bug.

 

And as trying fixing one usual stepp is : Restart pahe.

after i failed recover my thug from the bugged state moved to check papyrus logs maybe i find some clue what whent wrong. and i see one giant error cunamy.... this lead discover pahe-dom restart bug discovery.

 

Quote

Conclusion time!

or if you wish call it lesson learned:

 

1 - if you testing some complex mod like PAHE that very deep and complex or any mod new version. TEST evrything out. one thing change may effect other things that not expected to changed.

 

2 - if a mod uses another mod very heavy, first test all the base mod and best if can build up reference base or base lines. how that thing works alone. 

in my test case DOM change many things how work inside PAHE. so to me important to get a base line.

 

3-if something strange happen a mod that based on other mod, if you can try to reproduce that bug in the base mod. and check maybe base mod fault not the mod that uses the base mod.

 

4 - At this time point PAHE not like if you kill your slaves or sell in fellglow slave camp, i dont knwo that error cunamy that this generate how sirus effect on save files or other slaves.

i think better to avoid this things (killing slaves, selling slave in fellglow slave camp). At least in PAHE 8.0.2 version.

 

Here is the logs for those who intrested in it, or wish to  have nightmares...

 

Run 1:

DOM 2-0-2 testrun using alternate start to reproduce the restart bug

 

Run 2:

DOM 2-0-2 estrun with required mods only, no sos no cbbe or other fancy mods in use, this one filled with loot of error messages. reason for this simple: using clean save file as base 

ignore the first errors until first save

 

Run 3:

this one done exact same mod setup as Run 2 only diference DOM 2-0-2 not installed only pahe. same steps done to reproduce bug based on same save file as run 2 case

 

please be avare the log file sizes! especialy run 2 and 3 case!

 

This all for now, i hope its helpfull useful for others!

 

 

Run 1 - Papyrus.0.log

Run 2 -Papyrus.0.log

Run 3 -PAHE ONLY-Papyrus.0.log