Welcome!

The below has worked for me in the past, not sure if this will help you. return gameObject.interact("Use", item.getDefinition().getName() + " -> " + objectName);

Not sure if I'm allowed to post web-urls outside of the community at my current rank, but there is a very popular rs-hacking development website that has instructions on getting familiar with creating updaters yourself.

Get that motivation up @awesome123man.

Join Developer Chat | RuneMate

If you get on the developer slack we may be able to help you a little better. Could have someone teamview you to assist.

Possible fix for the clay oven interaction: clayOven.interact("Use", "Raw monkfish -> Clay oven") Possible fix for the make all interaction: public void selectOption() { getOption("Make All").ifPresent(interfaceComponent -> { if (interfaceComponent.isVisible() &&...

You solved this already, but I'm just going to throw in my two cents as well. public void selectOption() { getOption("Make-X").ifPresent(interfaceComponent -> { if (interfaceComponent.isVisible() && interfaceComponent.click()) { Execution.delayUntil(() ->...

Currently no built-in check, a lot of edge-cases are involved with single-bot ban detection. If there was a global statistic for RuneMate, competitors could drive the number forcibly and subsequently destroy that statistic. A great idea, but people suck.