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

Sell OSRS Gold

Aropupu

Premium Scripter
  • Content Count

    4,026
  • Joined

  • Last visited

  • Days Won

    13
  • Feedback

    100%

Everything posted by Aropupu

  1. Maybe just maybe you should tell me a bit more information then. You still haven't even told me where you are using the script (wilderness maybe?). I also assume you are using v2. The option to stop script when out of food affects only when you are out of food in bank I believe. Can make it work to stop when out of food when banking is disabled. - Send me your settings. You can get your settings by going to your .tribot folder and opening aAgility2_settings file in notepad. Then just copypaste all the text inside it here. > In Tribot 11 you can go to Settings --> View local scripts and then going a few folders back from there to get to the folder.
  2. I tested it and the script doesn't spam home teleport when it's down. Something is most likely different on your end. Are you on a different spell book? Or did this issue happen for you in death's office? Could be something wrong with that too. Also, if your death spawn point is not in Lumbridge you should be able to completely avoid the issue if your death spawn point is in lumbridge. Can look into blindly adding a second failsafe for whatever caused your issue but without any more information from you (debugs, settings, etc.) I might not catch your issue. EDIT: I updated an additional failsafe to home teleport, hopefully this will fix your issue. To update the script in Tribot 11 either use the refresh scripts button or restart tribot completely.
  3. No, based on your account name you get a profile that generates antiban delays for your account. I believe most scripts do the same either through ABC or through custom methods.
  4. By default the script uses them always. You can reduce it by using that setting if you enable it. When not using them, it uses default reaction delays that aren't as long based on your generated profile.
  5. I believe you need to enable Developer mode in Tribot settings for it to appear.
  6. Thank you for providing more information. Was able to reproduce the issue with silver bars. I updated a fix in the latest version of the script. In Tribot 11 to update a script you need to use the refresh button or just restart tribot completely.
  7. Seems to be working without any issues. Please do give more information. What are you smelting? Also send me full client debug and bot debug information after the issue happens. You can copypaste both by right-clicking on their tab and clicking Copy to Clipboard: > If you don't see debug loggers in Tribot 11, you have to open them first. There's a button to open them in the upper right corner.
  8. You can use lastv3 to start the script with the last saved settings. Arguments for v3 can always be found in the first post.
  9. Check the first post for more information on v3
  10. Can look into adding it since new teleports are not a big deal to add in v3. The chronicle seems to be a special case though since it has limited use based on wiki.
  11. It seems like that's happening because of an error you have made in the Motherlode placeholder item settings (custom ID). You didn't provide your settings so I don't exactly know what the error is but you can reset your settings by deleting your aMiner2_settings file and that will fix the issue as long as you don't make the error again. EDIT: It appears that specific setting is actually not working correctly for some reason. You can disable the custom placeholders and that should solve the issue until I fix it. EDIT 2: Custom placeholders should be fixed in the latest version of the script. Thank you for providing the debug. To update scripts in Tribot 11, either use the refresh button or restart tribot completely
  12. v3 doesn't have that option yet EDIT: Added that and some other settings in the latest update to v3 (General --> Worldhopping)
  13. If by configs you mean settings, please do provide the settings you are having an issue with. If the script "crashes" it will print out a message or an error in the client debug or bot debug, please provide both. - Send the settings you are having an issue with (start script with the settings so they get saved). You can get your settings by going to your .tribot folder and opening aMiner2_settings file in notepad. Then just copypaste all the text inside it here. > In Tribot 11 you can go to Settings --> View local scripts and then going a few folders back from there to get to the folder. - Tell me about your setup. What Tribot version are you using? Are you using looking glass? If you are, what client are you using? Are you using the script in resizable mode or fixed mode? - Send me full client debug and bot debug information after the issue happens. You can copypaste both by right-clicking on their tab and clicking Copy to Clipboard: > If you don't see debug loggers in Tribot 11, you have to open them first. There's a button to open them in the upper right corner.
  14. Unfortunately the script is working without any issues. If you don't provide the information I ask for, I cannot know what your issue is. - Tell me about your setup. Are you using the script in resizable mode or fixed mode? - Send me full client debug and bot debug information after the issue happens. You can copypaste both by right-clicking on their tab and clicking Copy to Clipboard: > If you don't see debug loggers in Tribot 11, you have to open them first. There's a button to open them in the upper right corner.
  15. Send me your full recorded data by sending me your aAgility3_settings file. Easy way to do so is to open the setting file in notepad, pressing CTRL+A and copying all the text and sending it to me.
  16. If the script stops, it will tell why in the client debug or in some cases in the bot debug. You are not giving much information here for me to know what's wrong. Please do make a proper bug report. Instructions are below. Please make a proper bug report: - Send me your settings. You can get your settings by going to your .tribot folder and opening aMiner2_settings file in notepad. Then just copypaste all the text inside it here. You can get to your .tribot folder easily by going to File --> View local scripts folder in your tribot client and then going a few folders back from there. In Tribot 11 you can go to Settings --> View local scripts to get to the folder. - Tell me about your setup. What tribot version are you using? Are you using looking glass? If you are, what client are you using? Are you using the script in resizable mode or fixed mode? - Send me full client debug and bot debug information after the issue happens. You can copypaste both by doing the following:
  17. Don't know why you thought so but Dwarven mine doesn't support barbarian mine. Those are two completely different locations. Dwarven mine is the falador dungeon and it will always go mine there if you choose that as location. Again, please do provide a full bug report for V3 for me to take a look. In the debug it says you have enabled custom path to bank and custom path to mine. If you have custom paths or other custom settings, those might be causing issues if you set them up wrong or because of some bugs. I cannot help you because you are not providing your full settings. Also, most likely the error is hidden in the bot debug if you are using Tribot 11 EDIT: Found an issue with v3 that should be fixed now in the latest version of the script. If using Tribot 11, make sure to refresh your script so the script updates.
  18. Could you provide a bit more information? Are you using v2 or v3? Are you using a custom location? If the script stops, you should always provide full client debug and bot debug. Instructions for a proper bug report: The counter has nothing to do with how the script tracks if bag is full or not. The script doesn't rely on counting the gems because there's no way to detect gems that are already in the bag, it only detects if the bag is full once the bag is full. The counter is only a visual counter for the user. Are you using an opened bag or a closed bag? I assume an opened one. Can take a look at what's causing the paint to not count the gems.
  19. I don't have plans atm to add prifddinas. V3 works in similar way to v2 without any recorded data, just with some differences.
  20. You can change or hide the paint in the script GUI under paint settings.
  21. Some of Tribot's minimap methods are broken on resizable mode after the recent runescape update. Either change to fixed mode in runescape settings or wait for a fix from Tribot.
  22. Some of Tribot's minimap methods are broken on resizable mode after the recent runescape update. Either change to fixed mode in runescape settings or wait for a fix from Tribot.
  23. Please do make a proper bug report: - Send me your settings. You can get your settings by going to your .tribot folder and opening aMiner2_settings file in notepad. Then just copypaste all the text inside it here. You can get to your .tribot folder easily by going to File --> View local scripts folder in your tribot client and then going a few folders back from there. - Tell me about your setup. Are you using Tribot 10 or Tribot 11? Are you using looking glass? If you are, what client are you using? Are you using the script in resizable mode or fixed mode? Screenshot of your client when the issue is happening. - Send me full client debug and bot debug information after the issue happens. You can copypaste both by doing the following:
×
×
  • Create New...