MVDSV

Finally \o/ :)

15:56 <@Renzo> I don't know proper way of adding it there
15:56 <@Renzo> perhaps made directory "configs"
15:56 <@Renzo> then add dir ktx there
15:56 <@Renzo> and then copy hmm
15:56 <@Renzo> 4 files
15:56 <@Renzo> make more directories
15:56 <@Renzo> copy more files
15:57 <@Renzo> make even more subdirs
15:57 <@Renzo> and copy files
15:57 <@Renzo> ...doesn't really sound good
15:57 <@Renzo> ktx+mvdsv consists of at least 5 separate big configs
15:57 <@Renzo> on top of that it requires configs for all usermodes
15:57 <@Renzo> so 1on1, 2on2, 3on3, 4on4, 10on10, ffa, matchless, whatever
15:57 <@Renzo> and they all are on their own dirs

KTX subdirectory contains:

ktx.cfg, listip.cfg, matchless.cfg, mvdsv.cfg, problem.cfg, pwd.cfg, server.cfg, and vip_ip.cfg.

Also it can/will contain configs for each port separately, in case you want per-port configuration for MOTD and QTV and whatever.

KTX/configs subdirectory contains:

reset.cfg, usermodes subdirectory that contains subdirectories for ffa, matchless and XonX modes. All of these subdirectories contain default.cfgs. Also mapcfgs can be found from ktx/configs.

So instead of 1MB server package, you want people to guess where each config go, in case they don't choose to use our server package and want to stir things up on their own from scratch? The current amount of configs with mapcfgs is 73.

I am not going to do this. If one big package that contains all is not enough and people can't get what they want from there, then it's their loss.

And change that maps.qw.nu to maps.qw-dev.net!

Sure, I can do that at some point.

The point of having it in SVN is not so that "people can get it from somewhere". Everything must be in SVN so that when you release next "full package", you know which version of those configs is the latest, you know that all changes that were proposed (like #178) were done to them and are already in the repository, you can watch the changes, you can see the changes, you simply have it under your control when it's in the repository. It's a common practice - "everything is commited in the repository".

I can have the serverpack configs unpacked and put to some directory but even so I have to remove some of the contents. At least this way it is the easiest and least time consuming and it also retains the dir structure.

Do not bother me about it anymore.

gg ;)