Jump to content

liverare

Scripter II
  • Posts

    1300
  • Joined

  • Last visited

  • Days Won

    3
  • Feedback

    0%

Everything posted by liverare

  1. Sometimes, the bot won't interact with a RS2Widget until I hover over the RS2Widget. [edit] I've just faced this problem in the standard client. Here's the code: } else if (cookWidget != null && cookWidget.isVisible()) { if (cookWidget.interact("Cook All")) { ...
  2. I've written a private, local red chinchompa hunting script to train my hunting level. Whilst trailing this new script, I've encountered a strange problem that the standard client does not face: The mirror client takes longer to register changed objects. Scenario: Placing a box trap on an empty tile. Box trap is set up, but the tile is still defined as empty. Bot tries to place trap on the same tile. Seconds pass. Box trap is finally registered as up. Whilst speaking with FrostBug, he noted the problem could be the mirrored client, so I closed the mirror client and tested the script on the standard client. There's no delay on the standard client.
  3. You could try write a formal letter to Jagex HQ, pleading with them to release the ban. That's what I would do. I think it'll stroke their ego some if they get nicely written, begging letters like that, instead of what I believe is the common method of contacting the parental concerns (or whatever it's called) hotline and trying to claim 'your son wasn't botting.'
  4. java.lang.NullPointerException at org.osbot.rs07.api.util.DynamicCircularPathFinder.construct(wl:259) at org.osbot.rs07.api.util.DynamicCircularPathFinder.construct(wl:175) at org.osbot.rs07.api.util.DynamicCircularPathFinder.construct(wl:200) at org.osbot.rs07.event.WalkingEvent.createPath(ef:315) at org.osbot.rs07.event.WalkingEvent.execute(ef:54) at org.osbot.rs07.event.EventExecutor$2.run(eg:210) at org.osbot.rs07.event.EventExecutor.execute(eg:25) at org.osbot.rs07.script.MethodProvider.execute(tc:729) at org.osbot.rs07.api.LocalWalker.walk(ym:172) at com.liverare.better.utility.wrapper.context.preset.WalkerContext.walk(WalkerContext.java:162) at com.liverare.better.utility.wrapper.context.preset.WalkerContext.walk(WalkerContext.java:172) at com.liverare.better.utility.wrapper.context.preset.WalkerContext.traverse(WalkerContext.java:149) at com.liverare.better.scripts.law_crafter.tasks.craft.WalkToRuins.executor(WalkToRuins.java:29) at com.liverare.better.utility.wrapper.script.BetterScript.iterateThroughRegisteredTasks(BetterScript.java:182) at com.liverare.better.utility.wrapper.script.BetterScript.onLoop(BetterScript.java:42) at com.liverare.better.scripts.law_crafter.Main.onLoop(Main.java:64) at org.osbot.rs07.event.ScriptExecutor$InternalExecutor.run(dl:173) at java.lang.Thread.run(Unknown Source)
  5. Random paths, interaction patterns and breaks; sure. Auto-talking/responding (aka. Cleverbot). Lol nope. A poorly coded auto-talker/responder can get you banned because of how easily it can be abused by bot-busters. Implementing Cleverbot seems safe, but the fact is that if you say dumb and incoherent stuff, or if you can be made to sing along to the entire My Little Pony intro song, you're reported.
  6. Perhaps you should have read this. Even if it wasn't a delayed ban, but a genuine mirror-client ban, you're an idiot for not botting wisely.
  7. liverare

    Widget Bug

    Widget [X amount > "Enter amount:"] = Widget [548 > 119] Testing: #isVisible();Mirror client: In-game widget is valid : true In-game widget is not valid : true Normal client: In-game widget is valid : true In-game widget is not valid : false TL;DR #isVisible() and #isHidden() are both broken for the mirror client.
  8. liverare

    Error

    [ERROR][Bot #1][03/17 09:16:46 PM]: Error on random executor! java.lang.RuntimeException: Unknown query: 0x29D94400 at client.nat.stream.Stream.m16(Native Method) at client.KNApAkkyGbM.sq(Unknown Source) at client.emu.EmuClient.getLoginState(Unknown Source) at org.osbot.rs07.api.Client.getLoginStateValue(se:106) at org.osbot.rs07.api.Client.getLoginState(se:198) at org.osbot.rs07.randoms.BreakManager.shouldActivate(fd:140) at org.osbot.rs07.event.RandomExecutor.run(me:80) at java.lang.Thread.run(Unknown Source)
  9. It also doesn't say it won't run on Win95, but am I to assume it would? Win7 isn't supported yet, but I'm sure it will be in the future. Also: I took that quote from the same page you took yours, this is written one line above where your quote begins. This tool is still in its infant stages and has only just been made available to the public. This mirror client business is not a full product yet. EDIT: I just read that thread entirely and it does say that this 'unsupported OS' could be a bug and suggests we go here to fix it. Sorry my mistake.
  10. It's as though you're illiterate... The problem is that Windows 7 operating system is not yet supported.
  11. Win8 is supported, but Win7 is not. I'm facing this problem on my laptop and I would like it resolved, because I plan to mostly bot on my laptop.
  12. liverare

    Stuff...

    Shift, tab, and other keys aren't being passed through to the game. Please fix this. Can paint rendering be passed from the mirroring client to the client source? If so, that'd be useful since there's some debugs and trackers RSBuddy don't provide. Also, if the aforementioned can be done, is there any purpose for the mirror client view aside from aiding developers? Perhaps a small bot controller (similar to one found on most media players) could be displayed instead of the full client. Just a thought.
  13. [sHIFT] and [TAB] aren't passing through from mirrored client to source client. This is annoying when I try to manually login or attempt to respond to a PM. Please add this.
  14. Clarifications: Only NPCs are affected. Occurs irrespective of game regions loading. The bot client went black and stopped functioning. The browser client was still running, but I couldn't interact with it and the bot stopped running, too.
  15. Using the mirror client: Using regular client: HOWEVER when I reloaded the mirror client using Google Chrome (instead of Firefox), the entities became valid once more.
  16. Anti-ban = more processing, more 'feel-good', less actual performance and output. I won't be adding them--or if I do, it'll clearly be for the feel goods of the user. I personally believe anti-bans are redundant. Unless you've got an anti-ban that actually simulates human behaviour right to the extent where the bot will pick up an entire new task, or venture off somewhere to do something else, I doubt it's even worth it. Shaking your camera and flicking your tabs isn't going to stop players from reporting your ass, and I doubt it'll 'trick the system'.
  17. yeah I'm running 1.02.
  18. I'm not sure if this can be attributed to the mirror client, but when I run the mirror client and, whilst in-game, I travel across to another region (by foot) and the game loads the new terrain, shit just freezes. Completely. It sometimes happens. It may be the web browser, but it happens in Chrome and Firefox and I have the latest plugins and Java update. If it happens again I'll be sure to see if the logger spits anything out.
×
×
  • Create New...