Alek

This is so old.

Remove the first two lines, they are doing nothing at all.

Most programmers avoid order of operations by forcing parenthesis to ensure the order is correct. Typical mistake: bool1 || bool2 && bool3 Some people might think it's evaluating (bool1 || bool2) && bool3 when it's really bool1 || (bool2 && bool3).

How is this a community discussion?

if (ore.isVisible()) { if (!myPlayer().isAnimating() && !myPlayer().isMoving()) { ore.interact("Mine"); sleep(random(2100, 3800)); mouse.moveVerySlightly(); } } else { getCamera().toEntity(ore); } Redundant code that essentially does nothing. Default InteractionEvent makes camera movements, checks for object visibility, walks, etc. You will get the exact same results (except the interaction is performed faster) if you just do: if (!myPlayer().isAnimating() && !myPlayer().isMoving()) { ore.interact("Mine"); Also look into ConditionalSleep and replace your static sleeps: sleep(random(2100, 3800)); Additionally, your "random" sleeps aren't really all that random. It's some tinfoil nooby stuff, especially the small delays: return random(210, 320); You can keep the longer sleeps deviations, but the above is kind of pointless. if (oresMined > 200 + random(20, 100) && !myPlayer().isAnimating() && !myPlayer().isMoving()) { sleep(random(3100, 3800)); worlds.hop(hopWorlds[random(0, 9)]); } Not bad, but if you are on a dead world why would you want to hop to a potentially full world?

Watch how you play, then mimic that in your script. It's a repetitive task, there's not much you can do about it. I mean you could try adding misclicks, but that's still a bit "tinfoily" and probably won't yield any different results.

Maybe next dev build, the param will be called "norender" under "allow" flag (in case you want to get your custom loaders ready).

API Docs updated

Changelog: -Added Arceuus Spellbook -Patched norandoms throwing NPE when combined with -script param -Fixed issue with one-time Worlds initialization on first hop Edit: API Docs are updated (finally)

Ive never had OOM exceptions using web walker in my scripts; but the script writer already confirmed it's unrelated to web walking whatsoever.

Web walker doesn't create an array of positions; we wouldn't be able to do things like use gnome gliders and travel through the charters. Also no, those links aren't available in the public API. Everything is still under a bit of heavy development and I'd like to be able to modify classes without hearing the kicking and screaming.

Watching your posts over the last month or two, you spend a lot more time thinking about everything else besides making the script itself. Make the script and as you write it, you will know the path you need to take. Some scripts are small and are best suited for simple loop logic, other scripts benefit from Tasks/States. It almost sounds like you are going to university and you're trying to directly apply what you learned into programming. Start simple and expand from there.

Just FYI this method is going to probably break in 2 days.

You can do that right now with pretty much any version of OSBot.

You didn't do any research on this plugin. It has a bunch of reported bugs, it was made in 2013 and only has ~50 sales, most of the content on the product page is dead links.

Recently I fell in love with a game Runescape. This game is very fun, the picture is very fine, fine line, playing with very smooth, but also full of stimulation, is a very good game. The game is to make transactions via gold. Incidentally, I have a good site to purchase gold Runescape Gold, I usually buy on this site, affordable, fast delivery, trustworthy. And often do some activities, some of the sweepstakes promotions to players. (I've tried this, it is able to get props like!) Want to play junior partner to find play with me!

Have you tried both simple and advanced paths? Do they both still walk through the same area?

Give me the source and Ill write it myself.

My favorite thing about people who talk about nostalgia, are people who haven't played the game for 10+ years. Still can't believe people don't want 08 HD graphics.

Bank.open checks if the bank is open. So in reality he could just do: if(bank.open()) { //Banking Code } Also it's worth mentioning that you are using the Entity super class and you're missing out on some of the functionality. Instead try: RS2Object crate = objects.closest("Crate") if (crate != null) { crate.interact("Examine"); } and RS2Object bank = objects.closest("Bank"); if (bank != null) { bank.interact("Bank"); inventory.isFull(); <- This does nothing } Similarly for NPCs: NPC banker = npcs.closest("Banker"); So inside of your LOOK state: case LOOK: GroundItem knife = groundItems.closest("Knife"); sleep(random(500, 700)); log(" for a knife"); break; } Good job on using states. Final criticism though: Get rid of these randoms: random(200, 300); it does absolutely nothing for your bans. Instead "return 250;" is fine.

Would you mind clarifying the area a bit? Is it a quest area or instanced area? Something like this was planned for web walking, but there are a lot of other things I need to work on first.

"Uptext" is simply the first menu action. MenuAPI.

While we're at it we might as well rename our product to QuadBot.

It's a soft currency and PayPal has the API required to process transactions. Unless there is a vendor that takes bitcoin and exchanges it to a hard currency for us, and provides us the same functionality, it's unlikely. Also PayPal has a great reputation and has been up for many years.

Have your app send a session id to a client which starts OSBot through CLI, using the sessionid as a script parameter. Once started, the script will communicate with your server the session id. Once that's complete, your app now has control over the script. Put a loop in your script continually requesting commands from your server for that session. After that it's simple, write some basic switch statement for various commands such as buying, selling, etc.