Would it be problem to implement possibility of limiting amount of players that can join your game? I think that now it's not a big problem, but in the future when more players will come it can be devastating for a host.

Good point indeed. Shouldn't be a problem to implement.

Not a problem.

I'd be also interested about what other rules or settings people might want to set when hosting a server.

- max rank you can choose when joining (0-7 or a rank you can choose from 0 to the rank of the host)

In addition to max starting rank, perhaps XP multiplier, so you can either get ranks quicker or slower depending on the setting. Even maybe have a max rank in general.

Maybe even have a setting for map rotation? So when a victory is won it goes to the next map.

Having a restart server option while the server is running would be nice too, or being able to change server settings while players are connected.

_________________
Ozymandias, King of kings, God of Caves, Wizard.

If we're discussing server features here, I'll add these to the list:

- Map rotation via configs
- Admin controls (ban, kick, maybe teleport) via password
- Server passwords
- Ability to change map rotation while server is running
- Ability to use custom weapon specifications (servers using them should be clearly marked in some way)
- Complete kill log for admins to catch teamkillers
- Speedhack detection and prevention maybe? (Not high priority right now)

That's all I can think of at the moment, some basic features.

Ah yes, it would also be nice if the kill massages for teammates was changed to "teamkilled" instead of "killed"

_________________
Ozymandias, King of kings, God of Caves, Wizard.

To summarize, in descending order of summed value of feasibility, time to implement and importance:

* Max initial rank, in Activate server menu
* Max player count slider, in Activate server menu
* User/Guest password, in Activate server menu
* Admin password, in Activate server menu
* Password field, in Join server menu
* Content package rotation list loaded from an XML file
- can be made to re-load for live changes
- biggest problem would be to deal with map loading times and the fact that the connection to the server is lost when everyone starts to load the next map.. Also, those clients, that load a new map faster than the server, will need to know to wait for the server to become active again, and know to just drop the whole thing if the server won't respond in a reasonable time
- when a client tries to join, validating the whole list that it's usable on the client seems pointless, if the list can change at any given time. The client will probably just check that if the current content package is ok to be used and then joins if it is, and at most just warns the player about conflicts with the upcoming packages in the rotation list on that particular moment. Then, if a conflicting package is taken into use on the server, the client can no longer stay in the game as it's unable to load the given package.

* In-game admin controls, ban, kick
- how to input these? Through chat bubble input as if they'd be commands, separated with a starter character from the usual chatting?
- a separate console? Console command handling will be anyway needed for controlling a dedicated server in a terminal

* XP multiplier, in Activate server menu
* Kill log
* Max rank, in Activate server menu
* In-game content package rotation manager UI, add,remove,shift up/down..

a quake-like dropdown console would be handy.