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

    • [CONTEST ANNOUNCEMENT] 2019 Botter's Choice Awards
      2019 Botter’s Choice Awards

      To celebrate the launch of our TRiBot Official RuneScape Bot Blog,

      we’re doing a giveaway! 

      The TRiBot Official RuneScape Bot Blog: 

      Teaching you how to do more advanced botting, faster.
      Contest Details

      Prize: 3 winners will be selected to win 25 TRiBot credits.

      How to enter:

      Respond to this forum post by November 12th tagging the thread for: 

      Your favorite script

      Provide a brief explanation (1-2 sentences) why you think that script should be put in the top 5. 

      Who can enter?

      Botter’s who are not currently scripters. Sorry scripters, the people are going to vote. Your contest is here.

      The top 5 in each category will be showcased on our TRiBot Official RuneScape Bot Blog in a “People’s Choice” section and promoted across the TRiBot website. 

      -- Credits will be awarded based on thoughtfulness and humor -- 

      Bonus points

      Use a meme in your explanation. Because we all love memes.

      *no purchase necessary. Winners will be announced on Friday, November 15, 2019 at 4:00 p.m. on our News and Announcements forum. 

      -- Vote Below -- 
        • Like
      • 28 replies

      I've noticed some new TRiBotters have had some troubles finding out sources of how to do certain things, such as using advanced scripts and often get lost in the forums.

      We are still getting posts asking where to start, what to do, recommended scripts, etc. 

      As many of you know, I am new to the team, and had troubles myself learning how to bot, let alone script. 

      So, what our team decided to do was make it easier to learn how to bot, how to script, and just become an overall better botter and scripter faster. 

      As some of you might have seen, I've posted 3 new blogs, you can check it out by clicking on the following picture or here.

      These first 3 blogs are the first of many blogs that will be TRiBot official. They are encouraged to be challenged, improved upon and act as A Best Practices Guide for Botters.

      What information would you like to see in the blogs?

      👇 [TEASER] 👇




      We are going to be hosting a  CONTEST  this  OCTOBER.

      Its scary to think how soon you'll find out.👻

      Stay tuned.

      - RileyZ
      • 8 replies
    • Today marks a big day for TRiBot! To make it easier for users to use TRiBot, we've created installers available for every platform! These installers are all bundled with the latest version of OpenJDK 1.8 (Java 😎, which is LG compatible.

      Using TRiBot is now easy. Simply download the installer for your platform, install TRiBot, and run it. The TRiBot Loader will correctly identify the bundled JDK so there's no need to change the Java selection.


      EXE installer: TRiBot-windows-x64-4.0.3.exe

      MSI installer: TRiBot-windows-x64-4.0.3.msi

      Portable version: TRiBot-windows-x64-4.0.3.zip

      Mac OS

      Installer: TRiBot-macos-4.0.3.dmg

      Portable version: TRiBot-macos-4.0.3.tgz


      Installer: TRiBot-unix-4.0.3.sh

      RPM installer (CentOS/Fedora): TRiBot-linux-4.0.3.rpm

      DEB installer (Debian): TRiBot-linux-4.0.3.deb

      Portable version: TRiBot-unix-4.0.3.tar.gz

      Platform Independent

      JAR file: tribot-loader-4.0.3.jar

      Note that this jar file does not include the bundled JDK.

      Windows and Mac OS users may notice a warning message stating that the installer/application is un-recognized or un-trusted. Please ignore this message and proceed with running the installer/application. We need to acquire a code signing certificate so that we can sign the installers letting the operating system know that these files can be trusted. It will take a week or more to acquire one, so please hold tight.

      Other notable changes to the TRiBot Loader:

      Support getting the version from OpenJDK distributions

      Add check for bundled JDK

      Copy OpenJDK tools.jar to the bundled JDK if not present

      Set the current java as the first available list entry

      Ignore Java versions which are symbolic links

      Make the bundled JDK the preferred Java version

      Update icon images

      Reduce the number of HTTP calls
        • Thanks
        • Like
      • 32 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
      • 18 replies
    • Hello TRiBot,

      Today we have a significant release that has been in the works for the last month addressing several key issues, features and bugs in the backlog.

      With these changes, we are also including a new TRiBot Loader which will allow you to select any version that is released. This adds the flexibility of allowing you to revert to a previous version should an issue arise, run development only builds, view an accurate change log between versions etc. we are very proud to offer this feature and think it will add a lot more functionality down the road as we continue to release new versions.

      These changes include 80+ commits by our development team, a list of them is summarized below and also available for your viewing pleasure in the new TRiBot Loader.

      In addition, we have taken additional steps to improve as a development team by adding continuous integration and deployment into our workflow to assist in delivering timely releases such as bug fixes as well as new features on a weekly basis depending on our development cycle.
        • Thanks
        • Like
      • 39 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Create New...