Author Topic: Connecting a client to another server?  (Read 3399 times)

With dedis you just set it in the advanced options, close it then host a dedi and it should adapt to it.

You could use an external program to modify the config/server/prefs.cs file to work with x port before launching the server. I did this with Java to set the port to 28000, launch, wait ten seconds, set it to 29000, etc etc for four servers and it worked fine.

You could use an external program to modify the config/server/prefs.cs file to work with x port before launching the server. I did this with Java to set the port to 28000, launch, wait ten seconds, set it to 29000, etc etc for four servers and it worked fine.
Yeah that's what I was thinking because it'd be a bitch if the computer crashed or something and you'd have to keep manually doing it.

You could use an external program to modify the config/server/prefs.cs file to work with x port before launching the server. I did this with Java to set the port to 28000, launch, wait ten seconds, set it to 29000, etc etc for four servers and it worked fine.

If I knew the C++ functions to start programs, and File I/O, I'd be able to do this, but I don't.

Edit: Ok still, this isn't my problem, does anyone have any idea about what functions to use?
« Last Edit: November 28, 2009, 06:32:48 PM by Zenthos »

What will different ports do?

What will different ports do?

To make it simple, ports are pretty much slots for incoming connections. Blockland used to use 28000-28030, because that's 31 slots - designed for 32 players with one being the host (at least that's what I've been informed of). I'm not sure if it's because of new router technology or Blockland does it for you, but you only need to forward 28000 now. So, by setting it to, say, 29000, Blockland can also accept connections in those slots.

If you tried running two servers on the same range of ports, it won't work because those slots are already being used.