Messages

Afraid it kept running fine.

2 times the same installation / bot launched (The Jar file)

Do both bots have the same JTS3ServerMod_InstanceManager.cfg file (or at least the same content)?

Yes they were identical. 1 bot and 2x the same instance launched.

Afraid it kept running fine.

2 times the same installation / bot launched (The Jar file)

I will wait with the update till the server heartbeat should trigger. Actually slightly excited to see if it will do its job
:Dabout 3-4 hours to go and we'll know

Its not but you can shutdown bots faster that are not allowed to be run then.

Will keep you posted what happens. Currently 3 instances running.

An alternative way to make this faster might be to have it check each 2-3 hours. But if it cannot connect it can be delayed to a MAX of 12 hours. This way you get that shut down effect faster unless the connection is unavailble then it falls back to once every 12 hours.

Heartbeat worked.

Tried starting a second process and it worked. Guessing I found a bug here.
Going to start a third now to see what it does. (Worked fine) Il leave these 3 instances running to see if the system will step in at some point because of license violation.

Started from 1 install location (changes port after every start) It has no issue validating license and going on. Offcourse all from the same IP and Server.

Okay might wish to add that, further no comments about the info.

Thanks for the hint, I added it.

License worked instantly without issues. However I opened up the port 5873 but it still says no heartbeat received on license page. Any special port or so required?

This is normal in the first 12 hours. The bot tries to send a heartbeat every 12 hours. I added this information to the Licence Management page too.

Last question. No port required to be open for the heartbeat?

I'll let you know if I run into issues.

Okay might wish to add that, further no comments about the info.

License worked instantly without issues. However I opened up the port 5873 but it still says no heartbeat received on license page. Any special port or so required?

Besides that its all good on a Ubuntu 14.04 LTS server with PLESK 12.5 (for firewall management)

Maximum allowed JTS3ServerMod instances: 1

Does that stand for the instance running that we start by JAR file or the bots in the interface.
Will there be a limit on the bots in the future?

Regardless of your choice, don't release your new features. Get a new protection up and running, then release that to us, i'm sure most of us are willing to try and break it, crack it etc so we can help you find a good security system. Only then continue on features.

Pff disappointing to see people have been sharing this on such boards. Isn't there a way to protect it with a license key or so?

Possible to have a welcome message based upon channel?

Maybe a odd idea but my community would love this function.

A page that will generate a token for a certain server group. Basicly when someone registers on your website you could give them a link in the welcome mail our account page that will generate a token on the teamspeak to have someone become a different server group.