Type:
Bug
Severity:
Minor
Game version:
Morrowind
Concerns:
TR_Mainland
Related Release File:
Found in Version:
Status:
Fixed for Version:
Item/Script Reference:
Identifier:
TR_m3_Rd_Burden
Name:
Burden of Proof
Description:
Upon finishing the quest "Burden of Proof" and making Diranya satisfied, she tells the player that they will get access to Roa Dyr's services. The same information also appears in the journal. However, the mer in Craftsmen's Hall will still give you a Service Refusal response, and tell the player that they only serve members of House Indoril. There are a few other NPCs offering services in Roa Dyr, but as far as I understand they did that also before finishing the quest. I might have missed something, but I interpret Diranya's offer as you will get access to all of Roa Dyr's services, which is not the case.
Comments
The same case. I have tried
The same case. I have tried to restart the quest via the console, but the outcome was identical
Investigating this I noticed
Investigating this I noticed TR_m3_Diranya lacks a proper NPC script and doesn't have a TR_Map variable.
There's nothing in the rewards dialogue that unlocks services... but it could be implemented in the service refusal dialogue itself...
edit:
Nope, there's currently no mechanism for unlocking services in Roa Dyr. But it could be implemented rather easily.
There's an entry in [service refusal] that goes "I am in the service of the Indoril Ilvi, outlander. I have nothing to offer one not of his house." filtered to Roa Dyr. This blocks any House Indoril NPC (bar a small number of exceptions) from providing services to non-Indoril players. Add a filter for Journal TR_m3_Rd_Burden < 500, and this service refusal entry will be disabled once the quest reaches the appropriate stage. This will still block services from higher-ranked Indoril in Roa Dyr (Concordant Minister and up) for non-faction members, but that shouldn't be an issue.
Thanks for your help, this
For the record, that exact
For the record, that exact filter was intended to be implemented, and I thought for sure I had implemented it, so either I did a big oopsie or it somehow got wiped after the fact. It should be (re)implemented.
There's an entry in [service
EDIT: Obsolete.