lukulus: I didn't understand that at all.

And one more thing: In chess tournaments winner and players with same ammount of points as winner dont loose rating. So, in case BKR will be counted on the end of tournament (or section) this rule will be aplicable and higher rated players can play much more tournaments.

lukulus: Oops, I forgot write it is in Hyperbackgammon

lukulus: Funny! I just counted 192!

I would like mentioned when was BKR racalculated there were less than 15 people with BKR higher than 2100. Now there is 25 such players...

As evidenced by there being 400 players (about half) above 2000 in backgammon now, yet I'm at around 20th place with 2200.

In chess there is about 700 points between 10th and the player half way down.

This indicates that backgammon is indeed partly influenced by luck.

Hypergammon is even more bunched, considering the number of games played.

The rating system, while not the best, is not as bad as all that. Remember that the ratings have bunched up as a result of the luck in the game, and as such the expected winning %age between players of differing ratings should be accurate.

In other words if a player is still rated low with this system, they must be terrible indeed and you should lose points if they beat you.

alanback: Yes, I've begun to do that with some of my regular opponents - we even play 10 wins matches. (It would still be better with the cube and a decent rating system though )

pgt: I have a different solution to the ratings problem: play 3-wins matches. It would be good if we could hold tournaments of such matches.

Andersp: Well we have two of the four problems resolved, but until there is a more realistic rating system, people who chase ratings will clsuter at the top and play each other rather than risk losing a lot of points in a single game. But once this is fixed and the cube is implemented, ther will be a lot of very happy people, I know!

Andersp: Ah, I don't think that issue will go away!

redsales: I will miss the sportmanship discussion too, especially from those who dont play too low rated players fearing they should lose rating

thanks filip, working flawlessly now :)

i'll miss the sportsmanship discussion...but apparently, it is still an issue with bid fixing in ponds.

Fencer: Thankyou for this enhancement. I look forward to seeing a game in which it applies. This will save a lot of unnecessary discussion about poor sportsmanship and the like, I'm sure.

I've been known to introduce a new bug without fixing the old one ;-)

WhiteTower: You can classify me as one of those programmers.

I don't think I have ever introduced a new bug while fixing an old one. (Usually I introduce MANY new bugs while fixing an old one...)

Fabien Letouzey! Perhaps it surpasses the "King" Richard Lang.......

alanback: He sure is - who knows ONE perfect programmer who doesn't introduce a new bug fixing a old one? ;)

Fencer: Hats off to you, you must be quite a programmer!

Should be fixed.

Mine work as well. Thank you.

Fencer: ah! i checked for you but didnt see you online .. i guess you heard all our souls cry for help ;)

Whoah, real-time troubleshooting ;-)

Wait a minute.

Hrqls: i posted the bug in the bug tracker

i have another game with the same bug : http://brainking.com/nl/ShowGame?g=1084960

i want to move the 4 first, so i can bear off with the 6

alanback: I mean, he obviously worked in the shadows while we were all jeering at him, and now his surprise has come out slightly faulty :) SURELY his pride will not allow this issue to remain alive for much longer ;)

WhiteTower: I'm sure you're right :-)

UzzyLady: I believe Fencer will fix this relatively trivial bug [pointing and shaking index finger at Fencer!] as soon as he is made aware of it :)

I'm not sure which big one you are referring to, but I can't say the present situation is an improvement if the reports below are accurate.

alanback: I'll gladly suffer through the fixing of a few bugs, if it means we get the big one taken care of!

Not uncommon, but it needs to be fixed!

http://brainking.com/en/ShowGame?g=1090894&i=18

I wanted to swap the dice so I could take the 4 first, but there was no swap dice button.

http://brainking.com/en/ShowGame?g=1084875 and
http://brainking.com/en/ShowGame?g=1084875 are examples of the bearing off problems. In both cases I want to take the smaller die first so that I can start bearing off.

