Yugod
-
Posts
231 -
Joined
-
Last visited
-
Feedback
100%
Posts posted by Yugod
-
-
setRunning(true);
Misses the running interface a LOT...
Ends up putting 1 click mouse on and music and such....
Would be nice if this could get fixed (Wasnt doing this at .38 and before, atleast not as often... It almost always misses now).
-
Ya doesn't get the inventory amounts for me as well.
Inventory invent = client.getInventory();Item Cash = invent.getItemForName("Coins");if(Cash.getAmount() < 50 000){}Spams like crazy... even if it withdrew already and it has more then 50 000 or even if i already had more then 50 000 to start with... -
Took you guys quite a while..
Thanks i guess
EDIT: IT withdraws, but it keeps doing so....
-
My bad!
-
My walk is spamming the minimap like 5x more then before the update of today.
Is this just my scripts? Or have other people also noticed that the bot spams the minimap way more now? It clicks like 5 times within 3 seconds... While its actually already running.
He did NOT do this yesterday or this morning, before the update.
EDIT:
ALSO the login bot seems to be way slower. He seems to have trouble finding the Click here to play interface..
Thought i'd call it in.
-
I kinda do agree with the fact chatbox mods could be a lil bit more online...
Till now i have only seen Sherlock He's quite active...
But sounds like someone is fishing for the spot :X
I'm online for almost 13 hours a day "hint hint"
-
I support this.
Imagine facebook puts a limit. ZOMG
-
Also got this one:
[ERROR][08/31/13 02:12:39 PM]: Error on executing random worker!java.lang.NullPointerExceptionat org.osbot.lPT2.A(ql:29)at org.osbot.lPT2.E(ql:60)at org.osbot.lPT2.onLoop(ql:31)at org.osbot.script.rs2.randoms.RandomManager.scan(xg:190)at org.osbot.lpT6.run(dn:117)at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)at java.lang.Thread.run(Unknown Source) -
Got this error...
But everything seemed to still work and stuff...
Thought i'd call it in thought.
[ERROR][08/31/13 12:59:25 PM]: Error on painter thread!java.util.ConcurrentModificationExceptionat org.osbot.x.A(se:376)at org.osbot.rA.next(se:438)at org.osbot.engine.Bot.A(jl:586)at org.osbot.engine.canvas.BotCanvas.A(sl:161)at org.osbot.lPt6.run(ue:52)at java.lang.Thread.run(Unknown Source) -
[iNFO ][08/30/13 09:14:38 AM]: Activating random : Talking Random Solver[iNFO ][08/30/13 09:14:48 AM]: Solved Cap'n Hand talking[iNFO ][08/30/13 09:14:48 AM]: Exited random : Talking Random SolverAre randoms still broken?
-
Scripts wont start.
Could be that the id's changed in todays update of RS.
It was the issue with my script. Had to adjust id's before it worked.
-
Zach,
walk(area); works fine again.
Also the login bot seems to function normally as it should.
Goodjob. Will report regarding any randoms once i get them.
-
The walking and login api were broken in 34 so he fixed that hopefully. Gonna test now.
-
[ERROR][08/29/13 06:14:54 PM]: AbstractMethodError on script worker.java.lang.AbstractMethodError: client.getMinimapX()Iat org.osbot.script.rs2.Client.getMinimapX(lm:1582)at org.osbot.script.rs2.utility.Utilities.getMinimapScreenCoordinate(fe:180)at org.osbot.script.mouse.MinimapTileDestination.getDestination(nm:199)at org.osbot.script.mouse.MinimapTileDestination.destinationReached(nm:127)at org.osbot.script.rs2.map.Position.walkMinimap(xe:15)at org.osbot.script.MethodProvider.walkMiniMap(gj:1074)at org.osbot.script.MethodProvider.walk(gj:392)at org.osbot.script.MethodProvider.walk(gj:490)at org.osbot.script.MethodProvider.walk(gj:2176)at org.osbot.script.MethodProvider.walk(gj:330)at org.osbot.script.MethodProvider.walk(gj:501)at Mining.onLoop(Mining.java:78)at org.osbot.DA.run(ve:74)at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)at java.lang.Thread.run(Unknown Source)[iNFO ][08/29/13 06:14:54 PM]: Stopped script : Mining
-
I SUPPORT THIS 1389172397231731723 %.
setRunning(true); missing
in Archive
Posted
Isn't a hard fix.
So thought i'd call it in so it can get fixed as well when next version rolls out