Navigation

Navigation section

Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

Sign up now!

StitchBurner

Overview Updates (13) Reviews (11) History Discussion
stitchorsuture

stitchorsuture

Joined
Nov 27, 2022
Messages
29
StitchOrSuture submitted a new resource:

StitchBurner - Trying to make free scripts

StitchBurner - Trying to make better free bots

What is Does:
-Burns all types of logs, up to and including magic, outside of east Falador bank.
-Will run in AFK mode or normal mode. Afk mode is to lower the chance of getting banned and plays like you are doing something else while burning.

Instructions:
Just start in east Falador bank.

Known Bugs:
-Cannot change...
Click to expand...

Read more about this resource...
 
Last edited by a moderator:
oldplay

oldplay

Joined
Feb 21, 2023
Messages
17
StitchOrSuture said:
StitchOrSuture updated StitchBurner with a new update entry:

StitchBurner v0.0.31 Released!



Read the rest of this update entry...
 
Still working on fixing it, I know it is a simple issue with the UI, but just trying to figure out exactly what is causing the bot to crash.
Click to expand...

Appreciate it bro, still crashing atm gets to starting bot 83% then unexpected error

I even tried logging in and starting the bot but still no issue. Is there any sort of logs I can send which can help
 
oldplay

oldplay

Joined
Feb 21, 2023
Messages
17
This is the last error code I got when trying to start it up
java.util.concurrent.ExecutionException: java.lang.NullPointerException: inputStream is null.
at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191)
at com.runemate.game.api.script.framework.core.BotPlatform.invokeAndWait(jw:214)
at nul.iiIIiIiiiiIiIi.iIiIiiiiIiIiIi(zt:301)
at nul.iiIIiIiiiiIiIi.initialize(zt:453)
at javafx.fxml.FXMLLoader.loadImpl(FXMLLoader.java:2655)
at javafx.fxml.FXMLLoader.loadImpl(FXMLLoader.java:2548)
at javafx.fxml.FXMLLoader.load(FXMLLoader.java:2516)
at nul.iiIIiiiiiiIIii.iiiIiiiiiIIiIi(pc:121)
at nul.iiIIiiiiiiIIii.iIiiIiiiiiIIii(pc:80)
at nul.iiIIiIiiiiIiIi.<init>(zt:538)
at nul.iiIIiIiiiiIiIi.<init>(zt:266)
at nul.IIIiiIiiiiIiII.IiIIiiiiIiiIII(uea:355)
at nul.iiIIiIiiiIiIII.iIiIIiiiiiIiii(sw:468)
at nul.IiiIiIiiiiiiII.iIiIIiiiiiIiii(ps:1323)
at nul.IiiIiIiiiiiiII.call(ps:1249)
at javafx.concurrent.Task$TaskCallable.call(Task.java:1426)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: java.lang.NullPointerException: inputStream is null.
at javafx.fxml.FXMLLoader.loadImpl(FXMLLoader.java:2562)
at javafx.fxml.FXMLLoader.load(FXMLLoader.java:2532)
at com.StitchOrSuture.scripts.StitchBurner.StitchBurner.botInterfaceProperty(rm.entrypoint:201)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
... 1 more
 
stitchorsuture

stitchorsuture

Joined
Nov 27, 2022
Messages
29
Waiting on the update to be approved. Script works fine on my IDE and so far when I test it in my Runemate client. The UI does not work once it goes to the bot store. Every time I try a new fix everything works for me and I cannot see that it is having problems until the update does through. Might still take some time until I figure out why there is this discrepancy with my stuff and the bot store or slowly pushing updates till I fix what is causing it.
 
oldplay

oldplay

Joined
Feb 21, 2023
Messages
17
StitchOrSuture said:
Waiting on the update to be approved. Script works fine on my IDE and so far when I test it in my Runemate client. The UI does not work once it goes to the bot store. Every time I try a new fix everything works for me and I cannot see that it is having problems until the update does through. Might still take some time until I figure out why there is this discrepancy with my stuff and the bot store or slowly pushing updates till I fix what is causing it.
Click to expand...
Thanks bro, I will keep updating you!

