MX Simulator

This one has a couple of new server commands (listtracks and settrack) and ignores socket errors. I couldn't reproduce the client quitting shuts down the server bug, but hopefully ignoring socket errors will fix that.

Unless you want to run your own server, you don't need this.

mxserver-2009-05-08.zip

i dont have any idea how to use this....

that arquive called mxserver...i have to put the name of the track their and???

like: mxserver alcrest.trackinfo
and after?????


i'm completely lost!

thanks all!

Mmmmm im neally there i think...
Could someone please fix up my codes for me? so it works. My IP is 192.160.10.0

thanks guys!

i have to dl this ???

Mikey wrote:Mmmmm im neally there i think...
Could someone please fix up my codes for me? so it works. My IP is 192.160.10.0

thanks guys!

Your IP address is 124.176.251.254

how do you know? i did what you said to run the code and it told me.

*EDiT* No lucas its my Server Info, you can use mine and just change it though i guess

Mikey, addresses ending in 0 are network addresses. So 192.160.10.0 would refer to an entire network, not one computer.

Unless you're running this on a dedicated server somewhere, chances are your router is doing Network Address Translation (NAT) for you. That's good because it lets multiple computers use one IP address. It's bad because to the outside world all the computers behind your router look like one computer. That prevents computers behind NAT from easily running servers since they aren't individually addressable from the outside. The workaround for this is to use Port Forwarding. This means you tell your router, if you get packets on port 19800, send them to the computer on lan address 192.168.1.5.

If you can't connect to your server from outside addresses, the things to check are:
- The router's firewall. Make sure your port isn't being blocked at the router.
- Port forwarding. Make sure your router is forwarding UDP packets on the port you're using to your server.
- Your server's firewall. Make sure your port isn't being blocked by a software firewall on your server.

ok so i 124.176.251.254, but i can not use port 19800 because thats your mxs servers. and i have you seen my codes and shit because they could be wrong.

Use port 19800. It won't conflict with my server since they are on different IP addresses.

Read my last post. You are almost certainly behind NAT and need to configure port forwarding and open up some ports on your firewall.

ok ill try that port, also is my folder, .txt and every correct because thier is a chance that is wrong.

jlv , if i want run a dedicated server. how i apply this list of comannds.
When connected to the server, you can sent it commands by chatting.
Currently the following commands are recognized:
server,listtracks
server,nexttrack
server,settrack <track number>
server,listplayers
server,kick <slot number>
server,ban <slot number> [minutes]
server,shutdown

and this " When connected to the server, you can sent it commands by chatting." , make me think anyone can take the control of the server? . i think the chat must take a functions of a real console . to allow login like admin. to take the remote contol of the server.

and what happend if whit this situattion, someone has a new track and want put in his server. obiusly he hasnt the file caled "xxxx.trackinfo", where he can make it or get it.

You can only use commands if you have the password for the server. The password is used by putting --password xxxxx in the same spot you would for --editor etc.

ok, i see its like rconpassword in FPS, thx for the info . and what about my question of the new released tracks.

Just start a normal race on his track, go into the chat thing, and type '/savetrackinfo'. This will save a .trackinfo file into your personal folder.

BTW, all these questions you have asked can be answered in the readme included with the server

arghhhhhhhhhhhhhhhhhh why wont it work

It goes "No Track Specified" when i run the Mxserver thing.