Quote:
Originally Posted by Restia Ashdoll
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
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.