Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Buy OSRS Gold

Sell OSRS Gold

Posting a Proper Script Bug Report

Recommended Posts

Posting a proper bug report for a script isn't very self-explanatory and is quite ambiguous for many users, thus resulting in many bug reports to look something like this:

  • “script not working. please fix”
  • “so many bugs”
  • “getting stuck”
  • "script very slow! plx fix"


Although it’s quite understandable to not know what information would be useful in a bug report (You would generally need to be quite fluent with computers or know a bit of programming), reports like these generally do not help the script writer debug the problem in most cases. (By most, I would say over 90% of the time)


Script writers usually run through a series of tests before releasing their scripts. If the script is released without the tag BETA or Development, it would generally mean that they have fixed all problems and are not experiencing any problems with the script. It would be hard helping you without any information since the script was fine the last time they have ran it and would not know where to start.


This tutorial will help you provide the script writer as much information as possible to fix an issue with the script.


Why follow this as a guideline? 


If you post a bug report without sufficient information, this is how it would go:

  • You post report and wait for me to reply
  • I receive report, look over it and find out I have insufficient information. I tell you to post more information and wait for you to reply
  • You post more information and I will need to look over it again

This can go on for days.




Proper Bug Report Format


Step 1: Copy and Pasting Client and Bot Debug


This can be found near the bottom edge of the Tribotclient. Press shift and click to selectively choose which lines to copy from. It would be preferred to copy both debugs completely and indicate to the script writer the time the problem have occurred (e.g 2:25:32). This is almost ALWAYS necessary. Even if the client or bot debug is spamming the same line over and over, the interval at which the line is being spammed may help the script writer know indicate where the problem may have occurred.




Step 2: Screen Shot/GIF/Video


Depending on the issue, you can decide for yourself which is the most appropriate. Many script writers such as myself put the bot status on the paint which will tell us at which state is the problem occurring at.


Script writers know very well how their script works. What you see may not be what they see. I once had a user who refused a screenshot because he deemed it was useless because nothing was going on but proved to be a major part of what allowed me to debug the issue when he finally gave me a screenshot.


Step 3: Stack Trace


This is generally needed when a script is stuck. This will indicate exactly where the script is being stuck as and is very useful information.


It can be found here (Print Script Stack Trace): 




It will look something like this once pressed (It will be visible in the Client Debug):

[02:51:28] Script Stack Trace:[02:51:28]  java.lang.Thread.sleep(Native Method)[02:51:28]  org.tribot.api.General.sleep(yh:170)[02:51:28]  scripts.daxHunter.utils.trap.Action$2.active(Action.java:44)[02:51:28]  org.tribot.api.Timing.waitCondition(ko:50)[02:51:28]  scripts.daxHunter.utils.trap.Retrieve.twoTickLaying(Retrieve.java:138)[02:51:28]  scripts.daxHunter.utils.trap.Retrieve.actionOnTrap(Retrieve.java:65)[02:51:28]  scripts.daxHunter.managers.BotManager.bot(BotManager.java:189)[02:51:28]  scripts.daxHunter.Main.run(Main.java:110)[02:51:28]  java.lang.Thread.run(Thread.java:745)

Step 4: Description of Problem


Giving detailed information on the issue is also a crucial part in allowing the script writer to debug your issue. You should indicate what causes the problem and how often the problem occurs.


Step 5: Your Settings


Provide the settings and modes which you have ran the bot in. In most cases, it would be screenshot of your settings in the GUI.

Edited by daxmagex
  • Like 17

Share this post

Link to post
Share on other sites

Where do i psot my bug reports? I think it's needed to help for you as a script writer(s) fix issues faster and easyer. Sinc i ask stuff on skype, and get repaly best case after 12-24 hours after asking i feel like i should post them on forums in correct section, so scripters will have to fix them and will feel more responsible for fixing it...

Share this post

Link to post
Share on other sites

Where do i psot my bug reports? I think it's needed to help for you as a script writer(s) fix issues faster and easyer. Sinc i ask stuff on skype, and get repaly best case after 12-24 hours after asking i feel like i should post them on forums in correct section, so scripters will have to fix them and will feel more responsible for fixing it...


Post them on the thread of the script

Share this post

Link to post
Share on other sites

The bug im encountering:


- it missclicks the tiles so it places the traps on the wrong spot, not a huge deal but this should work flawlessly imo.


- the escape from pkers doesnt work for me, it just keeps eating food standing on the same spot till it dies.


here is a picture of the debug:




GUI settings:




Post it on his thread. :P

Edited by Flax
  • Like 1

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Our picks

    • To better support the upcoming changes (TRiBot X, new repository), we're switching our login handler to Auth0. Instead of logging in with the standard form, you'll now be required to login through our Auth0 application.

      All existing accounts which have been used within approximately the past year have been imported into Auth0 using the same email and password combination which has been stored on the forums.

      What does this mean for users?

      Your account credentials are now even more securely stored

      You'll be able to login via Facebook, Google, and others in the future

      Is there anything users have to do differently now?

      Existing users: You'll have to login with the standard login, open your Account Settings, then link your Auth0 account

      New users: You'll be redirected to our Auth0 app (auth.tribot.org) where you'll be able to create an account

      Why was this change made?

      The new apps we are creating (such as the new repository) aren't able to use the forums to handle user logins

      To centralize all user accounts in one area

      To ensure that the client login doesn't go down when the forums are having problems

      To speed up our development

      Other considerations

      There's no documentation or official support for using Invision Community combined with Auth0, so there are still a few kinks we're working out

      We're in the works of creating an account management panel specifically for Auth0 accounts (ETA August)

      It's not possible to change email addresses for the time being (this will be resolved this August)

      Changing passwords is a weird process for the time being. To change your password, you'll have to use the "Don't remember your password" tool on the Auth0 login page
        • Like
      • 8 replies
    • Over the past month, we've been working hard on TRiBot's new repository - a much needed update. This change has been deemed necessary for TRiBot X, and will allow us to really speed up development of all aspects of TRiBot.

      Today we are going to share what we've been working on!

      Now you must be wondering what kind of features the new repository will have.... well, you'll have to be patient for a little while longer. We're still figuring out various technical aspects so we can't provide answers to all possible questions. We're also focusing on development rather than writing about it so that everyone can get access to our latest developments at lightning speed. I will however answer a few users' questions.

      We're planning on a release of this early to mid August, giving users some goodies before TRiBot X's release.

      Thank you all for being patient. I hope everyone is excited as much as I am!
        • Like
      • 17 replies
    • Over the past few months, I’ve been working diligently on a new project - TRiBot X. Everything has been written from the ground up, with all of the best practices of software engineering. Every aspect of TRiBot has been re-imagined to support three main goals: flexibility, useability, and reliability.
        • Like
      • 50 replies
    • Come give us feedback on the next version of TRiBot!
        • Thanks
        • Like
      • 86 replies
    • TRiBot is looking to improve a lot of its customer relationship management, customer on boarding process, customer experience, design elements, community engagement and pretty much everything else you can imagine when it comes to marketing.

      Our goal: To ensure that the marketing done TRULY reflects the experience and does not shine an inaccurate light on what TRiBot is lacking in.

      So I ask, what do you love about TRiBot and what do you hate about TRiBot? What does O S Bot, Rune M8, PowR Bot and Dre amBot do better? (yes I purposely didn't spell it right 😂).


        • Like
      • 26 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Create New...