Leaderboard

Dear community, In this release the following issues regarding OSBot 1 have been tackled: Login for high risk worlds Freezing random event engine related to hopping A change to gaussian distributions so they are capped and can't produce the VERY rare exceptions and thus bugs The isUnderAttack methods is now no longer just a logout timer. If nothing is facing you, it won't tell you that you're in combat. If something is facing you, it will check the actual logout timer. The above is implemented into the Run Away From Combat anti-random handler Both Login and Welcome Screen randoms have gotten an overhaul and work better The World Hopper should now have no more bugs All randoms that need a canReach() check now actually have it implemented Download for this version can be found here: http://www.osbot.org I know I should be focusing on OSBot 2, but on the other hand some of those fixes were a necessity. Sincerely, OSBot.org

Dear community, Sorry for another release but I only realized just now that most combat scripts don't have a random behavior hook for the Run Away From Combat random handler (which they should!). Therefore the changes I made to the handler were causing problems for all combat scripts, I have reverted those changes. The download can be found here: http://www.osbot.org Sincerely, OSBot.org

Thanks to @Jack for sparking the idea Variables: int currentXP; int gainedXP; int drawXP; int screenWidth = 520; int screenHeight = 337; double yMovement; int alpha = 255; In your onStart method: currentXP = client.getSkills().getExperience(Skill.YOUR_SKILL); Code for your onPaint method: gainedXP = client.getSkills().getExperience(Skill.YOUR_SKILL); if (gainedXP != currentXP) { drawXP = gainedXP - currentXP; currentXP = client.getSkills().getExperience(Skill.YOUR_SKILL); yMovement = 0; alpha = 255; } if (drawXP != 0 && alpha > 1) { g.setColor(new Color(255, 255, 255, alpha -= 2)); String drawString = "+ " + drawXP; int stringLength = (int) g.getFontMetrics().getStringBounds(drawString, g).getWidth(); g.drawString(drawString, screenWidth / 2 - stringLength / 2, (int) ((screenHeight / 2) - (yMovement += .7))); } If you're drawing other things after this remember to set the color back to what you want!! Here's what it looks like in game:

i got red swiggly line under mine_area, can u help?

@Zach has the best postcount. What a troll.

My best of 2013 was quitting Runescape.

so does your vagina

that twc looks sexy

Damn, there's a new release every couple hours or so haha

looks so good, so keen for this will be hoping to try this, maybe even buy membs back just for this script

Welcoooooooooooooome baaaaaaaaaaaaaaaaaaaack Raflesia!!!!!!!!!!!!! I will congratulate you again on Skype when I am on Never expected you to come back.

i dont give a shit about the updates, as long as you guys keep it free

How would he know what to do with the clue if he doesn't have it? Even if he is not hard coding it, how do you know what to do without the clues?

rules say 10 minutes

Omitting braces with only one line inside the statement is ok... but explain why you do that, otherwise people looking at the tutorial will be confused. Sometimes you did it with more than one line, though. I promise you that the walking method in the api does not recurse itself until the destination is reached, therefore you are able to easily fix it by doing what I stated above. Lastly, if this is a tutorial, make sure the code is presentable and functional with no logic errors or syntax errors. The entire point of a tutorial is to teach people how to code correctly.

I'll probably hit the 500 post requirement in a couple of years.