Page 1 of 1

Should I make an always on Server?

PostPosted: Sun Jan 15, 2012 23:38
by mrgasp
I downloaded Minetest and tried it out a bit, its a great idea, and i'd like to create a server.
However i am not completely sold on it... So, should i download the server, and create an always on server?

I have the hardware always on, a Tri-core system that sits at 10% usage, runs a MC server, and a few other servers... I'd add mods as i see fit, but at first it'd be blank.

Anyone Interested?

PostPosted: Mon Jan 16, 2012 02:44
by XCalibur54
Unless you have some sort of supercomputer, hosting several servers at the same time would result in lots of lag and crashing. But if you can somehow manage it, I'll try out your server.

PostPosted: Mon Jan 16, 2012 03:31
by mrgasp
It ran fine so far, for LAN access anyway, not sure if it is forwarded properly, I did it exactly the same as the other ports (that are responding correctly)... So yea, server will be up, join when you want.

IP: 50.53.21.166
Port: 30000

Let me know if it time outs, I have no clue why they can't detect these ports...


After doing a few more tests, i don't know what to conclude, but it'll need a client to try to connect... tried it on port 8123 (Dynmap for minecraft, port is detected by a port check), but when MineTest runs on that port, it gets refused....

PostPosted: Mon Jan 16, 2012 03:43
by jordan4ibanez
i timed out

PostPosted: Mon Jan 16, 2012 03:51
by mrgasp
And i am right in assuming the config line "Port = " is the port i want it to run on?

Edit: Try now, it wasn't set to port 30000 ....

PostPosted: Mon Jan 16, 2012 04:16
by mrgasp
So the server runs.....but the linux client doesn't load any textures. Windows client gets them, or rather never waits for them. I looked in my data directory and the client textures folder is pretty empty..

Edit: Works fine with the 3.1 Stable release, horrible with the unstable release =P