Welcome to the AFK Mods bug tracker. In order to report an issue, please select a project from the drop down menu below. Select “Open New Issue” and fill out the form with as many details as possible.

An account will be required to submit an issue, so if you need one and are unable to register, please contact us via the forums at https://afkmods.iguanadons.net/

Issue Data
Status: Closed
Issue Type: Bug Report
Project: Unofficial Skyrim Legendary Edition Patch
Component: Skyrim LE: Vanilla
Category: Quests
Assigned To: Nobody
Platform: All
Severity: Very Low
Votes: 0
Watching: N/A
Opened By simtam on Dec 5, 2017 9:51 am
Last Edited By BlackPete on Apr 6, 2018 7:21 pm
Closed By Arthmoor on Apr 6, 2018 9:45 pm
Resolution: Invalid
Comment: Issue does not occur when tested.

Issue #23284: Rikke/Galmar won't let me report in, CW alias FieldCO points to enemy lieutenant!

The Rikke/Galmar bug reports used to be pinned on #2325 ... But #2325 is only responsible for some of those issues. (Even if #2325 affects not only CWMission04 but also the other holds, like Hjaalmarch). For others, the symptom is that alias FieldCO on quest CW switches to field commander of the enemy side. So, if you look aliases in the console with "sqv cw", it holds Rikke instead of Galmar for Stormcloak playthrough, and Galmar when it should be Rikke for players aligned with the Legion.

It might be related to what inmundano says about CWMissionGeneratorTriggerScript
that this scripts triggers for the enemy camps.

If that's right, that would mean that it's a glitch that will be resolved after traveling far away and approaching the camp again, maybe from a different direction, or with/without fast travel. However, I wasn't able to observe the alias FieldCO change when approaching an enemy military camp - perhaps it was my observation that was broken on this occasion.

Related Issues: 2325  


4 comment(s) [Closed]
simtam said:
After some more testing, indeed the FieldCO alias is set to enemy field commander when approaching enemy camp. Provided that the enemy camp is enabled, and that this bug won't happen the other way round...

Now, inmundano wrote that it is a Bethesda bug that only affects CWO, but I guess he meant the part involving generating missions. Because this issue is possible to reproduce it in vanilla, for example: when walking from Pale camp Imperials in the SW direction towards the Hjaalmarch Stormcloak camp, the FieldCO changed to Galmar reference midway through, and didn't revert to Rikke after going back to the imperial Pale camp. That happened after loading a game saved in the Pale Imperial camp. And with default uGridsToLoad value. Looking at the UESP map grid cell, these two camps are at cell distance (+2,+4). So I guess you will be able to reproduce it that way.

One way to restrict this would be to change CWMissionGeneratorTriggerScript so that it will not apply to enemy field commanders.

- if myLocation.HasKeyword(CWCampImperial)
+ if myLocation.HasKeyword(CWCampImperial) && CW.playerAllegiance == 1

- ElseIf myLocation.HasKeyword(CWCampSons)
+ ElseIf myLocation.HasKeyword(CWCampSons) && CW.playerAllegiance == 2

The other part of that script - generating missions - might be indeed a non-issue in vanilla Skyrim.

Arthmoor said:
What your suggested possible fix does is logically no different from what the code is already doing in there. As far as I can tell, that guy on Reddit is entirely correct that it would only affect CWO.

Comment #2 Apr 5, 2018 11:20 pm  Edited by BlackPete on Apr 5, 2018 11:38 pm
simtam said:
If you tested the Pale Imperial - Hjaalmarch Stormcloak camp route, there and back again, watching with console commands how that alias changes, and cannot reproduce it, then go ahead, close it.

Arthmoor said:
I've now made several trips between the 2 camps and in every case, approaching the camp is selecting the proper NPC to fill the alias with. Even on successive round trips, the alias updates properly as you get close enough to each camp and thus the proper FieldCO is listed for that alias.

So as the guy on Reddit said, it's a CWO bug - I can't even say it's got an underlying cause as a Bethesda issue since nothing incorrect is happening.

Showing Comments 1 - 4 of 4