Jump to content

Need help with possible cause of quest startup failure


Recommended Posts

I need help. In the quest mods I'm involved with, I have received some reports that some quests won't start. They can't start quests even using console commands. Me and the authors have never experienced that problem, and the quest has no conditions, so I believe that the quest aliases fill-up has failed. I searched on Google and learned that it would happen if any of the quest actors were dead, and confirmed that it would be so if I killed someone. I asked the reporter to use the console to confirm that all actors are alive, but they say that all actors are alive.

 

Are there any other possible causes? If there is an article that may be helpful, please tell me the link.

Thanks.

Link to comment
Share on other sites

Hi Pentacrow, thanks for reply.

 

Specifically mod is here : Rigmor of Cyrodiil

 

This mod has a main quest line consisting of 12 quests, and starts sequentially from quest 1, and of course has SEQ file.

This is fine for most players, but some players have problems with certain quests (quest 7 and 10) not starting.

Perhaps the underlying cause is a conflicts with other mods, but I want to know how it can block the start of the quest.

Link to comment
Share on other sites

As I can see, there is no such thing as a common or a difference in the quests in question and other quests. And no common terms are found in the alias definitions of the two quests where this problem occurs. One quest contains more than 50 Unique Actors and Specific References aliases, while the other has only 7 Unique Actors aliases. And of course, all Unique Actors have Persistent Locations and Essential attribute.

The two problem quests are both triggered by a move to another cell/worldspace using defaultSetStageTRIG activator, but there are other similar quests and works fine.

Link to comment
Share on other sites

I have made some progress. The quest was started by adding "Allow Reserved" to all quest aliases.

However, the actors used in the aliases are all mod-specific NPCs, and this mod does not use the "Resrved" alias, so I have no idea why this works.

Link to comment
Share on other sites

  • 4 weeks later...

Although no clear solution has been reached, some have been found.

 

- The "Allow Reserved" flag worked fine. This solves some user problems.

- If you install the "No Essential Npcs Ini File" option file from No Essential Npcs, the quest may not start due to essential actor dead. This is the same as setting [GamePlay] bEssentialTakeNoDamage=0 in Skyrim.ini. In this case, we can solve it by resurrecting the actor on the console.

- I don't know either a quest bug or a conflict with other mods, it also happens when the actor that should fill in the quest alias without the "Initialily Disabled" flag is disabled. In this case, we can solve it by enabling the actor on the console.

 

Unfortunately, there are cases where trying the above does not solve the problem.

Link to comment
Share on other sites

  • Recently Browsing   0 members

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