0 carbon

When a hand is over, why not show the maximum contract for each declarer like they do at in-person tourneys, eg: Makeable : N:2D3S S:2D3S E:4C6HlN W:4C5HlN

Could you please post a link to the Mac executable & source? ty, tOM

Private clubs cannot currently manage their members. Administrators should be able to: - add or delete members - discover when a member joined or left - put a member on hold for a set period - see what club tourneys a member played in and their results Also, administrators should not be logged out, losing all the tourneys they created, when another admin logs on the same ID. tOM BBO Fans TD

The only way to load hands to a tourney now is to use the obsolete Windows client after generating the hands in LIN format. The only way to generate LIN hands for goulash now is an obsolete polish 16-bit DOS program. The only way to generate practice hands is to manually construct them. The DEAL program can be used now to generate hands for practice. Why not for tourneys too? This would support generating goulash hands and practice hands for teaching tourneys. tOM

To generate hands for bidding practice, you can use the Deal script at http://tomtrottier.com/Goulash.html#DealSource

If not TCR%, then just allow them to play - unless very new.

In tournaments, the description is always blank. Why have it? Tournament directors would appreciate more info in the table list: ♣ Board number would show which tables are furthest behind for urging or adjustment. ♣ Waiting/Playing/Bidding status would allow substitutions from the table list while bidding. In play, TDs should really adjust, then sub, since subs don't see past tricks. (It would be nice if they could, but it would show play ♣ Show the round clock for each table. This would mainly help kibitzers choosing what to watch. tOM

I'd suggest that a list of restrictions should be processed in order, inclusions, then "inclusion only if", then exclusions. If a player is included then they play. If they are excluded, then they are not allowed If they satisfy an "Only", then they are processed further This would imply changing the list of restrictions to read: Include friends of Host Include custom list(s) Only language of Host Only country of Host Only player level X+ or X- (ie, all >= or <= a particular level) Only BBO Masterpoints X+ or X- Only ACBL Masterpoints X+ or X- No enemies of Host(s) Minimum logins N None on these list(s): ... Minimum Completion rate % tOM

How do you do this in the browser/flash version?

As well as m (eg 2m) for minors and M for majors, would be a good short form to have an abbreviation for a suit bid (vs NT) eg "T" (for tie, as suits should be worn with ties....)

In browser, all TD calls show up.

Currently tables show: Matchpoint/IMP, round x of y, and decreasing round clock. It would be helpful to also show: hand x of y Pair/Team/Individual Clocked/Unclocked/Swiss/Survivor Tourney description (1st 12 characters or so) This is helpful for everyone and especially for subs.

One problem with tourneys is slow players. TDs need a way to establish which players are slow, so they can be messaged or sanctioned. Slow players either make other players wait(unclocked tourneys) or result in AVE(clocked) boards which are unfair and sometimes necessitate TD assessment and adjustment. One way would be to have a timer for each player for the tourney showing the average time taken per board, perhaps showing in the player's profile., either for the current tourney, and perhaps for all tourneys. Another would be to have a timer for each player in their name bar at the table which counts the time each player has taken in the current hand. This would have the advantage of showing players how slow they are compared to others, and if players call the TD for slowness, the TD can see. If the totals were kept with the player's name for each hand in the hand display for each Result, this could be reviewed by TDs later if requested. I suggest the format mm:ss, max 99:59, tho 99 seems unlikely.... I understand this would lengthen the name bar, but there is room! In fact, it should be lengthened, because the red point circle sometimes obscures long names. While most useful in tournaments, this could also be shown in all matches, to give feedback to all players on how fast or slow they are. It could even be used to give AVE+ or AVE- to the slowest pair in a timed-out board. tOM

It would aid TDs if there were a count-up timer in red players' title bar showing how long since communication dropped. Then TDs could allow a minute for reconnections. It would also help if TDs got a beep and auto-call when red time exceeded a certain threshold, eg, 1 min. It should autocancel if the player returns. However, if there a plethora of reds,then perhaps increase the wait time with each extra red player.

I TD using the web interface. 1. Report Tournament Status by board, not by round, to aid speeding up slow tables by chat or adjustment. Yes, this means longer status messages... 2. Fix score display of Swiss Tournaments to We and They not NS and EW - pairs switch directions, and "My Results" is inaccurate in 2nd+ rounds, 3. "Missing" message is very slow to update properly. It would be nice if it were not many seconds out of date. At least make it disappear after replacing a Red. It would be nice to have a beep, too, a different timbre from the TD Call. You may want a delay before recognizing new Reds since some connection problems clear up quickly. 4. Recognize non-breaking spaces in the "Welcome" field instead of deleting them. Is this a Unicode field? 5. Report survivor % in the "more" of a tourney. 6. Report required completion rate in the "more" of a tourney. 7. Report the number of rounds in the "more" of a tourney. 8. Allow TD to choose kibbing to open automatically: "Allow when fastest table is finished" (without any message to players)

