Dealer Script: 4 Aces Point Count

[hrothgar]

I'm going to kick off a few threads that are intended to show some interesting things that you can use with BBO's new Dealer.

 

I don't claim that these scripts are necessarily the "best" way to support a given feature. I hope that they are easy to understand.

 

Quick comment on syntax. Dealer uses a hash mark (aka a # sign) to denote comments. I will always try to use a red font to show actual code that you can run in the Dealer window. If you cut and paste this code into BBO, you should be able to run it as is...

 

I'm going to start with a few simple scripting techniques, then start building some more complicated examples.

 

My first example is very simple and very useful.

 

Dealer uses "HCP" to apply a traditional

 

Ace = 4

King = 3

Queen = 2

Jack = 1

 

point count.

 

Many folks prefer a point count that places more value on Aces and Kings and discounts "quacks". For example, the 4 Aces Point Count valued

 

Ace = 3

King = 2

Queen = 1

Jack = .5

 

You can uses the "altcount" and "c13" commands to create your own point count system. "altcount" defines your index. "c13" invokes this index.

 

The following script creates a

 

Ace = 3

King = 2

Queen = 1

Jack = .5

Ten = .2

 

point count scale. It will then generate deals such that North always holds exactly 10.7 "points".

 

 

######### Definition - Opening Points

 

# 11 is the index for c13

# This function allows the user to define valuations for calculating

# HCP

# Most hand evaluation is performed using a modified version of

# the 4 Aces Point Count.(Ace = 3, King = 2, ...)

# All values are multiplied by 100 to avoid fractions

 

altcount 11 300 200 100 50 20

 

############## Condition

 

c13(north) ==1070

 

[0 carbon]

Where is the complete list of Dealer commands?

[diana_eva]

This is where Fred & Uday guide people for more info in case they ask:

 

http://henku.home.xs...input_file.html

 

The vast majority of BBOers use the visual interface, so there isn't any thorough documentation created for this purpose.

[FM75]

This is where Fred & Uday guide people for more info in case they ask:

 

http://henku.home.xs...input_file.html

 

The vast majority of BBOers use the visual interface, so there isn't any thorough documentation created for this purpose.

 

Thanks for the link. To save others some "debugging time" here is a list of things that do not work:

• vulnerable
  
• dealer
  
• any of the actions (this should be obvious from seeing what they do)
  

 

Is vulnerability really only random?