search

w35l3y / userscripts

Public userscripts to be used with Greasemonkey
http://gm.wesley.eti.br
GNU General Public License v3.0
45 stars 23 forks source link

Neopets_Battledome_Fight! refuses to begin battling. #15

Closed mmehalko closed 9 years ago

mmehalko commented 10 years ago

Browser:
FF 30.0 Greasemonkey:
2.0 Script:
Neopets_Battledome_Fight! Installation url:
https://github.com/w35l3y/userscripts/blob/master/scripts/Neopets_Battledome_Fight!/161251.user.js Error Message:
Not really an error message, but I'm receiving "You should fight at least once to verify whether it is capable of winning consecutively by its own. Select its weapons and ability that you would like to use automatically." over and over again. Obs.:
I was prompted with the "You should fight..." message stated above and fought once with my preferred weapons. As the page reloaded, it asked me the same message again. After fighting 3 or 4 times without any change, I decided to set my weapons manually through the opponent options. After doing this, it asked me how many times I wanted to fight - I checked the automatic amount and hit okay. The autofighter didn't kick in, so I figured I'd manually fight again. After doing this about 5 times, it still didn't kick in.

Thank you for all that you do, your scripts are amazing! +1:

Edit: I read another member was having issues so I did what your comment suggested and that was look at the error messages. http://pastebin.com/Rj2MdxS2 Any ideas? Please and thank you! c:

w35l3y commented 10 years ago

Your message is very complete. This kind of message really help the fixing process. Thanks. The only downside was that you created your own issue instead of commenting in the one that you found, but it is understandable because your title is much more descriptive.

Once I get some spare time, I will try to reproduce these steps and fix it. In the mean time, it is suggested to downgrade greasemonkey to 1.15

mmehalko commented 10 years ago

I apologize! I'll remember to post on previous posts next time. I forgot to mention that I did try downgrading it but it wasn't seeming to work even when I downgraded (but if anyone else is having the same issue, I realized I had not clicked the 'auto update add ons' option off). Once I turned off the auto update add ons, the script is working like a charm again.

Thank you for such a timely response and solution!

w35l3y commented 10 years ago

I followed your steps but still wasn't able to reproduce the error you mentioned. The script should work even on GM 2.0.

So, for those with the same problem... more details are needed or downgrade to GM 1.15