What would you like to see in UT2007?

[Nny]

I'd like to see utan disappear entirely. Personally I run into bots all the time. All utan really does is lump innocent people in with botters and ban everyone indiscriminantly. It's not worth the effort. I'd say abandon the project.

[Torinir]

UTAN is a ban management system. It's not an anticheat of any type. Get it straight, bro. There's a major difference.

[ShiningSquirrel]

Originally Posted by Nny

I'd like to see utan disappear entirely. Personally I run into bots all the time. All utan really does is lump innocent people in with botters and ban everyone indiscriminantly. It's not worth the effort. I'd say abandon the project.

Torinir is correct, UTAN does not ban anyone, server admins ban and use UTAN to manage their bans. It's really nothing more then an elobrate database when you get down to it.
Now, this is not the place to air your grievance about being banned. You where banned from a single server by a single admin, who could have banned you just as easily without UTAN, so the existance or UTAN made no differance to your ban what-so-ever.

[UnderDark]

Things that need to be added:

• True RCON abilites. As in being able to see chat, deaths, and logins, logouts. This would allow for admins to 'silently' admin a server w/out taking up a player slot.
• An ability to 'slay' people. This would be useful for team games when a teammate is constanly TKing, but you (as a lower-admin) don't have kick/ban privs

[AnnihilatorSC]

1) Ability to run as an (unprivileged) service under Windows. Nonservice server processes are antiquidated.

2) Separation of installation files and homedir files, just like in Unix. The server doesn't need to have write access to its install files, only to the ones that are mutable - in the "homedir".

3) Multithreaded server process: one thread for masterserver registration, accepting incoming connections, monitoring and serving the web interface, and another that actually runs the game itself. This is CRUCIAL so that when the game crashes (sadly, a frequent occurrence), the master thread can reinitialize the game more quickly (and with the appropriate map).

4) Secure (SSL) web interface which exposes all configurable server options. The admin should NEVER need to resort to editing the INI file manually, thereby needing to kill the server temporarily.

5) Special in-game administrative interface which allows the admin to perform all the functions he could via the web interface.

I probably thought of more, but can't recall it now.

[buttpirate]

How about instructions from the program writer on how to run a server?

[Azazel]

Originally Posted by AnnihilatorSC

2) Separation of installation files and homedir files, just like in Unix. The server doesn't need to have write access to its install files, only to the ones that are mutable - in the "homedir".

You can already do symbolic links in Windows 2000 onwards, its just hidden.
http://shell-shocked.org/article.php?id=284

[yahooadam]

Originally Posted by AnnihilatorSC

1) Ability to run as an (unprivileged) service under Windows. Nonservice server processes are antiquidated.

2) Separation of installation files and homedir files, just like in Unix. The server doesn't need to have write access to its install files, only to the ones that are mutable - in the "homedir".

3) Multithreaded server process: one thread for masterserver registration, accepting incoming connections, monitoring and serving the web interface, and another that actually runs the game itself. This is CRUCIAL so that when the game crashes (sadly, a frequent occurrence), the master thread can reinitialize the game more quickly (and with the appropriate map).

4) Secure (SSL) web interface which exposes all configurable server options. The admin should NEVER need to resort to editing the INI file manually, thereby needing to kill the server temporarily.

5) Special in-game administrative interface which allows the admin to perform all the functions he could via the web interface.

I probably thought of more, but can't recall it now.

Think you pretty much summed up my post there

The other thing that would be nice is an admin window, where it gives you a list of number (1-0) and then you cycle through the menus till you get where u want to be
(mani-admin (css) style menu (they call it amx style ..))
And every player should have a player id, allowing you to grant admin without having to login atall, if you on the admin list, your an admin

[Naked_Ape]

Originally Posted by Azazel

You can already do symbolic links in Windows 2000 onwards, its just hidden.
http://shell-shocked.org/article.php?id=284

I don't see that the ability to create links has much to do with it. The point is that UT2004 (and predecessors) require write access to files in the install directory (namely the INIs). You can work around it but only with an effort from the admin. Making it place the INIs in the user directory automatically fixes the access problem and removes the need to get creative with permissions in the install directory.

But thanks for pointing this feature in Windows out, I wasn't aware of it and have sworn long and hard over its absense...

[i4gMedic]

1. The ability to hook the login/connection process of players. This to have custom login/password per player.

2. A way to update the ServerPackages on the fly without having to do a server restart. (After all, maps can have their specific packages loaded on the fly.)

3. Server-side CPU usage optimizations. Less CPU means more concurrent servers/players on one box, more fun, and less costs. (Same applies to bandwidth.)

[Strider]

1. Effective anticheat (optional automatic updates would be a plus).

2. A team balance system based on players master server stats. Players win/loss records should be by far the most important factor.

3. Music files pushed to clients (making it a client side option would be a plus).

[vitto]

Ik agree with Rush. A simple (yet secure) login system like ssh would be truly wonderfull. A place where you could do anything text-based; restarting server, choosing map/mods, ... you name it.

This would allow third party software to create remote gui's for interface, irc-bots/php-website's to retrieve info, and probably more things I can't come up right now. Of course some user-access-level has to available too, like webadmin - so people can't get too abusive.

[elmuerte]

*cough*ungateway*cough*

[vitto]

ungateway only supports telnet as far as I know, that isn't the security level we want use :p

[Rush]

Originally Posted by vitto

ungateway only supports telnet as far as I know, that isn't the security level we want use :p

Read about stunnel. It can secure almost any tcp connection, for example I stunneled my webadmin so that it is available only via https.

[Azura]

I would like to see even more sexier female butts in UT2007 :p .

[elmuerte]

Originally Posted by vitto

ungateway only supports telnet as far as I know, that isn't the security level we want use :p

And IRC
But, yeah, no SSL or alike. It's a bit difficult and slow to do that in unrealscript
Besides, the webadmin only does basic authentication, which sends the passwords pretty much in plain text. On the other hand, MSIE doesn't properly implement digest authentication.

[StellarAshes]

Hmm I can't believe nobody mentioned this yet... The oh-so-fun Version Mismatch is one thing that I really hate. Am I the only one who tries to correct other's codes and run them on my server? (Dodgeball anybody? Don't tell me it's just the DoB_Mut, because there are things I like to change about it other than that--I've gotten ways around it w/o modifying the original file, but very annoying.) I also try to code my stuffs to put on my server, and I keep on having to change the name every time I do it. What I would like to see, as an admin + coder, is that when a version mismatch occurs, UT would download the version on the server and temporarily use that while on this server.

PS: I don't know if this is at all possible or if there are already solutions out.

[Azura]

Tbh, it's up to coders to be less lazy and rename any modifications they make on a package. There's currently a lot of version mismatches for a server logo on the original UT because admins didn't take the trouble to rename their logo.

[{HTC}bite-me]

web spectating spot lock with password for admins only with hidden join so know one knows if your there or not
and server names un able to repeat like player names so server names can not be copyed for copycat servers sorta ip lock on names or registard server names