Gunman
Super Moderator
-
Joined
-
Last visited
Everything posted by Gunman
-
Using none binds it works but might take a couple tries. Related to the flashing, tut scripts have manual work around for this. -
Need to post your discord name too
-
Need to provide your discord UID
-
@moeezshahid11 Pretty sure it's broken on Linux, you'd have to use a Windows VM (When I tried Wine it didn't work out the box, you may be able to get it to work)
-
Assuming you have a Jagex account. Use Patcher, launch with account beta in boot, mirror if the legacy client still works rn, or through manager with manager lite
-
Finally my back ordered hooks from Christmas are here
-
Why not ask for a trial on their threads and try them for your self?
-
Need to post your discord UID too
-
Need to post your discord UID too ?
-
I don't think anything will change besides them blocking the legacy client's Java platform foot print tbh
-
They've made posts about this before
-
Use the patcher and click unpatch
-
Need your discord UID too
-
-
Try a different browser
-
Np
-
Please note global OSBot T.O.S. always apply in addition to this one, and personal T.O.S. can be declared obsolete at a moderators discretion. OSBot Rules Market Rules
-
@CoffeeNow Might be your language level. You are compiling with a higher level than the Java you run the client with. If on Intellij Project Structure -> Project -> Change language level to 8 -> apply and recompile
-
None, the author took the script off the store. Think he was gonna do something idk though
-
Yes. But none of that matters if some funky business is going on causing the wrong java version to be used
-
Legacy version only. You can manually point to the java version and run it directly from command prompt. "path_to_java/java" -jar "path_to_osbot/osbot 2.7.40.jar"
-
If it's greyed out then you're not launching it with the Java version you think you are
-
Looks like it was removed from the store, idk it's current status
-
Need to post your name too
-
Bump Jagex tuts in stock
