MX Simulator

+1 Well done sir. I will be using this. Player count is huge.

Is it player count currently, or last race?

Wahlamt wrote:Is it player count currently, or last race?

It is the last race player count. It is currently impossible to get a live count without the servers running some script posting the player count.

Actually really cool props to you

mx201 wrote:Actually really cool props to you

Thank you!

wow were is my credit...

broland278 wrote:wow were is my credit...

Its in the github lol

Ascaped wrote:

broland278 wrote:wow were is my credit...

Its in the github lol

who are you

Super cool, thanks!

Since this really isn't a connected application it would probably be a hassle to get current players since this seems to only be reading from the servers page.
If you could make remote calls to a server you could use to run "server, listplayers" every x seconds. Or maybe even use and , but in the documentation it says you can get disconnects without a connect if the players client fails to connect.

It may be a lot more work, but if you wanted to get server info in real-time you can write a service that runs on the server so you can make requests remotely to the IP addresses you already have from the server list and those requests can be executed from the service since it is localhost. Then the server info can be sent as JSON back to the server launcher. That may be too many requests to make depending on how many servers are "active" on the server list.
You'll have to take a look at the documentation for a complete list of functions you'd have to use in the production script. If nobody has any interest in writing an info service, I may give it a go if I have time.

LKR47 wrote:Super cool, thanks!

Since this really isn't a connected application it would probably be a hassle to get current players since this seems to only be reading from the servers page.
If you could make remote calls to a server you could use

Code: Select all

mxserver.schedule_command(commandline)

to run "server, listplayers" every x seconds. Or maybe even use

Code: Select all

mxserver.connect_handler(slotnumber)

and

Code: Select all

mxserver.disconnect_handler(slotnumber)

, but in the documentation it says you can get disconnects without a connect if the players client fails to connect.

It may be a lot more work, but if you wanted to get server info in real-time you can write a service that runs on the server so you can make requests remotely to the IP addresses you already have from the server list and those requests can be executed from the service since it is localhost. Then the server info can be sent as JSON back to the server launcher. That may be too many requests to make depending on how many servers are "active" on the server list.
You'll have to take a look at the documentation for a complete list of functions you'd have to use in the production script. If nobody has any interest in writing an info service, I may give it a go if I have time.

Do you know where that documentation is?

Ascaped wrote:Do you know where that documentation is?

It's in the latest server download in the JS folder. forum.mxsimulator.com/viewtopic.php?f=1&t=49636

LKR47 wrote:Super cool, thanks!

Since this really isn't a connected application it would probably be a hassle to get current players since this seems to only be reading from the servers page.
If you could make remote calls to a server you could use

Code: Select all

mxserver.schedule_command(commandline)

to run "server, listplayers" every x seconds. Or maybe even use

Code: Select all

mxserver.connect_handler(slotnumber)

and

Code: Select all

mxserver.disconnect_handler(slotnumber)

, but in the documentation it says you can get disconnects without a connect if the players client fails to connect.

It may be a lot more work, but if you wanted to get server info in real-time you can write a service that runs on the server so you can make requests remotely to the IP addresses you already have from the server list and those requests can be executed from the service since it is localhost. Then the server info can be sent as JSON back to the server launcher. That may be too many requests to make depending on how many servers are "active" on the server list.
You'll have to take a look at the documentation for a complete list of functions you'd have to use in the production script. If nobody has any interest in writing an info service, I may give it a go if I have time.

All great points, but the thing is he would still need the ability to run the service locally wherever the servers are actually hosted since all those calls require local access to the server just like xcommand does. I can't think of a way to request the info from a remote server without something already running locally listening for those calls.

Also, great job on the launcher Ascaped. Really cool stuff!

Hey man nice background pic for your program! Would of been cool to know you were using mine!

DP but nah i dont really care. Actually thought it was kinda cool that you used mine. Just giving you a hard time. <3