[Issue] Could not parse any number at 33 0

[ashishmverma1]

Bot's working great after the update! Just encountered this issue once: Could not parse any number at 33 0

Log:

[07.04.15 1:30:45 AM] aok.coc.state.StateAttack handle INFO: StateAttack 
[07.04.15 1:30:46 AM] aok.coc.launcher.BotLauncher loop SEVERE: Could not parse any number at 33 0 
aok.coc.exception.BotBadBaseException: Could not parse any number at 33 0
    at aok.coc.util.ImageParser.parseNumberFromBinary(ImageParser.java:252)
    at aok.coc.util.ImageParser.parseGoldFromBinary(ImageParser.java:74)
    at aok.coc.util.ImageParser.parseLoot(ImageParser.java:302)
    at aok.coc.util.ImageParser.parseLoot(ImageParser.java:324)
    at aok.coc.state.StateAttack.handle(StateAttack.java:45)
    at aok.coc.state.Context.handle(Context.java:20)
    at aok.coc.launcher.BotLauncher.loop(BotLauncher.java:88)
    at aok.coc.launcher.BotLauncher.start(BotLauncher.java:72)
    at aok.coc.controller.MainWindowController$3$1.call(MainWindowController.java:154)
    at aok.coc.controller.MainWindowController$3$1.call(MainWindowController.java:150)
    at javafx.concurrent.Task$TaskCallable.call(Unknown Source)
    at java.util.concurrent.FutureTask.run(Unknown Source)
    at javafx.concurrent.Service.lambda$null$488(Unknown Source)
    at javafx.concurrent.Service$$Lambda$267/1610290296.run(Unknown Source)
    at java.security.AccessController.doPrivileged(Native Method)
    at javafx.concurrent.Service.lambda$executeTask$489(Unknown Source)
    at javafx.concurrent.Service$$Lambda$265/1250858972.run(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)

[07.04.15 1:30:46 AM] aok.coc.launcher.BotLauncher loop INFO: Waiting for dc checker to wake me up... 

Base screenshot from Bluestack window:

[norecha]

it should have an image in bug folder, can you attach that

[ashishmverma1]

Looking in the bug folder, I see it captured my desktop background instead of the loot area. Could be an issue with me pressing Ctrl or using my mouse while the bot was in action?

[norecha]

Those shouldn't be an issue. Only thing I can think of is you moving the window or putting something else in front. Nothing else makes sense.

On 7/3/2015 5:37 PM, Ashish Verma wrote:

Looking in the bug folder, I see it captured my desktop background instead of the loot area. Could be an issue with me pressing Ctrl or using my mouse while the bot was in action?

— Reply to this email directly or view it on GitHub https://github.com/norecha/pokubot/issues/74#issuecomment-118428826.

[ashishmverma1]

Well that ain't possible since I keep the Bluestack window on a secondary monitor and it stays untouched.

I'll just wait and see if the same issue happens again.

[1-Click-Dev]

Same problem with ashishmverma, I used in a virtual machine, untouched, nothing on the screen, only pokubot and bluestack screen. but I see same error often.