GW Working Bots 2020

06/20/2021 18:26 Restia Ashdoll#1981
Quote:
Originally Posted by CookiesCream View Post
Ich glaube es hängt in irgendeiner form damit zusammen:

f $NearestDistance > 4000 Then
Out("Boss Group Dead")

Sleep(2000)

Out("Accepting Quest Reward")
Do
$Tekks = GetNearestNPCToCoords(14618, -17828)
GoNPC($Tekks)
TolSleep(1000)
Dialog($TekksComplete)
Until Not IsDllStruct(GetQuestByID($hTekksWar))

Die letzte Zeile macht mir dabei etwas Zahnschmerzen.
Er schnallt einfach nicht, dass die Quest schon abgeben wurde...

was natürlich immernoch nicht erklärt, warum das auf dem anderen gw account tadellos läuft
Dann guck doch einfach erstmal of der struc call und getquest id überhaupt funktioniert .. dann check ob die questid noch passt.. etc. - kann ja nicht so schwer sein, alle teile da mal einzeln zu checken
06/20/2021 20:50 CookiesCream#1982
Quote:
Originally Posted by Restia Ashdoll View Post
Dann guck doch einfach erstmal of der struc call und getquest id überhaupt funktioniert .. dann check ob die questid noch passt.. etc. - kann ja nicht so schwer sein, alle teile da mal einzeln zu checken
natürlich ist das nicht schwer...
aber wieso sollte der bot dann mit meinem main account laufen und alles richtig machen, wenn dort irgendwie ein fehler drin wäre?
es klappt ja auch alles... bis zu dem Moment, wo er die quest abgegeben hat.
da gerät er irgendwie in einen loop oder so und will sie immerwieder abgeben.



ich checke jetzt nocheinmal sämtliche id´s...
mal sehen was dabei rauskommt


EDIT: Alle ID´s sind in Ordnung

Edit II:
Ich habe das Problem gelöst... aber die Ursache dafür umgangen.
Jetzt geht der Bot erst zur Kiste, lootet und gibt dann permanent die quest ab, bis zum map-change...
ab da läuft alles wie gewohnt.

Erklärt zwar immernoch nicht, warum auf dem einen account alles funktioniert und dem anderen nicht aber damit kann ich erstmal leben.
06/21/2021 10:02 Restia Ashdoll#1983
Quote:
Originally Posted by CookiesCream View Post
natürlich ist das nicht schwer...
aber wieso sollte der bot dann mit meinem main account laufen und alles richtig machen, wenn dort irgendwie ein fehler drin wäre?
es klappt ja auch alles... bis zu dem Moment, wo er die quest abgegeben hat.
da gerät er irgendwie in einen loop oder so und will sie immerwieder abgeben.



ich checke jetzt nocheinmal sämtliche id´s...
mal sehen was dabei rauskommt


EDIT: Alle ID´s sind in Ordnung

Edit II:
Ich habe das Problem gelöst... aber die Ursache dafür umgangen.
Jetzt geht der Bot erst zur Kiste, lootet und gibt dann permanent die quest ab, bis zum map-change...
ab da läuft alles wie gewohnt.

Erklärt zwar immernoch nicht, warum auf dem einen account alles funktioniert und dem anderen nicht aber damit kann ich erstmal leben.
Der Punkt ist, dass ggf. das questid auslesen dann z.b. nicht 100% funktioniert deswegen hätte ich einfach mal trocken überprüft ob der eine beliebige questid die du hast bspw. richtig wiedergibt - also einfach mal printen lassen.

Warum das manchmal klappt und manchmal nicht kann halt auch ggf. zufall sein, oder was weiß ich- deshalb hätte ich halt überprüft ob wirklich jede Funktion das Returend was sie soll..

das sollte jetzt auch nicht abwertend klingen, aber das ist ne "arbeit" von +/- 10min und erspart in der Regel eine menge rumgerate.

Wenn alle Funktionen richtig funktionieren kann man das Problem ausweiten ggf. mit nem dritten Account testen .. blablabla

Permanent die falschen dialoge zu schicken kann ja jetzt nicht die lösung sein die du haben willst.
06/21/2021 10:03 AMDXD#1984
its working!!
06/23/2021 04:35 logicdoor#1985
Quote:
Originally Posted by Restia Ashdoll View Post
there is an explanation for that issue eventhough you don't find ich rightaway - best way to narrow down the issue is using different parts of the code and see what works and what doesn't at best on the "wrong" account
I gave him newer code via PM a few days ago, because the last version is 2.0 and 0.72 is really old but it doesn't run on GWA2. Waiting for his response but I am not sure if he knows how to plug it in. I just need him to tell me what more help he needs.

I believe 0.71 and 0.72 were updated by someone else so I am not even sure what his current code looks like.

I built code to avoid the character getting out of range of heroes to allow for resurrection, and also to suicide when there is no more rezz remaining, and to move out of poison traps above a certain party health depletion rate. Also wipe management to ensure it is catching the right way point after a wipe at the start of level 2. But all of it is via the logic framework so it might take some time to get it all fixed using GWA2. But it's actually a good learning experience to try and fix suboptimal behavior in existing bots.

Quote:
Originally Posted by CookiesCream View Post
Ich glaube es hängt in irgendeiner form damit zusammen:

f $NearestDistance > 4000 Then
Out("Boss Group Dead")

Sleep(2000)

Out("Accepting Quest Reward")
Do
$Tekks = GetNearestNPCToCoords(14618, -17828)
GoNPC($Tekks)
TolSleep(1000)
Dialog($TekksComplete)
Until Not IsDllStruct(GetQuestByID($hTekksWar))

