* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [2006-02-18 09:59:18]: > About user registration it would be a great addition provided that it is not > mandatory.
It can be either mandatory or optional, depending on what the admins of a community prefer. > About rating i don't know if it is desirable, IMHO it shouldn't be mandatory, > but it is in fact not a simple problem : As a quick reply: whether a game is rated or not depends entirely on the patch within the game server. If it registers a match (using a function in the API we provide), it appears in the rankings. If not, the FGS never even knows it existed. So, complex to-rank-or-not-to-rank algorithms are to be defined entirely in the specific FGS patch for a game. Now, concerning Wesnoth in particular... Currently, I seem to understand (I didn't dev the FGS patch for wesnoth) that the server is more a network hub than anything else, relaying data back and forth between clients. Aside from the problems this has on the cheating front, it also means that the server's options for making FGS-related decisions are more limited. However, as long as the server knows what game type is being started, it can decide how to rank it, no problem. > People like me, Roze, Elvish Pillager, Tomsik and various others do develop a > MP scenarios and from time to time some introduce a new kind of of MP game. > Some of them may become popular. > If rating is supported, it shall be flexible to rate differently different > kinds of games on the same server. I think it would be interesting to allow > the scenario maker to specify how the rating should work (so inside the > scenario itself). > Can FGS do things like that ? Like I said, all up to the game server. You can look upon the FGS backend and infrastructure as a fancy key/value database there. Some pairs concern players, some pairs concern games in progress or past games, and some concern the specific stuff of players within a game. We are trying to standardize some of the values, but the thing here is that if you have extra data that is specific to wesnoth, you can push it to the backend same as any other data. then it's the templates and specialized code for wesnoth that deals with those extra values as it sees fit. For instance, Wesnothd could export an extra ScenarioType key/value pair, that the templates would then use to separate Survival from MinDotW in the ranking and information display. Hopefully you get the idea. We're aiming for a very flexible system. Currently our portals list the same values for Wesnoth and Tetrinet, but that's because we lacked inspiration and time to make it otherwise before our first public event featuring the FGS. In future, wesnoth could have dozens of specific values and ranking/game info that tetrinet doesn't, and have a page that displays all that specialized info properly. - Dave.
