NoxMerc

How come you don't use the Combat API -- getCombat().isFighting()?

Then...sleep until ClickToContinue is not null?

It's hard to go off your word alone when both Explv and myself have working TutIsland scripts relying on the notion of "Click to Continue", and you haven't given us the latest code that's producing the issues you're describing. public static RS2Widget getClickToContinueWidget(ScriptContext ctx) { return ctx.getWidgets() .getAll() .stream() .filter(f -> f.isVisible() && f.getMessage() != null && (f.getMessage().contains(TEXT_LOOKUP_CLICKHERETOCONTINUE) || f.getMessage().contains(TEXT_LOOKUP_CLICKTOCONTINUE))) .findFirst() .orElse(null); }

*Duplicate, sorry

Not sure what your issue is with a lack of code. You've been given an open-source example of a working script for clicking ClickToContinue. What's the latest code you have that's not working?

I'm wondering if you're storing vein in a variable that's out of sync with the game. Have you tried replacing vein with the retrieval code (e.g. getObjects().closest("vein"))?

The Gielinor Guide and all other Tutorial Island instructions widgets do not function correctly with the Dialogues API (unless we've both been attempting to use it incorrectly). You must implement your own method for continuation. You're also unnecessarily complicating your life with the widgets API. getWidgets().getWidgetContainingText(root, "Click here to continue") should suffice for you to get the single, visible widget containing that text. You might find Explv's open-source script helpful. https://github.com/Explv/Tutorial-Island/blob/master/src/sections/TutorialSection.java

Reading through Alek's post, one thing that bothers me is that he mentions that a fatigue system, among other things, is useless to implement in a script. To ensure we're talking about the same thing: I envision a fatigue system as something that gradually decreases the efficiency of a script as the play duration increases. Someone 30 minutes into mining is not going to be as efficient as someone 3 hours into mining. Moreover, nobody is 100% efficient for any meaningful duration. In other words, nobody is going to be able to always click the next rock spawn the instant it spawns for hours on end. The other methods he outlined -- mouse.moveRandomly(), stat hovering, camera.moveRandomly() -- I understand as being mildly silly. Along with a fatigue system I was going to attempt to randomly include a minor break system -- something that attempts to mimic the way humans naturally have distractions. Bathroom breaks, mom calling, whatever.. TL;DR: Nobody is 100% efficient for hours on end, and I would be surprised if efficiency isn't a factor in determining if an account is a bot. Why is fighting this useless?