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

Fluffee

Administrator
  • Content Count

    3,881
  • Joined

  • Last visited

  • Days Won

    59
  • Feedback

    100%

Fluffee last won the day on December 3 2019

Fluffee had the most liked content!

Community Reputation

1,032 Excellent

About Fluffee

  • Rank
    Customer Support Lead

Personal

  • Sex
    Male

Recent Profile Visitors

17,903 profile views
  1. @Todd Is this a possibility? I feel like it was discussed before, but I don't remember offhand.
  2. Try switching your jar out from the TRiBot loader to the actual TRiBot jar. You can find that one in your .tribot/dependancies folder
  3. That would be my thought as well, as you do appear to have VIP on the forums @mel12 If that is the case, feel free to open a ticket on the helpdesk or shoot me a Discord message! I'm happy to help where I can
  4. Excellent glad to hear it worked! As for the other issue, is there anything being printed in the debug? I'm thinking an error message might be printed there. If there isn't, can you post the command you're trying to launch TRiBot with? Please remove any identifying information beforehand though
  5. I think I might know a solution to this. I did some googling of that error, and it looks like your issue is caused by a registry key that Java requires not being created, and being unable to be created. There's two options (I think) to fix this. One which is easier (but I'm not sure if it works) and another which is more work but I'm more confident in it. Method One Open a Command Prompt as an Administrator (right click, select "Run as Admin" or something similar) Run your cli command from that elevated command prompt. This should allow Java to create the required keys Method Two Go into your Start Menu and type regedit into the search field. Navigate to path HKEY_LOCAL_MACHINE\Software\JavaSoft If this path does not exist, try this path instead: HKEY_LOCAL_MACHINE\Software\WOW6432Node\JavaSoft Right click on the JavaSoft folder and click on New -> Key Name the new key Prefs and try your CLI command again. Sources https://stackoverflow.com/questions/23720446/java-could-not-open-create-prefs-error?lq=1 https://stackoverflow.com/questions/16428098/groovy-shell-warning-could-not-open-create-prefs-root-node
  6. Uninstall OpenJDK 11 and 8, instead install Oracle JDK 8, That should fix the issue
  7. That might be the issue, try downloading the .jar from the OSBuddy website (it's labelled as "Cross platform"). That should resolve the black screen issue
  8. It looks like Looking Glass isn't hooking correctly. Are you hooking to the OSBuddy.exe or the OSBuddy.jar?
  9. RuneLite changed the way their client loads, essentially adding some obfuscation to make it harder for others to reverse engineer (at least I believe that was the goal). However, this resulted in us no longer being able to hook to it.
  10. @4head123 Please use the bump button to bump your topics, do not post to bump.
  11. need credits add me back on discord 

  12. I believe both of those errors can be ignored! You should be good to go as long as the client loads
  13. Sadly, this is an issue with Jagex' servers. The best thing to do is to just leave the tab open in TRiBot, it should automatically retry and eventually load a client
  14. I'm not sure I've seen this error before, can you send a screenshot of the error you're receiving?
  15. Sadly, this is an issue with Jagex' servers. The best thing to do is to just leave the tab open in TRiBot, it should automatically retry and eventually load a client
×
×
  • Create New...