Quest book issue #138


Closed
  • BuddyTTV created this issue May 27, 2017

    In the "Arming Yourself" quest line, after completing the first quest on the left side (Armor Plus Enemy Minus), you are not able to open the next quest in the line (Call me Hawkeye) as it says it requires "Feel the Power" quest... which is not able to be completed as it is not in the current quest book in the latest update.  Reported this a couple of weeks ago and was told this was fixed, but it wasn't.  I went into bq_admin edit mode and noticed that the quest calls for Feel the Power to be completed, which seems to be removed from the quest book and not able to be completed, removing "Feel the power" quest requirement for "Call me Hawkeye" should fix the issue.

  • WarNachos posted a comment May 29, 2017

    I had the same problem.  I tried a few things but here's the one i think fixed it.  If the first one doesn't work then do the rest. Full exit out of the game before making these edits.

     

    Go to curse/minecraft/instances/craft of the titans/saves/YOURWORLDNAME/betterquesting

     

    Open "QuestDatabase" and ctrl+f search for "Hawkeye".  Scroll down a bit until you see:

     

    "preRequisites": [
            150,
            152

     

    Change that to:

     

    "preRequisites": [
            152

     

    Try that and if it doesn't work then do the following:

     

    Go to curse/minecraft/instances/craft of the titans/config/betterquesting  open "DefaultQuests", ctrl+f search for "Hawkeye" scroll down a bit until you see:

     

    "preRequisites": [
            150,
            152

     

    Change that to:

     

    "preRequisites": []

     

    Now go to the Resources folder in that same folder (/config/betterquesting/resources/betterquesting)  there's a DefaultQuests file in there, do the same as above.

     

    Basically you're removing Feel the Power (quest ID: 150) from being a preRequisite for Hawkeye.


    Edited May 29, 2017
  • Boolyman posted a comment May 30, 2017

    This is fixed in the next update.  1.18


    Edited May 30, 2017
  • Boolyman closed issue May 30, 2017

To post a comment, please login or register a new account.