ez11

That is a client issue where the Osbot client doesnt properly load your quests and gives my script the wrong information. Are you on mirrormode? Restarting your client usually fixes those Osbot client related issues. If that doesnt help and the issue keeps showing up even after restarting let me know and I will discuss this with one of the client developers.

Thats exactly what the next update should fix

It means im going to update my script and push the update to Osbots servers. The way updating official scripts works is that we scripters push our updates to the osbot server, but they first get checked by the script manager to make sure we dont upload any malicious code to protect users. Then after the script manager checks that our updates dont have any malicious code in them, he allows them onto the osbot server where you can actually see the update. I improved the walking part and that should fix the issue I introduced in the last update. You can see the update is live when the script version is 2.11 If you still have the issue when the scriptversion is 2.11 please send me a private message with all the settings you used and a screenshot of the client when the issue is happening.

I pushed an update to the script yesterday to improve something else and that probably caused the issue you notice now. As I said I will push an update for that later

Probably related to the last update, will push another update later to fix this

Jagex accidentally added a Tbow item spawn to the game once. They are just very bad at testing their updates lmao

Nice to hear the update to mapdata fixed that issue. Yeah those vampires in the are are annoying, added an hp check so the script eats if you are getting low during resetting aggro. Its gonna be in script version 2.10

They didnt do it to break bots. They made a new interface and had a typo in there. Their new content is often pretty bad in terms of those things.

What do you mean by that? They dont need to mess with your account to check if you are a bot or not if they want to manually ban you. They do manual bans at zulrah sometimes because its pretty obvious when an account is a zulrah farmer even if it doesnt get detected automatically.

Nice one

@MGI Client version: v5.9.192 (supposed to be 6.0?) Java version: java version "1.8.0_241" Java(TM) SE Runtime Environment (build 1.8.0_241-b07) Java HotSpot(TM) 64-Bit Server VM (build 25.241-b07, mixed mode) Opening trying to connect osbot to a runelite client crashes the runelite client after a few sec and produces the error seen below: [DEBUG][Bot #1][12/03 05:31:57 PM]: Initializing mirror client bot... [INFO][12/03 05:31:57 PM]: Started bot #1 Created temp copy of nattach_64.dll as C:\Users\Stefan\AppData\Local\Temp\wrwr3008764690954625013.dll Created temp copy of stream_64.dll as C:\Users\Stefan\AppData\Local\Temp\wee6853939873995132694.dll Created temp copy of stream_32.dll as C:\Users\Stefan\AppData\Local\Temp\qww1738742892720662449.dll Created temp copy of stream_64.dll as C:\Users\Stefan\AppData\Local\Temp\erre48495078837714222.dll java.io.IOException: VirtualAllocEx failed: ERR(5) at client.nat.nattach.WindowsVirtualMachine.M9(Native Method) at client.nat.nattach.WindowsVirtualMachine.srr(Unknown Source) at client.dB.km(Unknown Source) at client.dUK.vj(Unknown Source) at client.yr.lmd(Unknown Source) at client.uc.rqse(Unknown Source) at client.emu.Tm.run(Unknown Source) Running the newest 64bit Runelite client and following the instructions in the release post (moving runelite directory to desktop). Also tested having runelite installed in the default directory (users/appdata/local) aswell as installing runelite in the same directory as osbot (users) without success. I have seen multiple others with the same issue I have including multiple people in the release post. I talked with @Patrick who seems to have the exact same runelite/java version aswell has having runelite in the same directory as me and it works for him somehow.

nice

follow the instructions here: If it doesnt work please post a bug report here: https://osbot.org/forum/forum/316-bug-reports/ And give all the relevant info you can give and mention @MGI in your bug report so he sees that there is an issue and can fix it

Please post the logs

yes

Dont think so. Usually Osbot has sales around christmas.

yes

@MGIany updates on this? Cant get it to work and I dont seem to be alone. The live mirror version isnt 6.0, its 5.9.192

You should make yourself familiar with the forum before requesting git access. You dont need git access to write local scripts btw

webwalk changes pog

yes

Bump

ok

As far as I know some people bot a lot on accounts linked to the same 2fa so it shouldnt be an issue. But obviously no one will ever know for sure outside of jagex so why use 2fa for just a mule if thats a concern?

I checked the location where you get stuck and it seems like webwalk must think that there is a route through that area, im in contact with the dev for that. edit: we did some investigating and currently mirrormode for some reason tries to generate a path through an area that is not reachable, so this was send to the next dev who has access to change the webwalker code. As long as osbots mirrormode isnt updated I would suggest using the other swampcrabs area. I will mention you when its fixed @Fich420