LOGIN
User Name
Password
Remember me


Register...Forgot password?
Main menu
Leagues
Gonzaga
Blue Max
Cartagena
Wooden Ships...
King Me!
VampiRing
Forum Message
Previous messagePost on the new forumNext message

City:Corvallis US
Personal Data:Male,
HomePage or other cool site:http://www.youplay.it
Membership23years 206days ago.
Last Login5years 258days ago.
Last Move13years 209days ago.
webmaster is currently Offline!Send a mail to webmaster


Message header
Area/Game:General
Topic:General
Subject:Re: A question about ELO
Posted by: webmaster - 22years 246days ago.
Message text
von Trishoven wrote:
> You don't need random planes!
> (I like them, but you don't need them
> for this method to work)
> At the end of a match, add up the ratings of
> the players on each team, divide by the number
> of players on the team, to get the average
> rating and adjust by global scenario
> win/loss statistics

Bingo! that's exactly the solution we have in the ToDo list

The new statistics will be a squad matter. No more "I choose the best plane to win" because will be the squad which will be winning or losing.

As an addenda, FalconFab proposed to add a modifier per faction to each scenarios. This modifier is dynamic, and is automatically recalculated every time a game ended. This way if we should have an umbalanced scenario, after some games the automatically calculated modifier will rebalance it.
Actually this is just un idea not yet completely analized. We have to avoid that someone could abuse this parameter, for example losing several time in an already balanced scenario with a dummy username, and then creating a new game joining in the faction favorited by the new modifier.

This is the theory, but the final implementation is not so near. As for the automatic movement, we need to finish rewriting the site with a brand new engine (and with a new language, and a database engine) because the actual site is grown more than we could imagine when we started to program it, and now we are encountering some engine limits.

So currently we have 2 different project running. The first continue to implement new features to the current site engine, and the second is completely rewriting the site from scratch.
When the second will reach the first, we will be ready to put it online, but don't hold your breath in the meantime.

Have fun
Your WebMasters

Back to the messages list
Messages thread
Posting elapsed timePosted bySubject

22years 255days gugliandalf A question about ELO
22years 255days flying_neko Re: A question about ELO
22years 255days marcuza Re: A question about ELO
22years 255days flying_neko Re: A question about ELO
22years 254days ivanhawk Re: A question about ELO
22years 254days Falconfab Re: A question about ELO
22years 254days gugliandalf Re: A question about ELO
22years 253days duke68 Re: A question about ELO
22years 253days gugliandalf Re: A question about ELO
 22years 253days TnT Re: A question about ELO
22years 249days Pitch Re: A question about ELO
 22years 249days flying_neko Re: A question about ELO
  22years 249days Pitch Re: A question about ELO
   22years 248days flying_neko Re: A question about ELO
     22years 248days flying_neko Re: A question about ELO
     22years 242days Pitch Re: A question about ELO
     22years 246days webmaster Re: A question about ELO
     22years 246days Falconfab Re: A question about ELO
     22years 246days gugliandalf Re: A question about ELO
      22years 245days Falconfab Re: A question about ELO
     22years 242days Pitch Re: A question about ELO
      22years 242days Pitch Re: A question about ELO
        22years 242days Bramley Bomber Re: A question about ELO
          22years 242days Pitch Re: A question about ELO
            22years 241days Pitch Re: A question about ELO
Next thread
Posting elapsed timePosted bySubject

22years 241days flying_neko Re: double pilot kill
 22years 241days flying_neko Re: double pilot kill
22years 241days gugliandalf Re: double pilot kill
Previous thread
Posting elapsed timePosted bySubject

22years 241days kaesar Pb in game 35723
Page generated in: 28.90625 milliseconds.