Welcome to TRiBot Forums

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

TacoManStan

[Quick Tutorial] The "Maximum Instances" Issue

10 posts in this topic

The "Maximum Instances" Issue - Explained

Ever get the following message when you try to start a script, or something similar?

FOz9jOs.png

From what I've seen, there isn't a single thread anywhere that is devoted entirely to explain why this happens. Sure, plenty of people explain how to fix it, but how many times has someone really taken the time to explain why it happens? Well, that's why I've made this thread. Instead of telling you to "just deal with it", I've decided to provide a bit of an explanation as to why it happens, and how to avoid it.

Explanation

While you are running a script, TRiBot continuously pings the server letting the server know a script is currently being run on your TRiBot account. This is how the Instance Manager works. When you stop the script or close the TRiBot client, TRiBot pings the server one last time to let the server know that the script is no longer running. Under normal circumstances, you can then immediately start up another (or the same) script.

However, if your TRiBot client is closed improperly (your computer crashed, TRiBot was terminated via Task Manager, etc), the server never receives the message indicating that the script has been stopped. As a result, you will see the infamous message shown above even when you don't even have TRiBot open anymore!

How to Solve It

This can obviously be incredibly frustrating. Luckily for you, you aren't out of options. If the server doesn't receive an "update ping" from the TRiBot client for 15 minutes, it will assume there was a problem, and automatically remove the instance from your Instance Manager. This means that if this ever happens to you, all you need to do is wait for 15 minutes for the instance to "time out" on the server, and you will be ready to start up another script once again!

Note: If you are VIP or VIP-E, you can instantly "Kill" an instance by using the Instance Manager mentioned above.

How to Prevent It

Especially because the solution to this problem oftentimes involves waiting for 15 minutes until you can do anything, the best solution to the problem is to prevent it entirely. While it is unfortunately true that the occasional computer crash is unavoidable, and that you sometimes have no choice but to use the Task Manager to terminate a frozen TRiBot client, you should avoid these situations whenever you can.

To help minimize the chances of unexpected "bad stuff" happening, make an effort to do the following:

  1. If you run your bots on a VPS, use the most stable and reliable VPS that you can find. Sometimes paying an extra dollar or 2 is worth avoiding the headache that constantly running into this problem can cause.
  2. If you run your bots on your own computer, ensure that you have enough RAM and CPU power to handle the number of bots that you are running. Just because "it's working right now" doesn't mean that it will stay that way. I would recommend staying below 80%-90% both CPU and RAM usage, and even less if you are using the computer for other things as well.
  3. Don't terminate TRiBot clients using the Task Manager unless you absolutely have to! While this oftentimes does work properly, as I have mentioned it above, it can also work very improperly. If you need to close a lot of clients at once, spend the extra 30 seconds to open each one and close the client as intended.
    Think of this like turning your computer off using the power button; it usually doesn't cause any problems, but it certainly can.

Conclusion

Well that's about all I have to say on this subject for the time being. If anyone has anything else they would like to add, just let me know, and if it isn't utter and complete nonsense, I will add it to this thread.

Good luck everyone, and happy botting!

Edited by TacoManStan
4 people like this

Share this post


Link to post
Share on other sites

This is an extremely common issue, thank you so much for posting a nice, clear tutorial on how to fix it! Will definitely be directing people to this in the future :)

Share this post


Link to post
Share on other sites

You're a straight up boss! I hope everyone understands how much you do for the Tribot community.

Share this post


Link to post
Share on other sites

This is very unfortunate. 

I am experiencing occasional lag spikes because of my shitty connection. Every time this happens I get this message and the script shuts off. This needs to be fixed.

The lack of interest from the management of Tribot amazes me.

Share this post


Link to post
Share on other sites
Just now, netgear said:

This is very unfortunate. 

I am experiencing occasional lag spikes because of my shitty connection. Every time this happens I get this message and the script shuts off. This needs to be fixed.

The lack of interest from the management of Tribot amazes me.

Read the thread again, and you will realize that there is nothing to "fix". The very purpose of the Instance Manager is to allow you to kill instances when you run into issues like the one you have just described.

Share this post


Link to post
Share on other sites
2 minutes ago, TacoManStan said:

Read the thread again, and you will realize that there is nothing to "fix". The very purpose of the Instance Manager is to allow you to kill instances when you run into issues like the one you have just described.

It requires you to have a very steady connection in order to not run into this problem. Instead of the bot retrying it shuts down completely, which is unfortunate. 

I have a paid VPN that runs into trouble with this system once or even twice every hour. 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.