Jump to content
  • 0

"wetriggerscript" script error popups on Solstheim


Question

Posted

This is a script issue that's bugging me on my STEP install, though it could likely not have anything to do with STEP itself, I've had no luck Googling answers to this one.

 

The popup below randomly appear as I explore Solstheim. Its a Box that I can press OK on and continue, it doesnt cause always cause CTDs, though it did on a couple occasions, but its slightly irritating either way. I have a substantial load order, mostly STEP mods, but they're all carefully BOSS'd and all. Googling the error says this can be caused by duplicate Skyrim.esm entries in plugins.txt, but I checked my plugins.txt (the one Mod Organizer generates), and the core esm is only there once (though there are also the unofficial patches ofc). The only change I've done to any of the ESMs is cleaning the Update, and the Official DLCs as recommanded.

 

Just want to know if this rings a bell to anybody :)

 

WETriggerScript < (********)>]WARNING: getMyHoldFactionControllerMarker() myHoldOwner propertyexpected to be 1 or 2, instead have:-1

Additional info; the source for that script is in scripts/source and shows the script has to do with creating context-appropriate random events for the player. The portion of the script generating the errors seems to be the following... and given neither Imperials or Stormcloaks are on Solstheim to my knowledge, well, I'm not sure this should be triggering at all...

ObjectReference Function getMyHoldFactionControllerMarker()

{Returns the xmarker associated with the Civil War faction currently controlling myHold.}

 

if myHoldOwner == CWs.iImperials

  if myHoldIsContested

   return WEHoldImperialContestedRef

  Else

   return WEHoldImperialRef

  EndIf

 

elseif myHoldOwner == CWs.iSons

  if myHoldIsContested

   return WEHoldSonsContestedRef

  Else

   return WEHoldSonsRef

  EndIf

 

Else

  debug.MessageBox(self + "WARNING: getMyHoldFactionControllerMarker() myHoldOwner property expected to be 1 or 2, instead have:" + myHoldOwner)

;   debug.trace(self + "WARNING: getMyHoldFactionControllerMarker() myHoldOwner property expected to be 1 or 2, instead have:" + myHoldOwner, 2)

  return None

EndIf

5 answers to this question

Recommended Posts

  • 0
Posted

Looks like it has to with Wet & Cold since that makes the PC and NPCs have wet and cold effects on them. You can turn the wet or cold effects off in the MCM menu and see if this is still a problem. I think you can also deactivate the mod from the MCM menu, but don't just uninstall it on a current save.

  • 0
Posted

Thanks, sadly its a no go, still happening for now.

 

I also tried disabling all mods with a Dragonborn component that I could think of, and using clean inis, new char, still the same.

 

This is a resilient little cockroach.

 

This is still happening with no mods AT ALL, just the official DLCs, not even UPs, clean inis, new game...

Ugh, BUT it doesnt happen if I launch that clean game through the normal launcher instead of ModOrganizer. I guess the problem has to be there, or SKSE.

 

Edit 3: Ok at this point I've realized that it IS a mod causing this, but that merely unchecking the ESP of whatever mod it is does not suffice. I need to uncheck the mod completely, should have thought of that. Now it should be just a matter of time...

  • 0
Posted

And the winner is "Atlas Map Markers with Dragonborn, Dawnguard and Blackreach addons". :p

 

I unchecked its ESPs like 3 hours a go and give it a pass because the problem kept occuring. Just finally noticed that it tries to modify ... WETriggerScript.pex :p

 

Thanks for the help.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.