Eliot

You go first unless higher FB. Add skype: eliot.osbot no period after osbot

This happens a lot when ending scripts: [ERROR][06/01 04:11:37 PM]: Uncaught exception! java.lang.ThreadDeath at java.lang.Thread.stop(Unknown Source) at org.osbot.rs07.event.ScriptExecutor.restart(zm:113) at org.osbot.rs07.event.ScriptExecutor.suspend(zm:71) at org.osbot.rs07.event.ScriptExecutor.stop(zm:79) at org.osbot.rs07.event.ScriptExecutor.stop(zm:137) at org.osbot.Lpt7.run(fn:881) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)

I can assure you he is not ignoring you, it will be fixed.

It's been nice for a while. :P

Well, if you want to be more efficient: short planksPerHour = (short)(3600000d * planksCreated / System.currentTimeMillis() - startTime);

Check this out: MiniMapTileDestination(Bot bot, Position position) Creates an instance of this mouse destination for a tile displayed on the minimap.

As @TheScrub stated, you're going over Integer.MAX_VALUE and thus overflowing. Just change the order of operations. You might have some errors if you store some values as integers, but you should be able to work those out. long planksPerHour = (long)(planksCreated * (3600000.0 / (System.currentTimeMillis() - startTime));

You obviously have minimal knowledge of the source in which OSBot derives revenue. Sponor/VIP sales accounts for a huge portion of the sites income. Keep in mind OSBot only gets 30% - fees of each script sale. As of right now, it does not seem monthly rates will be mandatory, though this is subject to change.

Haha, I tip my fedora to you. You sir are a gentleman and a scholar.

Yes, do it this way.

How do you know if the door is open or closed?

See Swizz's answer.

localWalker.walk(position); From this you can quite easily make a method to traverse a path.

I don't believe there will be an OSBot 2 version of that particular script by that individual scripter (I could be wrong). Lifetime means lifetime of OSBot 1, which is coming to an end.

Look at his last script update.

I'm fairly certain @Ande has left OSBot.

Did you really expect OSBot to last for your entire life? OSBot 1 client will remain functional for several months, during this time you can bot all you want with your OSBot 1 scripts.

You should be checking things such as facing , in combat, etc (all of those are avaliable in the API) to see if you're in combat. If and only if you're not in combat should you attack a cow. As for the area problem, I'm not sure, try something like this: if (client.getMyPlayer().isInArea(FARM_AREA)) { doSomthing .. . }

What's a girlfriend?

why am i a dog?

No, you'll pay for a renewal on an entirely new script if you want to use the OSBot 2 version, or you can continue using the OSBot 1 equivalents until support is dropped.

The CPU usage on OSBot 2 is comparable if not lower than OSBot 1 now (I believe).

Every available bot client is theoretically detectable, however the developers have implemented systems to prevent being detected, which may or may not be effective. If JaGeX could accurately detect the client there would be no bots (unless they want bots, which they may).

All OSBot 2 scripts will be monthly, so there will be no one time fee counterparts to monthly scripts (or so I've been told).

I love you.