Request: Alching on charged bracelets of ethereum
Description: Starting with some gold and nature rune in your inventory and have revenant ethers in your bank. Buying 26 uncharged bracelets of ethereum from grand exchange and charge each bracelet with 1 revenant ether. After 26 bracelets are charged it is now time for high alching all of them from your inventory and now profits are made and should go on repeat. If it possible to set max buying price for uncharged bracelets it would be great. Sorry for my bad English, I can record all the process and send it to you, to understand me more.
Please add me on Discord if you are willing to write this script for me. Thank you,
Payment Amount: $110 If all works fine.
Time: As soon as possible
By lets be friends
If you're using a local script, is there a way to run the script from within the same script if the script is ending? So basically if the script stops for some reason I want to rerun it. Sometimes the bot will fuck itself trying to dismiss a random (has been happening for like a year) so the script will stop. Would be nice if I could just automatically re-run it from the onEnd function or something so that as the script ends it also restarts itself. I could add other parameters so that it doesnt re-run when I don't want it to.
Do extra threads slow down the script by much?
Will having a concurrent thread that updates my database every 5 minutes or so and the rest of the time it will just sleep going to slow my script down? Or would it be better to start the thread when it needs to update and stop it when its done? and would that slow down the script noticeably?
Right now it will update every 5 minutes but it takes a few seconds to do it and I would rather get rid of that if I can. Also if the extra thread doesn't slow down the script at all it would be nice to chuck some other stuff in there to speed up the actual botting part. like getting prices or something.
hey, need help. im running two bots, bot after ~14 mins stops. running zulrah script. any thoughts?
[08:12:48] at java.security.AccessController.doPrivileged(Native Method) [08:12:48] at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source) [08:12:48] at java.awt.EventQueue.dispatchEvent(Unknown Source) something like that and after these lines bot automatically stops. to able run script again , i have to kill script instance.
This release will:
Fix Settings UI placement bug
Fix game object location bug
Fix small layout bug making the client shift up and down
Fix client crashing bug where loading the client with a small display area will cause the client to crash
Fix annoying Linux bug relating to painting events and peers
Fix settings saving bug where settings are saved to disk more often than they should
Fix RSInterface#isBeingDrawn bug affecting a limited amount of people
Drop Java 1.7 bytecode version for 1.8
Important: Since the downloadable RS client uses Java 7, it will no longer be compatible with Looking Glass. To make up for this, we will add support for using other clients such as RuneLite (at a later date).
This change was necessary to allow us to use Java 8 syntax. It also paves the way for Java 9/10/11 support.
Try our development release by checking "Development Release" on the TRiBot Loader. Note that these new features are currently in beta.
This release features:
Re-sizable mode support for both LG and the regular client
Slightly improved login bot
Removed final access modifiers from API classes
Added RSServer hook wrapper to get the client's cached list of server/world info
[NEW] Bug fix for intelligent banking
[NEW] Improvement to the stability of LG over time
[NEW] Vastly improved the reliability and speed of Screen#getColorAt on both LG and the regular client
[NEW] Fix LG login problems
[NEW] Fixed re-sizable mode container bug
[NEW] Fixed re-sizable mode mouse bug
[NEW] Use of public constants in the Banking API
[NEW] Use of other various constants such as Projection#NULL_PT and Screen#EMPTY_COLOR
More features to come very soon!
Please test it and let us know here if there are any new bugs introduced in this release.
Recently Browsing 0 members
No registered users viewing this page.