GWCA Based Polar Bear Bot

Mavygr · 01/01/2010, 22:56

when it happens, the mobs in the center of the area are not yet killed by snowmen so they kill it... the mobs that are sometimes stuck in the are that u circled are not messing with it (i think)... so something is not right with counting the number of mobs (if it has such a function) or it just does not wait enough time at the door. So the bot dies and it is written as ''failed run''.

kumulus · 01/02/2010, 00:22

bei mir started der bot zwar, läuft dann aber gegen die nächste wand bleibt da stehen

j66chevell · 01/02/2010, 00:37

Another Update, adding more time into the waiting at the end.

I can't seem to saty in game to test much, I keep getting random error 007s.

djsylver · 01/02/2010, 05:42

I'm getting every Second Run a Error 007 pls help me

Mavygr · 01/02/2010, 09:07

hi, 5 runs so far with the new version. 1 failed because of loot collecting too soon. It has also a problem with district change (it tries to change but then a messege appears saying that the party is already in an active district). I got that 007 error with a previous version, I haven't got it so far with this one. Keep up the good work

Minen · 01/02/2010, 09:22

in some cases he wont pick up the drops from the chest

Mavygr · 01/02/2010, 11:04

I didn't notice that happening.
But some times it moves to the npc position but stops a bit earlier and it doesnt get the quest. Then it goes to the wall (just behind rift warden) and waits while the bot says ''running gauntlet''. After that I got error 007... Any ideas why it does that?

dcgero · 01/02/2010, 11:20

Quote:

Originally Posted by Mavygr

I didn't notice that happening.
But some times it moves to the npc position but stops a bit earlier and it doesnt get the quest. Then it goes to the wall (just behind rift warden) and waits while the bot says ''running gauntlet''. After that I got error 007... Any ideas why it does that?

The error 007 can be prevented by using an UTP cable for the internet instead of wireless. Just test it.

grtz

Mavygr · 01/02/2010, 12:02

I use ethernet anyway. The error occured again just after the bot missed the rift warden and didnt get the quest (like described above). It appears as if the bot stops like 2 steps before the warden (resulting in failing to get the quest) and then starts the quest run (running gauntlet), only its not in the dungeon but in kamadan...

djsylver · 01/02/2010, 14:04

I try your Source and getting no error 7, i think there is an error in you compiled exe File....

Mavygr · 01/02/2010, 14:23

Quote:

Originally Posted by djsylver

I try your Source and getting no error 7, i think there is an error in you compiled exe File....

most of the times it gets it right... but there are times that it happens... maybe it is the exe as you say...

j66chevell · 01/02/2010, 16:31

I'm Getting the error007 just standing in Kamadan. I think, until they fix Kamadan, it will be very hard for me to test fixes or even duplicate issues.

Something they did in the holiday update really screwed some things up, especially in Kamadan.

Herr Daim · 01/02/2010, 16:36

Tried to start the source, but got this error ... dunno how to handle, new to this ;o))

j66chevell · 01/02/2010, 18:11

Quote:

Originally Posted by Herr Daim

Tried to start the source, but got this error ... dunno how to handle, new to this ;o))

Most likely that is due to having a different version of the GWCA Constants file and Graphics.dll file. The target foe command was added in the last update. Make sure you have the latest of both and see if that fixes it. That command is not used in the bot at all, so it must be comming from the constants call.

Herr Daim · 01/02/2010, 18:33

Fixed the old Problem, got a new ^^