Message Boards

Before it's too late, these should be...

Green
Indigo
Brown
Red

These should also be alterable through the server, to suit wads that already use other colors, such as those made for ZDaemon (which copied UT, which is cool but isn't DOOM), to allow designers more freedom in their wadmaking aesthetics, or in case it's already "too late" for some reason.

What seems interesting about Odamex is its commitment to being free software and sticking close to the PrBoom branch in general functionality (plus stuff like C/S, CTF and other online specifics). This thing about a standard is rather fallacious and pretentious, though.

There is no standard already because many map sets use features specific to ZDoom, Skulltag, both, or whatever.

Other level sets will not work on Odamex, but anything mapped for Odamex is going to have to be made also according to the other engine standards? I'm betting this will fail also already because Boom features and other engine quirks themselves are slightly different in the various engines, enough to alter any complex designs.

You should stick to something basic and solid without necessarily slaving everyone to the whims of the ZDaemon, Skulltag or ZDoom coders, who do not set standards but just follow their own designs.

People wanting their maps to work on all the engines will make the extra (and easy, in Odamex's case) effort just like anyone who sticks to a Doom or Boom format making a SP/Coop map. There is no need for engines to try to stick supposed standards onto designers, nor is it a good idea.

I can understand that, and don't think that they should want to have to redo the stuff. Neither is it unreasonable to consider keeping Red/Blue/Yellow/White as default colors due to the precedents. But, in addition to personally preferring classic colors (especially when thinking about designing levels), but seeing also that others might want to choose other colors for custom design purposes or even as a clan standard (like a shirt for a football team), getting rid of the arbitrary hardcoded colors for a system similar to the one for each player would not harm anything while it would make sense.

In addition to a default, settings like this one could be settable through the wad (in a file similar to ZDoom's MapInfo or to MBF's Options lumps), and/or through the server CFG. The Odamex wad would simply have two flag sprites, standing and carried, both green, and recolored according to the chosen team colors.

Also team names; I'd stick to R/B/Y/W if the default colors are set, Team 1, 2, 3, and 4 if nothing is set, and a custom name if all the players in the team share a team name, or if the name of each of the four teams is set on the server. This would enhance teamplay and CTF giving the chance for the teams to have proper (clan or whatever) names, which if not always stupidly end up in the user name, cluttering it and causing annoyances when people change teams. Instead of that it could optionally appear along with the user name (if something like show_teamname is set to 1).

getting rid of the arbitrary hardcoded colors for a system similar to the one for each player would not harm anything while it would make sense.

Actually, they're not hardcoded. I believe the team code (especially the CTF code) is really flexible, but the scoreboard is hardcoded. I could be wrong and I'm sure denis will pop in correcting me.

As for the other suggestions, they're nice ideas, throw them in the bug tracker as an enhancement.

After playing Sauerbraten endlessly, perhaps a team system like it's would be interesting, where teams are just like second player names, and everyone who's team string matches is on the same team.  For this to work with maps which are made with a specific number of flags, there would first need to be a team limit.  The server slots the flags to teams and sets the team limit to the number of flags available on the map.  Additionally, the server sets the team colors to the colors of the available flags.

Some system allowing teams to set the team color, and allowing a team to be locked would also be nice, but I'm having a hard time thinking of the best way of doing it where it couldn't be abused.  Anyway, this functionality isn't neccesary for things to work.