Page 1 of 1

pathway_fallhaven quest broken

Posted: Thu Aug 10, 2017 8:51 pm
by carceris-magister
In conversationlist_pathway_fallhaven.json, questProgress value 10 is required to be able to ask the watchman why the path is closed, but the only way to get to that level is to ask the watchman why the path is closed, so it's currently impossible to start the quest.

That seems to have broken with this commit:

Code: Select all

commit 91ac4cc44965cc466cbab90ce673c8542841a903
Author: Zukero <kpochat@gmail.com>
Date:   Wed Dec 21 17:18:34 2016 +0100

    Replaced all JSON files by ones re-exported by ATCS, to prepare for
    cleaner diffs.

Re: pathway_fallhaven quest broken

Posted: Fri Aug 11, 2017 7:03 am
by Zukero
Nice find. I'll look into it.

Just a note: this is an unreleased quest, planned for next version.

Re: pathway_fallhaven quest broken

Posted: Fri Aug 11, 2017 9:29 am
by Zukero
I fixed it, but it won't show up on github before a bunch of hours.

If you're venturing in the realms of the development versions, I'd suggest using the "stoutford_tests" branch over the "master" one these days. More stuff to play with, more bugs to find.

Re: pathway_fallhaven quest broken

Posted: Fri Aug 11, 2017 10:55 am
by carceris-magister
Thanks! I'll switch to that branch.

Re: pathway_fallhaven quest broken

Posted: Fri Aug 11, 2017 11:01 am
by carceris-magister
If I do send any pull requests (no promises), should they be against the stoutford_tests branch?

Re: pathway_fallhaven quest broken

Posted: Fri Aug 11, 2017 11:58 am
by Zukero
It depends on what the content of the PR is. If it has no ties to Stoutford, or other content exclusively in the stoutford_tests branch, I'd rather have them against "master".