HasQuestAvailable broken in latest release
- Thread starter crowley6
- Start date
DanielMahan
Member
- Joined
- Dec 1, 2013
- Messages
- 556
- Reaction score
- 2
I havent managed to get ANYTHING to work with the new release.
Tony
"The Bee"
- Joined
- Jan 15, 2010
- Messages
- 128,830
- Reaction score
- 571
That's because the log doesn't show the behavior, just the result. If you look, there are several if and while statement checks, where it checks if the npc has a quest available, and/or if you have the quest already.
The log does not show that it was returning false when checking if the npc has the quest available or not, even though I confirmed that he did.
Since the log doesn't show this, I did not include it in the first place, but it seems that the canned "Attach Log" response is commonplace, instead of actually reading what I said in the first place.
I've been a developer for more years than I care to count, so trust me when I say that it is not a profile issue, the HasQuestAvailable in the questing bot is not returning a correct value, and what me stopping and starting the bot repeatedly has to do with anything is beyond me, as I stopped it when it would stand there, not picking up the quests, and started to move on to the next area.
Hi Tony, the log that I attached was set to diagnostics, I see little reason to create a new one. The log that I attached shows the behavior that I mentioned, you'll see a bunch of while and if statements then it "has nothing left to do" and moves on to the next profile... this is the problem, the npc's had daily quests available, with the quest id's that it was checking for, but the bot was saying that they did not and so it didn't do anything but stand there for a couple secs then leave. That is why I stopped and started it repeatedly, to try and isolate the event that was causing the behavior. At this point, I have told you everything that you need to know to fix this issue, but you continue to ask for more logs.
I have a full time job, and this issue has already taken more of my time than I care for. Close this thread if you must, but attaching logs isn't going to change the fact that the logs do not show the problem, only the result.