Die letzte Zeile macht mir dabei etwas Zahnschmerzen.
Er schnallt einfach nicht, dass die Quest schon abgeben wurde...

was natürlich immernoch nicht erklärt, warum das auf dem anderen gw account tadellos läuft
As far as I know the dialog method to accept quest reward doesn't work correctly anymore, instead using the GetReward() function with just the quest ID as a parameter instead of the modified dialog parameter should ensure that the quest is accepted in all cases.

I am not sure why the dialog method is working on your first account, though. All I can think of is using different GWA2 versions by mistake, I would make sure there is no other GWA2 or add-ons file linked accidentally from a different location. Apart from latency issues preventing the quest from being accepted on the second account, or having a different dungeon quest or griffs war still active, which is know to sometimes bug the dungeon, same code should produce the same results.

Aa Ashdoll said, printing the results of each function should allow you to isolate the faulty behavior, but based on what you said it really seems to be the dialog not accepting the reward so try replacing it with the replacement code I gave you.
06/23/2021 15:32 Restia Ashdoll#1986
Quote:
Originally Posted by logicdoor View Post
I gave him newer code via PM a few days ago, because the last version is 2.0 and 0.72 is really old but it doesn't run on GWA2. Waiting for his response but I am not sure if he knows how to plug it in. I just need him to tell me what more help he needs.

I believe 0.71 and 0.72 were updated by someone else so I am not even sure what his current code looks like.

I built code to avoid the character getting out of range of heroes to allow for resurrection, and also to suicide when there is no more rezz remaining, and to move out of poison traps above a certain party health depletion rate. Also wipe management to ensure it is catching the right way point after a wipe at the start of level 2. But all of it is via the logic framework so it might take some time to get it all fixed using GWA2. But it's actually a good learning experience to try and fix suboptimal behavior in existing bots.


As far as I know the dialog method to accept quest reward doesn't work correctly anymore, instead using the GetReward() function with just the quest ID as a parameter instead of the modified dialog parameter should ensure that the quest is accepted in all cases.

I am not sure why the dialog method is working on your first account, though. All I can think of is using different GWA2 versions by mistake, I would make sure there is no other GWA2 or add-ons file linked accidentally from a different location. Apart from latency issues preventing the quest from being accepted on the second account, or having a different dungeon quest or griffs war still active, which is know to sometimes bug the dungeon, same code should produce the same results.

Aa Ashdoll said, printing the results of each function should allow you to isolate the faulty behavior, but based on what you said it really seems to be the dialog not accepting the reward so try replacing it with the replacement code I gave you.
I am totaly with you making sure a quest is accepted should be an easy task ;) you can go from reading out the log to just check if your gold had increased xD might be a bad work around but hey it's not stupid if it works.

Never the less it's an easy task to fix so if you need further help logic and i will responde i guess.
06/23/2021 20:52 zeiow#1987
hi, when im trying to use the chest run bot updated, i click on Run but nothing happens, what should i do ?
06/28/2021 03:49 OriginsEXE#1988
Hi all

GoSignPost is not working. I have updated headers but still no success.

Func GoSignpost($aAgent)
Local $lAgentID

If IsDllStruct($aAgent) = 0 Then
$lAgentID = ConvertID($aAgent)
Else
$lAgentID = DllStructGetData($aAgent, 'ID')
EndIf

Return SendPacket(0xC, $HEADER_SIGNPOST_RUN, $lAgentID, 0)
EndFunc ;==>GoSignpost

Global Const $HEADER_SIGNPOST_RUN = 0x57 ;Runs to signpost


Any Ideas? Thanks
06/28/2021 05:49 Jarriola#1989
Anyone have a working Kilroy Bot? Mine doesn't pick up any items.
06/28/2021 15:11 Lutziffer#1990
OmniFarmer_Presearing V2.4.0.1 working for anyone?
It detects the character but i canot edit the configs nbeitehr does it something after starting the bot

- I was able to resolve the Problems by getting a new GWA2 and chaneg some parts of th script Ty anyways
06/29/2021 23:32 OneStrangeGuy#1991
Quote:
Originally Posted by OriginsEXE View Post
Hi all

GoSignPost is not working. I have updated headers but still no success.

Func GoSignpost($aAgent)
Local $lAgentID

If IsDllStruct($aAgent) = 0 Then
$lAgentID = ConvertID($aAgent)
Else
$lAgentID = DllStructGetData($aAgent, 'ID')
EndIf

Return SendPacket(0xC, $HEADER_SIGNPOST_RUN, $lAgentID, 0)
EndFunc ;==>GoSignpost

Global Const $HEADER_SIGNPOST_RUN = 0x57 ;Runs to signpost


Any Ideas? Thanks
The function is rigth and working, the header is correct.
Maybe your issue is how you declare the $aAgent constant.
07/04/2021 22:24 borotroth#1992
I'm trying to get the pongmei valley chest bot or the boreal one working and the pongmei one tells me "Starting run #1" but actually doesn't do anything. The boreal one acts as if it's zoning and stuff but again, does nothing.

I'm really bad at stuff like this and have been able to get bots working before when they give me errors but I seriously have no idea where to start with these ones.

Not begging for a fix, but I'd appreciate a nudge in the right direction to get me started.
07/05/2021 08:58 natsilent#1993
Hello,

I found this :

SendPacket(0x8, 0x19, GetHeroID($aHeroNumber)) ;

To make a hero dropping a urn, but it doesnt seems to work, am i doing something wrong ?

Thanks
07/05/2021 18:10 DerMoench14#1994
The Header is wrong.
The correct Header is 0x15
07/05/2021 19:34 zeiow#1995
Hey, any GWA2 for chestrun on pongmei ?