Quest not on API yet

[seeker]

So i'm trying to check if the Client of Kourend quest is done of my script, but it hasn't been added yet to the API since it's newish. Is there anything i can do at all?

Edited July 31, 2017 by seeker

[Deceiver]

color of the text or config

[seeker]

Just now, Deceiver said:

color of the text or config

ye i was thinking about colour. But that's too much work. What do you mean config?

[Chris]

Config API

[Eagle Scripts]

Look into the Configs; every quest has a certain config from which you can see the state of the quest; meaning you can also determine when it has been completed

[Alek]

I like how there are all these suggestions for writing your own API instead of submitting a "Client Suggestion" to get the quest added to the existing API. 

[seeker]

6 minutes ago, Eagle Scripts said:

Look into the Configs; every quest has a certain config from which you can see the state of the quest; meaning you can also determine when it has been completed

Ah right. One question though, how do i find the config ids? I've enabled configs on the debug option on the client and all i'm getting is just 1999 - 1989 with all 0's not changing even after opening quest?

 

Cheers

[JARNQ]

9 minutes ago, seeker said:

Ah right. One question though, how do i find the config ids? I've enabled configs on the debug option on the client and all i'm getting is just 1999 - 1989 with all 0's not changing even after opening quest?

 

Cheers

Try restarting your computer

[seeker]

2 minutes ago, JARNQ said:

Try restarting your computer

no lol

[HeyImJamie]

36 minutes ago, Alek said:

I like how there are all these suggestions for writing your own API instead of submitting a "Client Suggestion" to get the quest added to the existing API. 

To be honest for checking quests it's actually better to write your own 'API'. I've been told the Quest API checks colour which has given me false calls in the past whereas checking via configs do not. We could collect together completed quest configs tho and put them in client suggestions?

35 minutes ago, seeker said:

Ah right. One question though, how do i find the config ids? I've enabled configs on the debug option on the client and all i'm getting is just 1999 - 1989 with all 0's not changing even after opening quest?

 

Cheers

You'd need to complete the quest and check for changes. or find the quest config and grab its child off a completed acc

Edited July 31, 2017 by HeyImJamie

[Alek]

1 hour ago, HeyImJamie said:

To be honest for checking quests it's actually better to write your own 'API'. I've been told the Quest API checks colour which has given me false calls in the past whereas checking via configs do not. We could collect together completed quest configs tho and put them in client suggestions?

You'd need to complete the quest and check for changes. or find the quest config and grab its child off a completed acc

When are quests green and not finished, or when quests are red but already started?

[The Undefeated]

2 hours ago, Alek said:

I like how there are all these suggestions for writing your own API instead of submitting a "Client Suggestion" to get the quest added to the existing API. 

True. But the way how quests are checked now is not viable at all. Had multiple occasions it returning as not started while it was finished.