Apaec

Hey, Sorry to hear you're having trouble getting the script up and running. Please could you open the console logger (via the settings gear at the top right of the OSBot client), and then try starting the script? The script will immediately stop if there is a configuration issue or if it is otherwise unable to continue, and the reason for stopping is always displayed in the console logger, so this should hopefully help you determine the issue. If I was to hazard a guess at what might be the problem, perhaps you have enabled ammo looting without the game configuration for auto-equip being set? If this is the case, it should display a warning message when you start the script; this warning should direct you to speak to the lumbridge guide to enable this feature. Please keep me updated with how you get on Apa

Sure- trial activated Apa

Sure - trial started!

Wow, 78k exp/h for 30 hours! Awesome gains Thanks for sharing (again!) Apa

Hey, Sorry for delay - i've been away over the weekend. Just started a trial on both scripts - enjoy Apa

Sure - trial started -Apa

Both trials activated Apologies for the delay in reply, I was away from home this weekend. Best Apa

Hey, Thanks for letting me know. I'm not sure why that might be; perhaps the interface details have changed in a game update. I'll check it out ASAP. Best Apa

Of course Trial started! Apa

Ofcourse; both trials started Apa

Hi troro, I'm sorry you feel this way. If I felt a complete rewrite of the code would prevent bans, then of course I would do that, however that simply isn't the case. The reason for this stems from the problem at hand: The goal is to emulate a human playing Runescape. Jagex have an entire team and 20+ years to dedicate to the comparatively simpler task of telling bots and humans apart, so naturally they have the upper hand. For this reason, rather than altogether avoiding detection (a task which, considering all variables, is next to impossible), the best approach is to 'bot under the radar'. As much as I don't like repeating myself, I am confident that my last reply summarises this well: I may have already pointed you to this resource, however this is a helpful summary of the topic by an ex-developer: https://osbot.org/forum/topic/124429-preventing-rs-botting-bans-v3/ Best Apa

Sure - trial started Apa

Thanks for the progress reports and the kind words Glad you are both getting good use out of the script! Apa

Hey, Sure - unfortunately the script doesn't support resizeable mode as I mentioned to dabswax, be sure to disable it before starting the script! I'll update the thread to mention this. Apa

Unfortunately not Progressive mode would be a big feature to add and would probably eat a weekend (incl. soak testing). I'm still trying to work out whether that kind of time would be better spent on other new features that benefit as many script users as possible. As a result, i'm not really able to give an ETA, or even a promise that progressive will see production, but it's still high up on the wishlist (I know I said that last time!). Wo - awesome progress once again; thanks for sharing!

Just an update on this. I've just tested the script and everything is working smoothly on Stealth Injection, so feel free to give that a go

I don't think there's any significant advantage of mirror mode over stealth injection wrt. bans, from my experience both are equally dangerous. With that said, it's slightly worrying that the script is not working for you. It might be that mirror mode is misbehaving - i'll run some tests this evening but ultimately would advise you to switch to stealth for superior reliability with all scripts. Apa

Hey, Please could you confirm some diagnostics for me? Are you using the resizeable game mode? The script may not behave correctly on resizeable mode - i'd recommend switching to fixed mode. Are you using mirror mode? The mirror mode debug text obscures the rune tiles, meaning the board reading system (which relies on co-ordinate colours) cannot function correctly. If you're using mirror, please switch off the debug text using SHIFT+F5. I'd recommend switching to stealth injection where this problem won't occur at all. If you haven't already, please give the 'things to consider before trying/buying' section of the thread a quick read (link: https://osbot.org/forum/topic/121795-apa-rune-sudoku/ ) I'm happy to extend the trial until the script performs as expected - it is likely that this could just be a configuration issue so hopefully we should get this sorted fairly quickly -Apa Sure - trial activated Apa

Sure - trial started Apa

Both trials activated Thanks for stopping by, -Apa

The rune prices fluctuate quite a lot, so i'm not sure how profitable the script is at the moment. With that said, I have so far avoided detection throughout my entire use of the script (incl. development process), so hopefully if you keep short sessions and a low profile, you should be fine. You're right though, this script solves the puzzles faster than most humans can do (unless the user has a cheat-sheet or the like), so it is worth being extra cautious.

Hey riddal, Apologies for the very late reply, for some reason I was unfollowed from the thread. Are you still having issues? I'm more than happy to help you get started with the script. You shouldn't have to create any files or the like, the script should 'just work' through the OSBot script starting interface. If you could provide me with a little more info on exactly which feature you are struggling to get set up, that would be very useful Best Apa

Hmm, it might be doing this if it's selected a spell, but the chest is ready to be plundered. This should be quite a rare occurrence, but might be more common if there is a high network latency or you are running in low CPU mode. Could this be the case? Apa

Sure - trial started -Apa

(I've copied my reply on the other thread for completeness):