Issue Data
|
|
||||||||||||||||||||||||
It looks like this issue was supposed to have been fixed way back in v1.3.1. See (Bug 6671). Not sure how this is possible, but the console shows that dunPinewatchQST is still running. That could be related to the unique name not clearing as it should.
Comment #1 Nov 18, 2025 6:49 am
Edited by BlackPete on Nov 18, 2025 7:10 am
Assuming you still have this issue, we're going to need some additional info
What stage is dunPinewatchQST at?
What stage is USKPChangeLocation06 at?
The fact that dunPinewatchQST is still running suggests the patch quest never kicked in for some reason, but that shouldn't be possible.
What stage is dunPinewatchQST at?
What stage is USKPChangeLocation06 at?
The fact that dunPinewatchQST is still running suggests the patch quest never kicked in for some reason, but that shouldn't be possible.
Yeah, I went in there again and still have the same issue.
dunPinewatchQST: Stage 100
USKPChangeLocation06: Stage 0
dunPinewatchQST: Stage 100
USKPChangeLocation06: Stage 0
Yes, dunPinewatchQST is still running. It looks the five aliases haven't been cleared for whatever reason. I have no idea why that would be because the console shows that TGTQ01 isn't running.
- 5 Aliases for quest 'dunPinewatchQST' (000786B9) -
LOC 'PinewatchLocation' -> '' (0001928A)
REF 'PinewatchBoss_alias' -> '' (0002D23B)
REF 'PinewatchBanditChatter101' -> '' (0002D1FA)
REF 'PinewatchBanditChatter102' -> '' (0002D1F8)
REF 'PinewatchBanditChatter103' -> '' (0002D1F9)
- 5 Aliases for quest 'dunPinewatchQST' (000786B9) -
LOC 'PinewatchLocation' -> '' (0001928A)
REF 'PinewatchBoss_alias' -> '' (0002D23B)
REF 'PinewatchBanditChatter101' -> '' (0002D1FA)
REF 'PinewatchBanditChatter102' -> '' (0002D1F8)
REF 'PinewatchBanditChatter103' -> '' (0002D1F9)
Comment #5 Feb 5, 2026 3:49 am
Edited by BlackPete on Feb 5, 2026 3:56 am
Showing Comments 1 - 5 of 5

Issue Data