ClickContinue not working?

[ArcticAlpha]

public class TalkToTask extends Task {

	private Script script;
	private String npcName;
	private String INTERACT_OPTION = "Talk-to";

	public TalkToTask(Script script, String npcName) {
		super((MethodProvider) script);

		this.script = script;
		this.npcName = npcName;
	}

	@Override
	public boolean canProcess() {
		api.log("[TalkToTask] " + npcName + " visible: " + api.npcs.closest(npcName).isVisible());

		return api.npcs.closest(npcName).isVisible();
	}

	@Override
	public void process() {
		api.log("[TalkToTask] Talking to " + npcName);

		NPC target = api.npcs.closest(npcName);
		if (target.interact(INTERACT_OPTION)) {
			do {
				api.dialogues.clickContinue();
				try {
					script.sleep(1000);
				} catch (Exception e) {
					e.printStackTrace();
				}
			} while (api.dialogues.isPendingContinuation());

			api.log("[TalkToTask] Finished dialogue.");
		}
	}

}

api.dialogues.clickContinue() is returning false, even when a dialogue is open and has the "Click here to continue" text.

 

Is there a condition that I am not satisfying in my code to have this execute properly?

[lisabe96]

The dialogues in tutorial island seem to be different from the normal game, you'll also find some info dialogues that wont be working with the default clickcontinue method.

You'll have to grab the widget and click it with mouse

 

eg:

getWidgets().containingText("Click here to continue");

Edited June 25, 2016 by lisabe96

[ArcticAlpha]

Thanks a ton. I will implement that.

PS: Thanks for the walker snippet that you put out! Been using it to great effect

[lisabe96]

Thanks a ton. I will implement that.

PS: Thanks for the walker snippet that you put out! Been using it to great effect

That must be outdated as hell

[ArcticAlpha]

That must be outdated as hell

 

Seems to work for the most part, although it doesn't appear to handle more than one obstacle in the path.

[lisabe96]

Seems to work for the most part, although it doesn't appear to handle more than one obstacle in the path.

 

It was a solution to the webwalker not handling obstacles yet, but since a while the webwalker handles pretty much everything (even boat trips) so there's no real reason to still use that snippet