As well as the obvious effects (desertification, flooding), we have to worry about the death of 99.99% of organisms in a couple of centuries. And we may have passed the tipping point already. http://journalstar.com/news/opinion/editorial/columnists/gwynne-dyer-how-bad-could-global-warming-get/article_670c924c-b25e-59aa-9276-87d381c51c2e.html

Currently Tournament Status reports by round, not by board. This makes it more difficult to speed up slow tables by chat or by adjustment whenever the rounds are more than one deal. Please change so that it reports by board, not by round. tOM

I have set the Survivor Cut % to 24%, Logically, this should leave 4 pairs at the end, 2 tables, since with 5+ pairs 1+ will be eliminated. Instead, I have 7 tables left - 28 pairs for the last 8 rounds of the tourney, with no one cut. Howcome? tOM

How about an FD card for GIB rules?

Ah, when I change tourney to INDy, it changed Survivor to Swiss....

Why does GIB have to always be explicitly called? Why not display best possible double dummy results for all finished hands for everyone? Then use GIB only to explore lines or partial positions.

I think it would be advantageous in clocked tourneys if the software could count the time spent by each pair to help determine slow play, and award Avg+ to the pair taking the lesser time and Avg- to the pair taking more time.

When I ran a 10% Individual Survivor, everyone survived to the last round!

Where is the complete list of Dealer commands?

A Goulash script - you can use pieces for other kinds of bidding: bigN = shape(north, any 6xxx + any 7xxx + any 8xxx + any 9xxx + any 00xx + any 01xx + any 11xx + any 02xx + any 12xx + any 03xx ) bigS = shape(south, any 6xxx + any 7xxx + any 8xxx + any 9xxx + any 00xx + any 01xx + any 11xx + any 02xx + any 12xx + any 03xx ) bigE = shape(east, any 6xxx + any 7xxx + any 8xxx + any 9xxx + any 00xx + any 01xx + any 11xx + any 02xx + any 12xx + any 03xx ) bigW = shape(west, any 6xxx + any 7xxx + any 8xxx + any 9xxx + any 00xx + any 01xx + any 11xx + any 02xx + any 12xx + any 03xx ) solidN = (hascard(north, AS) and hascard(north, KS) and hascard(north, QS) and hascard(north, JS) and hascard(north, TS) and (shape(north, 6xxx) OR shape(north, 7xxx) OR shape(north, 8xxx) OR shape(north, 9xxx)) or (hascard(north, AH) and hascard(north, KH) and hascard(north, QH) and hascard(north, JH) and hascard(north, TH) and (shape(north, x6xx) OR shape(north, x7xx) OR shape(north, x8xx) OR shape(north, x9xx)) (hascard(north, AD) and hascard(north, KD) and hascard(north, QD) and hascard(north, JD) and hascard(north, TD) and (shape(north, xx6x) OR shape(north, xx7x) OR shape(north, xx8x) OR shape(north, xx9x)) or (hascard(north, AC) and hascard(north, KC) and hascard(north, QC) and hascard(north, JC) and hascard(north, TC) and (shape(north, xxx6) OR shape(north, xxx7) OR shape(north, xxx8) OR shape(north, xxx9)) solidS = (hascard(south, AS) and hascard(south, KS) and hascard(south, QS) and hascard(south, JS) and hascard(south, TS) and (shape(south, 6xxx) OR shape(south, 7xxx) OR shape(south, 8xxx) OR shape(south, 9xxx)) or (hascard(south, AH) and hascard(south, KH) and hascard(south, QH) and hascard(south, JH) and hascard(south, TH) and (shape(south, x6xx) OR shape(south, x7xx) OR shape(south, x8xx) OR shape(south, x9xx)) (hascard(south, AD) and hascard(south, KD) and hascard(south, QD) and hascard(south, JD) and hascard(south, TD) and (shape(south, xx6x) OR shape(south, xx7x) OR shape(south, xx8x) OR shape(south, xx9x)) or (hascard(south, AC) and hascard(south, KC) and hascard(south, QC) and hascard(south, JC) and hascard(south, TC) and (shape(south, xxx6) OR shape(south, xxx7) OR shape(south, xxx8) OR shape(south, xxx9)) twoN = shape(north, any 55xx + any 56xx + any 57xx + any 58xx + any 66xx + any 67xx) twoS = shape(south, any 55xx + any 56xx + any 57xx + any 58xx + any 66xx + any 67xx) highNS = hcp(south)+hcp(north)>20 majorsNS = shape(north, 5xxx + x5xx) or shape(south, 5xxx + x5xx) spadeEW = spades(west)+spades(east)>9 diamondEW = diamonds(west)+diamonds(east)>9 heartEW = hearts(west)+hearts(east)>9 clubEW = clubs(west)+clubs(east)>9 competition = clubEW or heartEW or diamondEW or spadeEW bigE and bigW and bigN and bigS