Really cant be asked with FM haha too much clicking for a macro recorder
 
stitchorsuture

stitchorsuture

Joined
Nov 27, 2022
Messages
29
StitchOrSuture updated StitchBurner with a new update entry:

StitchBurner v0.0.33 Released!

StitchBurner updated to v0.0.33.
Click to expand...

Read the rest of this update entry...
 
StitchOrSuture said:
StitchOrSuture updated StitchBurner with a new update entry:

StitchBurner v0.0.33 Released!



Read the rest of this update entry...
Click to expand...

This did not fix the issue. Another Attempt at fixing it is waiting on approval. Next update has a new method of loading the User Interface FXML file and added logging so that I can hopefully use the stack trace to finally get this fixed.

I will continue to try to fix this issue, since it is a roadblock in my way of creating better and better bots.
 
oldplay

oldplay

Joined
Feb 21, 2023
Messages
17
it doesnt crash now but just stands at fally east bank doing nothing, it doesnt have a UI to select logs does it?
 
stitchorsuture

stitchorsuture

Joined
Nov 27, 2022
Messages
29
oldplay said:
it doesnt crash now but just stands at fally east bank doing nothing, it doesnt have a UI to select logs does it?
Click to expand...

It does have a UI for selecting the log type, which is the only reason I added a UI to the bot. It currently will not work properly without the log selection from the UI. The same issue is still happening where the Bot is not loading the FXML resource. I am really hoping I just figured out the issue and that the next update will finally have the UI displaying. Next update probably would not be until tomorrow morning at the earliest, since that seems to be when they get approved.
 
stitchorsuture

stitchorsuture

Joined
Nov 27, 2022
Messages
29
oldplay

oldplay

Joined
Feb 21, 2023
Messages
17
thanks bro, yeah did 2/3 invents then crashed when I went to toilet so I didnt see what caused it

heres the error log:

java.lang.NullPointerException
at bot.IIiiiiiiIi.execute(f:32)
at com.runemate.game.api.script.framework.tree.TreeBot.onLoop(TreeBot.java:61)
at com.runemate.game.api.script.framework.LoopingBot.run(LoopingBot.java:80)
at com.runemate.game.api.script.framework.AbstractBot.start(vo:263)
at nul.iIIiiIiiiIiIiI.run(sha:452)

just some feedback :) mouse movement was quite slow lighting logs and would miss a few ticks, also banking was quite slow too standing in the middle of the bank before clicking on banker

well done though, keep moving forward and im sure you will keep improving.
 
stitchorsuture

stitchorsuture

Joined
Nov 27, 2022
Messages
29
oldplay said:
thanks bro, yeah did 2/3 invents then crashed when I went to toilet so I didnt see what caused it

heres the error log:

java.lang.NullPointerException
at bot.IIiiiiiiIi.execute(f:32)
at com.runemate.game.api.script.framework.tree.TreeBot.onLoop(TreeBot.java:61)
at com.runemate.game.api.script.framework.LoopingBot.run(LoopingBot.java:80)
at com.runemate.game.api.script.framework.AbstractBot.start(vo:263)
at nul.iIIiiIiiiIiIiI.run(sha:452)

just some feedback :) mouse movement was quite slow lighting logs and would miss a few ticks, also banking was quite slow too standing in the middle of the bank before clicking on banker

well done though, keep moving forward and im sure you will keep improving.
Click to expand...

Yeah I am adding some logging to allow me to see what caused the null pointer exception. I am also adding some try catch blocks, which might allow it to fix itself once something weird happens.

I might try adding some options for the user to control the clicking speed. The reason being is that I created the bot to play like someone who is afking the skill, while doing something else. So it is intentionally slow and also clicks randomly from about 1 - 3 seconds.
 
S

satanscreation

Joined
Jan 14, 2019
Messages
2
Runs great for me at points, but one thing is since it runs back to the same spot and if the logs haven't turned to ash the bot can't light the next fire and stops unless you manually do it
 
Top