-
Posts
3967 -
Joined
-
Last visited
-
Days Won
5 -
Feedback
100%
Everything posted by FrostBug
-
Was this with OSBot version 2.5.56? Additionally, can you reproduce in Stealth injection mode?
-
Try asking around in the mirror mode support section Might be. I somewhat doubt it prevents potting up, but I can't be sure. If someone could confirm I can add a check/faq entry about turning aid off It does.
-
You shouldn't have to worry about inventory layout; this is how the bot will attempt to order the items while running. Try checking all the troubleshooting steps from the OP, including hotkey configuration and duel ring Looks like something is off with the kill order; can you screenshot your kill order, or send me the profile you're using (profiles are located in the OSBot data folder) Script is currently not compatible with the beta version 2.5.56; please use stable version 2.5.53 until further notice
-
Should do it automatically when starting at the bank, if any hotkey is missing; will test and see if that function broke, though. Thanks
-
Unfortunately brews only. The consumable calculations heavily rely on the synergy between brews, restores and range pots. Alrighty. Be sure to use injection mode, not mirror. If need be you can quickly run tests on different setups in the tournament beta worlds
-
Have you checked all of the troubleshooting steps? Also, logs can still be found in the OSBot data directory after closing the client I haven't tested it in a while, but I did originally add salamander support. It will only apply magic buffs though, even when using non-magic styles.
-
This was recently added upon request. To do this, you must use the 'None' option in your kill order, and avoid using the 'Random' option; as Random may randomly select the brother you wish to ignore. I cannot recommend using this feature though, as it will heavily decrease your chance of receiving barrows items overall.
-
As requested, here's one from today
-
Just need to have every hotkey assigned; order doesn't matter. Reset to default if in doubt. Are you 100% sure the client mode is fixed? Even in resizable it can look like fixed mode if it's sized to the same size as fixed mode
-
Looks like "[ERROR][Bot #1][08/13 09:08:44 PM]: Inventory widget is null, trying to guess position." may be the cause of the problem. I asked the dev about it, and it would appear to be an issue in resizable client mode, potentially causing the script to be unable to interact with the inventory. Please ensure that: 1. You are running in fixed size graphics mode 2. All hotkeys have been set
-
For now you'll have to open the barrows chest manually to reset the barrows state. It needs one to be alive at script start to determine where the correct tomb is. But yeah let me know if the troubleshooting steps help
-
You can find the log files for previous runs in the OSBot data directory; I'd be interested in seeing one from where it stopped. Be sure that you've checked all the troubleshooting steps listed in the OP as well.
-
Sorry to hear it. If you tell me what happened I may be able to offer some advice. In case your latency is unusually high, it's best to disable prayer flicking.
-
Can you post a screenshot of it stuck? (Where / log / status)
-
Mirror mode is not supported in this script; so half of those attempts were invalid. Can't speak for the other half; not knowing what happened
-
Future<Integer> readval = client.read(buffer); String serverResponse = new String(buffer.array()).trim(); System.out.println("Received from server: " + serverResponse); readval.get(); You cannot read the serverResponse immediately after requesting the read. It's called Async for a reason, and returns a 'Future' for the very same reason. readval.get() will block until the read is completed, after which you may read the response. Not before. To properly utilize the async-aspect of it, you should get the response at some point after readval.isDone() is true, or better yet retrieve the response from a completionhandler by using the overload AsynchronousSocketChannel#read(ByteBuffer, Attachment, CompletionHandler). The completionhandler will execute once the result is ready.
-
Not sure what it is you've read (and not 100% sure what you're trying to achieve either) You can override OSBot API to the extent of creating classes that extend some API class and override certain public or protected methods. For example you might create a class called CustomWorlds which extends the Worlds class, and proceed to override the hopToP2PWorld method. This would allow you to create an instance of your CustomWorlds class and use it to hop to p2p worlds with your overridden implementation; however when using the MethodProvider to access the worlds API, you will still receive the instance of Worlds (not CustomWorlds) managed by the client. In turn, any other OSBot API that were to access the hopToP2PWorld method would not use your overridden variant either. EDIT: Actually, considering that all API fields in MethodProvider are public, you could set the worlds field, of the MethodProvider held by your Script instance, to an instance of your CustomWorlds class.
-
Break handler isn't really an API function, but a "Random Executor" (Group of event executors that are automatically triggered by some condition; like being logged out or in a random event). Some of these can be overridden with the RandomExecutor#overrideOSBotRandom method, providing a new implementation. The break manager can be overridden like this. For world hopping you can create your own methods that interact with the ingame world-switcher (See FrostHopper snippet for an example), but if you're looking for logged-out world switching, you'll have to disable the login-handler by using CLI, and provide your own custom login-handler that allows it.
-
Is there anything in the logger, and have you configured all hotkeys?
-
Broodoo shields aye; hadn't thought of those as degradable. I'll add them to the degradables list Log files are located next to the profiles; in the OSBot data directory. On windows this will typically be at C:\Users\{User}\OSBot\Data\FrostBarrows\Logs
-
Try to remove all your quickprayers before starting, and ensure that you have hotkeys for all tabs. Reason for logging out should be in the logger and in the log files Spoken with the client devs about this, and have learned that there is currently a security bug with the clients new skin. Doesn't happen for all users, and supposedly can be fixed for some by moving the OSBot launcher to your desktop. Try moving the OSBot jar to your desktop and launch it from there; or await a fix from the client devs. They are working on it
-
Ah, you mean make it do more than 1 chest before banking? There's a "Chests per trip" setting on the General tab
-
Check the logger
-
Looks like you're missing a hotkey binding for the equipment tab Works fine in mirror Can run it for a few hours right now and give you a proggy if you want EDIT: F, the run was cut short at 1½ hour because of the game update