And of course, now that I'm looking for it, I can't find the other game I had a problem with. I'll keep searching.

UzzyLady: If you see them, post about it here - a link to the game, and what you want to do...... That way Fencer can see it and fix it.

UzzyLady: If it is as you describe it is definitely a bug.

BIG BAD WOLF: I've run into several situations where it won't let me use the smaller die first. These aren't games where I will only use one die, but want to move the smaller number first, to set up the larger number. In one case it didn't give me the option of swapping my dice. Is this a bug or have the rules changed?

Marfitalu: Looks like the system currently does not see that you can bear off chips soon, and in the process - trying to make you use both your dice.

Looks like Fencer will have to add the code of "if using the smaller dice leads to a point where you can start to bear pieces off the board, then allow it - otherwise ...."

AbigailII: It's in effect immediately even for running games. It would be too complicated to separate them.

Fencer: Ah, good. I presume that the new rule is in effect immediately even for running games? Or do running games keep using the old rules, which didn't enforce maximum die usage?

alanback: Right, I changed/fixed the model.

Fencer: Thank you, Fencer. I interpret this to say you have changed the software, not just the published rules?

I've just added these two points to the rules:

• If it is possible, both dice must be used. It means that some pieces can become "frozen" in certain positions because making a move with these pieces would create a situation where the second dice couldn't be used.
• If only one die can be used, the one with the higher number must be chosen.

Please let me know if it really works. I hope I've fixed this issue at last but I could easily overlook some special cases :-)

What is that "cube" and "bug" all about?

jolat: Indeed, there's no cube on this site. The reason is that it isn't implemented - a Fencer decision. ;-) At some, yet unknown, time in the future, a backgammon version with a cube will be implemented.

Some put a line on top of this page with the message that cubes will be implemented in the future.

I am new on this site and I would like to play backgammon but it seems to me that it is not possible to use the cube.
Is this well that?
If so, do you know why this possibility does not exist here?

I've no idea, but I hope so! Sounds like a very sensible tourney to me. ;-)

Brainking board's perhaps best for this as someone might have done it for a different game type.

It doesn't seem to be possible to create a tournament of multiple-point matches. That is, one in which each player would play the other a 3-point match, for example. Am I missing something?

And a good calculator once you get past airplane-cockpit syndrome, lol.

Javascript calaculation:
function afRatingChanges (fRatingP1, fRatingP2, uiExperienceP1, uiExperienceP2, uiMatchLength)
    {
    var fRatingDiff = Math.abs (fRatingP1 - fRatingP2);
    var fRootMatchLen = Math.sqrt (uiMatchLength);
    var fBasicMatchValue = 4 * fRootMatchLen;

    var fProbUnderdogWins = 1 / (1 + Math.pow (10, fRatingDiff * fRootMatchLen / 2000));

    if (fRatingP1 < fRatingP2)
{
     fProbWinsP1 = fProbUnderdogWins;
     fProbWinsP2 = 1 - fProbWinsP1;
     }
    else
   {
  fProbWinsP2 = fProbUnderdogWins;
    fProbWinsP1 = 1 - fProbWinsP2;
  }

    var fExperienceFactor1 = Math.max (1, 5 - (uiExperienceP1 + uiMatchLength) / 100); // Will be 1 when
    var fExperienceFactor2 = Math.max (1, 5 - (uiExperienceP2 + uiMatchLength) / 100); // Exp >= 400.

    var fRatingChange1W = fBasicMatchValue * fProbWinsP2 * fExperienceFactor1;
    var fRatingChange1L = fBasicMatchValue * fProbWinsP1 * fExperienceFactor1;
    var fRatingChange2W = fBasicMatchValue * fProbWinsP1 * fExperienceFactor2;
    var fRatingChange2L = fBasicMatchValue * fProbWinsP2 * fExperienceFactor2;

    return new Array (
       fRatingChange1W, fRatingChange1L,
      fRatingChange2W, fRatingChange2L);
    }