Bot works most of the time, but lately success rates been really low and for some reason it keeps picking the highest ping world. Anyone know how to make it not pick high ping worlds?
The world hopping logic just pings each world once & selects a world based off that; So if the ping changes substantially it might not be the best. Might just want to set a world manually.
Beyond that I can only really recommend the general debugging:
- Try the "Recommend Settings Optimizations" button in the bot, and try to use some of it's advice if it seems useful.- Ensure your stats are reasonable for CG (the Wiki recommends 85+ Combat stats, 77 Prayer & Rigour/Augury. But I'd prioritize high Ranged (or Magic if using 5:1 & Staff priority), ideally high Prayer & Rigour/Augury, high HP/Def. Att/Str don't matter as much).
- It's recommended to use RuneLite with GPU plugin on (if possible) as it runs smoother.
- Disable essentially all other Runelite plugins, as many can interfere with the bot (you can make a separate profile on Runelite with your current plugins saved, for using when not botting). You may choose to keep some on like GPU (with default settings)/FPS/Worldhop/Loot.
- Keep DirectInput & Hopping Mouse on, and/or have Runemate's mouse speed set to 3x (in Runemate settings).
- Ensure reasonable FPS (30fps+), Ping (50ms-), and CPU/RAM usage aren't spiking too much. You may consider closing other programs.
- It's always possible it's a temporary Runemate or bot issue and you can try again later.
- If you're on Mac, a feature called "App Nap" may be reducing resources to windows that are not focused, and may require keeping Runemate as the active window.
- It may just be very bad luck.
It's also possible this is something I need to improve in a future update. Please enable "Benchmarking mode" (in the top left of the Progress Log tab), let the bot run a few attempts with it on & DM me a log (found in Help > View Logs) along with info on what the bot is doing wrong, what it should be doing instead, and what circumstances it seems to happen.
Feel free to test using the lite version of the bot so you don't get charged while testing. If the issue persists or this doesn't help, let CuppaJava know.
