Daggerfall Workshop Forums

This one seems like Hazelnut's wheelhouse. Just let me know if I'm needed at all.

It's happening with the Fighters Guild too now, with another character I started. Just did one quest (classic) and now it's the same error with them.

The error itself is happening in the following line because oneTimeQuestsAccepted is null and the code is trying to access its members.
It's just a simple logic error. The oneTimeQuestsAccepted list is only initialised when a one-time quest starts, but the same list is also being used to select a quest before it starts.

I moved the initialisation of oneTimeQuestsAccepted to right before its actually used, and added another safety null check when starting a one-time quest.

Hazelnut might want to refine this one further when he has time, but this will address this specific issue from next round of builds. I'll push out new builds a little sooner to fix this problem so people can play your quests again.

Oh, sorry Interkarma - been so focussed on my performance work/fun that I forgot all about this because it wasn't in bugs forum.

S'right! Was a 5 minute fix and I'm happy to have been able to help.

Yeeeahh! Thank you

EDIT: I see you already mentioned a hotfix build so I deleted my request Reading!

I altered the quest lists to remove the 1 values temporarily, so there's no need for an accelerated build. This fix is working fine from what I'm testing.

Yes, that should do it too, that null collection is only checked for one-time quests.

Will still get a hotfix up soon, just have a few PRs to finish testing.

Jay, could you recheck this with latest build please. I'll look into it if is still an issue.

Edited out