Fluffee

You could use something like the Script Queue or nRestocker to accomplish this. However, it might be a little bit more complicated than you would've hoped

If there are any issues with it, let me know! It's possible newer operating systems may not work, as I haven't personally tried them? But I can't say for certain

Try disabling that, and see how it goes. If I had to guess, it's possible that CloudFlare is blocking/challenging the VPN IP which is preventing the client from running

Are you behind a VPN or proxy?

Would you be able to post a screenshot of the error you're receiving?

That was all very helpful, thank you! Sadly, I'm still not entirely sure what the issue is. Do you have Discord? If so, would you mind sending me a message there?

We currently do not have an installer that supports 32 bit operating systems. As such, in order to run the client using 32 bit you'll have to install a 32 bit version of Java 8 and then download the launcher using this link

Theoretically, JavaFX isn't required to run TRiBot. The loader uses JavaFX but the client doesn't, ergo if you used something like CLI to launch a client (bypassing the loader) you could get away with not running JavaFX at all. However, this will likely result in instability as so many scripts use JavaFX for their GUIs. It'd be functional, but limited to say the least

I know you mentioned you solved the issue, but when did that error message pop up? When you clicked "nNightmare Zone" to start the script?

There isn't an easy method, but if you open a ticket on the helpdesk I should be able to do that for you

I have a few questions, that should help me understand this a bit better Is this still an issue? If it is, are you behind a proxy or VPN? Is there anything being printed in the bot/client debug?

Looks like this might have it: https://github.com/xKylee/plugins-release

I'd love to say that this transition has been smooth and without issue, but well, as you've all seen that's not exactly the case. While I, and the rest of the TRiBot staff are confident that in the long term the transition to Auth0 will be worth it, at the moment it's definitely a little bit problematic. I really am sorry that this transition hasn't went as well as we had hoped, I can honestly say even I've tripped up a few times and tried to use my old credentials to login instead of the new Auth0 credentials. With that being said, the Auth0 system seems to be working for me now, so let's see what we can do to get it working for the rest of you as well. We definitely don't want to keep you out of your TRiBot accounts or prevent you from botting. I'm sure we'll have this sorted out in no time. One of the bigger changes to note with Auth0 is that you now have to use your email address (that being the email address which was associated with your TRiBot account on July 31, 2020) instead of your forums username. That means on both the forums and in the client you'll want to use your email address to login and not your username. So, the first thing to do is make sure that you're using your email address to login and not your username. With any luck, for some of you, that's a fix for the issue! But, if it's not (and I see some of you are already using your email address) stay with me, we'll see if we can figure this out. The next thing to try is to reset your Auth0 password. As I see some of you have already figured out, the reset password process has changed and, well, it's definitely less intuitive than it was. This was definitely not an intentional side effect of the Auth0 changes but it was a side effect nonetheless. To avoid copying and pasting (and I think the guide explains it well) please see the (updated) guide on our helpdesk on how to change your password. Now, with any luck you've managed to reset your password, it's now time to try logging in again! Hopefully, this time, the issues are resolved and you're back in your TRiBot account and back to botting. However, if not, the last resort is to open a helpdesk ticket. At this point I'm not entirely sure what the issue is so I'll need to manually look into your account to see what's going on. Trust me when I say I can definitely get you back into your account but I'm really sorry this has all taken so long. We definitely didn't expect so many hiccups with Auth0, but I promise in the future it'll be worth it.

What issue are you hitting when you try to login? Are you using your email address or your username?

Sadly, the transition definitely has an adjustment period which we're still working through. In the long term, it'll definitely be the right move, but I can understand the frustration in the interim. I know I personally have forgotten to use my email more than once and been confused when my login didn't work.