naivite / game-golem

Automatically exported from code.google.com/p/game-golem
0 stars 0 forks source link

Loop after entering new preferred targets #252

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.Introduce new preferred target
2.Set mode to Only/Until Dead
3.Wait for the Battle worker to start

What is the expected output? What do you see instead?
Instead of starting battles with the targets in question, Golem will loop 
between the Home page and the Battle page continuously.

What version of Golem are you using? Beta or release? On what browser?
r982, on Firefox

Does anything relevant appear in the Console? (ctrl+shift+J)
The console spams the following messages:

"Warning: Error in parsing value for 'filter'.  Declaration dropped.
Source File: http://apps.facebook.com/castle_age/index.php
Line: 0"

------------------------------------------------------------------

"Warning: Unknown pseudo-class or pseudo-element 'contains'.
Source File: http://apps.facebook.com/castle_age/index.php
Line: 0"

and same as the above but for 'even' and 'eq' as well.

------------------------------------------------------------------

"golem/Rycochet's Castle Age Golem: [r982] [10:04:27] Battle:
Unable to find Duel button, forcing reload"

"golem/Rycochet's Castle Age Golem: [r982] [10:05:11] Battle: Navigating to 
index.php"

------------------------------------------------------------------

This seems to be the most interesting message, and doesn't appear as often as 
the others

"golem/Rycochet's Castle Age Golem: !!![r982] [09:58:26] Battle: TypeError in 
Battle.update({"type":"data","self":"true","worker":"[worker Battle]"}}): 
data[i].name is undefined"

Original issue reported on code.google.com by bernardo...@gmail.com on 25 Jan 2011 at 10:12

GoogleCodeExporter commented 9 years ago
The first two warnings mentioned are irrelevant. The inability to find buttons 
seems to happen from time to time, usually when a page doesn't download 
properly and critical identification or navigation elements are missing. Not 
much for that other than a reload, which is what it already does. The final one 
is a fairly minor error, but I've put in a fix for it in r984. All that could 
really go wrong is the Battle status line wouldn't update, and some timers may 
fire that would otherwise be canceled. Perhaps a timer is causing the looping, 
but nothing else appears to have been skipped that might explain it. Give r984 
a try and see if that sorts it out for you.

Original comment by lur...@hotmail.com on 25 Jan 2011 at 9:48

GoogleCodeExporter commented 9 years ago
It's still happening. I appreciate the time you've put into it, though. Thank 
you, but don't worry about it too much. It might only be happening to me

Original comment by bernardo...@gmail.com on 26 Jan 2011 at 1:36

GoogleCodeExporter commented 9 years ago
I have the same problem, and my golem is r997(FF 3.6.13) The preferred target 
would not be attacked, and Golem looped between the Home page and the Battle 
page

Original comment by liangchi...@gmail.com on 28 Feb 2011 at 2:34

GoogleCodeExporter commented 9 years ago
There were some subtle issues with Firefox with the battle preferred list not 
always storing changes correctly, and not wanting to let go of the last entry 
in the list. Try r998 and see if that doesn't sort out the issue.

Original comment by lur...@hotmail.com on 4 Mar 2011 at 11:10

GoogleCodeExporter commented 9 years ago

Original comment by 0Artifi...@gmail.com on 21 Mar 2011 at 6:20