[gemma]

Not to be skeptical, but I've done a number of works that use start game enabled quests to add scripts; they work fine as of 1.7.

Skepticism is healthy, but in this case, generating them will do no harm at all. I'll be planting these in the USKP updates.

[AnDres MeZa]

Is it even possible to do if the file depends on Update.esm and one is participating in the beta?

I suppose I'll do it the next time I update, if I update (for example, if there is a new expansion, and it adds new followers, I'll have to do an add-on to Change Follower Outfits).

[Roy Harris]

I, personally, am not sure what all the CK loads when generating this SEQ file, so you can certainly try. It only seems to load the quest data out of your plugin, and nothing from the masters (Unless your plugin alters them, etc) so I assume you could do it even with the beta and update.esm as a master.

[Emily Martell]

I would love to see whats inside this small file.

[butterfly]

It's literally just a list of the formID's for the quests your mod alters/adds. The engine does something with it internally, but we aren't sure what.

[Rusty Billiot]

The CK is only concerned with the content of your own mod. All of the form IDs I've seen contained in the files so far are your own quests. Vanilla quests will be covered in the SEQ files found in Update.bsa. Yes, they've been there since 11/11/11 but nobody paid attention to them.

For instance, even though the UDGP modifies one quest which is start-enabled in vanilla, the SEQ file only contains the two form IDs for the retroactive fix quests.

[Connor Wing]

Just out of plain curiosity, I had a look at my backup archives and noted, that Update.bsa was first introduced with 1.4.20 (containing some updated armor meshes), and it has been updated three times since, including the current beta. Patches containing a fresh version of Update.bsa are:
- 1.4.20
- 1.5.24
- 1.6.87 (beta) / 1.6.89 (release)
- 1.8.145 (beta)

In the first two updates, no SEQ files were included inside Update.bsa. SEQ files were were first intoduced in the 1.6.87/1.6.89 update, which also coincides with the appearance of this bug. So, I think there has been some really bad luck in play here, with nobody making the connection.

[Joey Avelar]

Yeah. They altered something for some reason, thus requiring the SEQ files, and we simply never figured it out. I'm really glad that Joel and them reached out to us finally with this info.

[Bedford White]

Odd, I could swear those had been there since 11/11/11 but I guess not.

[Heather Stewart]

Update.esm has certainly always been there, while Update.bsa has not. But really, with all these files, and even more files of various kinds hidden further inside the archives, like the SEQ's, the whole setup currently seems incredibly convoluted.

[Richard]

Well one thing is for sure, when these updates come out people will pay more attention to mysterious new additions to the family.

[Charlotte X]

This is great news! Now that navmeshes and the dialogue bugs have finally been fixed, quest mods can start rolling!
Thanks for the information!

[Flesh Tunnel]

This is really great news I'm glad the devs reached out to us and we got this sorted

[Lisa Robb]

I've made a quick video that briefly explains how to do this using Steam's launch options to help spread word in addition to all of Arthmoor's posts: http://youtu.be/Ai3txtvoSbM

[cassy]

Think the SEQ falls under Misc in the TESArchive?

[Camden Unglesbee]

So with this is the dialogue bug solved? When I generate SEQ files?
I think with quest.start() scripts some have still reported oddities. Is it better and more save to undo the quest.start() workaround and go back to GSE and SEQ files?

[xemmybx]

So with this is the dialogue bug solved? When I generate SEQ files?
I think with quest.start() scripts some have still reported oddities. Is it better and more save to undo the quest.start() workaround and go back to GSE and SEQ files?

That's what I've done. I disconnected all of my 'starter' quests, and simply made the actual quests GSE, and with the addition of the SEQ file, everything works flawlessly as though there was nothing wrong. Because all that was wrong, was that we were missing the SEQ files. (Of course there may be a tad bit of buginess throughout, but this should fix 99% of the issues for everyone)

[Bigze Stacks]

Think the SEQ falls under Misc in the TESArchive?

Not sure I understand what you're asking here?

[Anne marie]

That's what I've done. I disconnected all of my 'starter' quests, and simply made the actual quests GSE, and with the addition of the SEQ file, everything works flawlessly as though there was nothing wrong. Because all that was wrong, was that we were missing the SEQ files. (Of course there may be a tad bit of buginess throughout, but this should fix 99% of the issues for everyone)

Yay! I can start modding again!

[Arrogant SId]

how is this done via the "command line"?

[Ellie English]

I'm curious to see if marking all quests as "Start Game Enabled" temporarily so they can be added in the generated SEQ and then toggled back off would have any positive/negative effect. Will need to test this myself.

Not sure I understand what you're asking here?

Likely means the BSA packager. Misc seems to be the appropriate category for this kind of file.

[Tamara Dost]

I personally wouldn't recommend simply making all quests SGE now that the dialogue issue is fixed. A quest that's SGE but isn't actually "started", will still show as Running with SQV. This could lead to problems if you alter scripts or aliases in this quest in a mod loaded save.

[John N]

mmm.. I have several "quests" (nothing with dialog only using the alias system) and never used/needed this SEQ.

Is your recommendation based on some a new thing?

Definitely include it if you have any new/altered quests in your mod. Can't hurt.

[lolly13]

I suppose I should specify, quests that in any way touch dialogue or scenes (containing dialogue?). Purely script quests appear to work alright.

- New link, I exported to 720p on accident the first time: http://youtu.be/Ai3txtvoSbM

[A Boy called Marilyn]

mmm.. I have several "quests" (nothing with dialog only using the alias system) and never used/needed this SEQ.

Is your recommendation based on some a new thing?

Nope. I discovered it myself. I made a quest very early on in my mod progress. SGE, Run Once etc etc as we were told in many tutorials. This quest is a quest for later in my mod.

Much later, I changed some of the alias info. Then in a save that already used my mod, the alias changes took no effect. This is because the quest is Running in the background, whether its started or not. I thought a quest had to actually be Started before no edits would change it. I was wrong.

So I recommend unless your quest needs to run at the start of the game, do not have it SGE.