Lord Apocalypse wrote:Best way to work rankings would be a hard number (ie actual wins) and a social ranking, say a 1-5 scale or 1-10 based on a few things. Was the player any good or did he/she win by attrition (sit back while better players bash each other into oblivion then stroll in and clean up the mess). Was the person a sore loser/ polite (can't think of something better) winner? And you could also apply if the player was a real jerk (includes those who rage quit) or kicks out any experienced player just to bash noobs all day (high wins low social). Its possible you could also track how many times a particular host kicks people out.
Side note: You coul stick with the above or continue with data collection. Number of wins per map, favored map or game configuration etc. Most of this could be collected when you click play or after the game is complete. Save all this is an SQL server (as well as private data such as IP address & provider) and to prevent multiple accounts, have the client send in the computers mac address.
SQL server? I think open source has moved on from that buggy thing.
It'd be much better to use a BSON server, or something like MongoDB.
SQL Server is a Microsoft product. (no comment on that). "An SQL server" is an member of the class of relational databases that speaks Structured Query Language (SQL). Examples are Oracle (a commercial product), MySQL, PostgreSQL and sqlite (open source offerings). NoSQL databases are becoming popular for applications where the relation model (think tables of stuff) is not a good fit, but relational databases are by no means dead.
