Czar

Add your account in the account manager to be logged in, simple. Clearly I shouldn't leave anything to the client since it is historically unreliable. I will be disabling OSBot's random handler and providing the script with my own version. Script updated to version 4.0. The update should be live within 12 hours. Thanks for the feedback! EDIT: Also added a new paint to reflect the new version number Version 4.0 - Anti-randoms fixed - Slight optimization of code logic Let me know if you would like to see any more updates, as of now I can't think of anything to add

+11111111111111111111111

still going strong with blue name, hopefuly i dont get kiked

lmao XD

Screenshot and post here I want to see this. And evil bob problem? Explain more please EDIT: Please make sure to use the latest OSBot client version 2.3.19

> needs help, finds problem > posts anyway

Yeah it does support trout/salmon in Shilo Village and banks too. EDIT: I'm thinking of making it check XP after it levels up (like most players do) for extra anti-pattern

Script has been updated by Alek, thanks man! Enjoy, shark fishing has been fixed now

Make sure to use OSBot version 2.3.19 (latest one) and restart client, if this still happens please post here and I will get this fixed immediately.

1st

Yes this will be fixed today, the update is pushed on my side we just have to wait until it's updated on the SDN. The developer is currently online so I'm sure he will update it today And that's how the new GUI looks like

Version 1.17 - Added GUI option for no afking - Added GUI option for not displaying paint (to save memory) - Added a new form of antipattern - Fixed fishing spots with right-clicking (sharks and other spots) Update is pushed, once Alek approves of the updates they will be live.

Alright I'll add the option in the GUI. So there will be absolutely no paint unless you enable it at the start.

Alright I'll add a small button to show/hide paint in the corner, thanks, any other suggestions before the script is updated?

Alright no problem, made the likelihood of doing that 1% chance. All it took was a line of code ;) Update will be live within 12 hours, sorry for that guys!

Is it doing this very often? It's supposed to do it once in a while, and after that it manages to harpoon by right clicking. If not, it will be fixed ASAP. EDIT: Can you confirm that it doesn't right click at all?

NPC cow = npcs.closest("Cow","Cow calf"); That shouldn't be declared outside a method, remove that and remove if(!inventory.isFull() && COW_AREA.contains(myPlayer()) && !myPlayer().isUnderAttack() && !cow.isUnderAttack() && cow != null) { return State.ATTACK; } the red part along with it EDIT: Also, try to debug this in onPaint(Graphics2D g) g.drawString(getState().toString(), 15, 15); Just to know which state you are in, it helps alot.

I'm glad you chose CzarRangeGuild Thanks man, and enjoy ;)

Gj man, @@@@@@@@@@@2

idk

Well usually when the script is working, there aren't many posts on the thread. If it were broken, trust me, there would be a lot of posts here XD As of 1/23/15, the script is currently working. The OSBot client update didn't break this script.

Option for afking/not will be added in the next update. Also, did you set up your account in the account manager? EDIT: Update pushed, it will be live within < 12 hours. - This is a small update which adds an option in the GUI to allow AFKing or not (part of the 'antiban')

The script sometimes AFKs and logs out as part of the antiban, but it doesn't stop. Just make sure your account is set in the account manager and it will log back in. If you would like this removed, I can add an option in the GUI to move camera/right click to not be idle

It usually takes some time (maybe 5 mins) if it doesn't work, you can always refresh your script browser or restart client, if it still doesn't show then check if you actually bought the script

You can override OSBot's logger just as you can do so for paint, onLoop, onMessage etc, just make your own @Override public void log(String message) { //save message to file } This is what does the logging: getBot().getLogger().debug(message);