small idea, big win!

[Discoloda]

I had this idea the other night, each player has a list of maps they like. So if they can communicate this list to a server, the server can distribute it to other quake 2 servers. When a match ends it sends the clients to servers that are running the maps they like (if the next one is not in the client's list). A client with no list will not be able to tell the difference since they will not be pushed to other servers.

I don't know what server mod Tastyspleen uses, but I'm sure this can implemented on a few of them.

Amendment:
Because these servers know what maps are most popular with players, they can adjust the map list they run.

[UUD-40]

The old skool way seems easier. 

[WiFi_Man]

Having a per-player preference system in place could be useful in other ways, too.  For example, those of us who bound "use Phalanx" for xatrix could instruct the server to honor "use Railgun" properly, and likewise for ionripper and hyperblaster.  I'm sure there are other mods that could use it.  And, hey, here's a thought: configurable weapon auto-switch order.

As far as I know, DM and vanilla are running nearly stock Q2, however the auto-goto feature probably wouldn't be too hard to put into wallfly (note: I'm not volunteering).

The preferences could be put partially or wholly into cvars, or they could reference some sort of config database, in which case there would need to be some sort of secure user-ID or the like to prevent unauthorized modifications.  And while secure user-ID could be useful for other purposes, that would require either client modifications or use of an external program, at which point it'd be easier for many to just use a website... plus, a lot of players already have readonly configs where they can put stuff like

Code: [Select]

set mappref "mapname/minplayers/maxplayers mapname/minplayers/maxplayers ..." u
set ignoreservers "server server ..." u
set ignoremods "mod mod ..." uI'm not as well versed in Q2 server commands as I should be, but that should be fetchable without modifying the game DLL.

[reaper]

you can put an auto-exec in each mod folder, or bind a key to exec a certain config.  with these options im not sure there's any issue having a proper config while playing multiple mods, unless you were talking about something else.

the user specific map thing seems a bit much to me, if you don't like the map, how hard is typing goto

[WiFi_Man]

I'm not aware of any means for a client to control weapon auto-switching (like when you run out of ammo) or bind overloading (where using something again will cycle to another weapon), although the latter can be simulated with aliases or toggle.

The map preference system could be more than just auto-goto - as Discoloda said, servers could have maplists based on those playing.  It's not uncommon for a disliked map to cause half the players in a server to leave, and an arbitrary mymap by someone might not be any better.