drneau.com Forum Index drneau.com
A discussion board for drneau.com
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

3 tournament granularities

 
Post new topic   Reply to topic    drneau.com Forum Index -> Development and Release News
View previous topic :: View next topic  
Author Message
drneau
Site Admin


Joined: 13 Feb 2005
Posts: 2385
Location: Woodbury, MN

PostPosted: Tue Oct 02, 2007 4:29 pm    Post subject: 3 tournament granularities Reply with quote

I've now identified three tournament modes for v3. The difference being how data is tracked for each type.

This has nothing to do with heads-up/shootout/freezeout....

For all three types, you specify buy-in, add-on and rebuy options. You create a chip case. You have a betting schedule and a payout schedule. You can track expenses. You can have a checklist and console settings.
So, what's different about them?

Type 1: "Standard"
This type of tournament is ideal for the home game where they want a detailed report of all activities, possibly to post to a website.
- The state of the tournament is history-based (like in v2).
- Requires a player database.
- League association is optional.
- Extremely detailed history of the tournament (who knocked out who when, etc.)
- Complex side-bet capabilities.
- Seating management.
- Tournament placing is history-based.
- Number of knockouts per player is automatically tracked via history.

Type 2: "Mixed"
This type of tournament is ideal for a bar league (as an example).
- No history tracking.
- Player state is specified manually.
- Seating management.
- Buy-in count, add-on count, rebuy count, are calculated.
- Remaining player count is manually specified.
- Still uses player database and can be associated to a league.
- Number of knockouts per player is manually tracked.
- Pretty good side-bet capabilities.
- You specify tournament placing manually.

Type 3: "Simple"
This type of tournament is ideal for those who just want a simple clock, betting schedule and payout schedule. Candidate for tournaments where you don't care about the details afterward.
- No player database
- No ranking method
- No roster
- No seating management
- No side bet management
- No history tracking
- Player names are typed in manually for finishes.


I AM looking for better names for these.
_________________
--
Dr. Neau (not a real doctor)
http://drneau.com
http://home.comcast.net/~jneau
Back to top
View user's profile Send private message Send e-mail Visit poster's website
rastapete
Founding Father
Founding Father


Joined: 13 Feb 2005
Posts: 401
Location: 'Ipsa' this, you pissy little bitch!

PostPosted: Tue Oct 02, 2007 4:43 pm    Post subject: Reply with quote

"League"

"Open"

"Sit 'n' Go"
Back to top
View user's profile Send private message
rumackay
"A Set of Mop Squeezers"


Joined: 15 Oct 2005
Posts: 60
Location: Queensland, Australia

PostPosted: Wed Oct 03, 2007 3:46 pm    Post subject: Reply with quote

"Advanced"

"Standard"

"Basic"
_________________
-- Kingaroy High Rollers Poker Tour --
Back to top
View user's profile Send private message
drneau
Site Admin


Joined: 13 Feb 2005
Posts: 2385
Location: Woodbury, MN

PostPosted: Wed Oct 03, 2007 4:15 pm    Post subject: Reply with quote

I think I've settled on:
- Standard Self-Validating
- Standard Non-Validating
- Standard Simple

The word "standard" will distinguish it from other tournament types I'll create in the future (like Heads-Up, Complex, etc.).

"Self-Validating" means that the state of players, etc. is entirely based on the entries in the event log....much like the balance of your bank account is based on the entries in your statement history.

"Non-Validating" means that the state of players, etc. is something you can tweak at will. Someone is eliminated? Simply set them to eliminated.
You'll still have the event log with this one, but there's a good possibility that it won't represent reality. The event log is more like a diary than a bank statement.

"Simple" means no player management at all. Just a chip case, betting schedule, payout schedule, financial management, etc. You will simply enter the number of purchases of each buyin/addon/rebuy, the number of remaining players, etc.

Don't get the difference between "self-validating" and "non-validating"? Let me explain it this way.

Scenario: You eliminate the wrong player and fix it.
- In "Self-Validating", you'll eliminate player like you are used to, then go and edit the event log to remove the event.
- In "Non-Validating", you'll eliminate the player like you are used to, then simply set them back to "active". You can tweak the event log later, if ever.

Why have both???

I've always liked the idea of the event log dictating what ACTUALLY happened. And in v3, it'll be much easier to edit (it'll be cool).
However, some people are confused by that. Other tools don't have that concept.

Does that make sense? Please let me know if it doesn't, because I'll need to make it crystal clear in the tool.
_________________
--
Dr. Neau (not a real doctor)
http://drneau.com
http://home.comcast.net/~jneau
Back to top
View user's profile Send private message Send e-mail Visit poster's website
drneau
Site Admin


Joined: 13 Feb 2005
Posts: 2385
Location: Woodbury, MN

PostPosted: Wed Oct 03, 2007 4:25 pm    Post subject: Reply with quote

I may also just combine "SelfValidating" and "NonValidating" into one type and give you the option of setting the EventLog to either "SelfValidating" or "NonValidating"...but I need to think about the repercussions of that.
_________________
--
Dr. Neau (not a real doctor)
http://drneau.com
http://home.comcast.net/~jneau
Back to top
View user's profile Send private message Send e-mail Visit poster's website
drneau
Site Admin


Joined: 13 Feb 2005
Posts: 2385
Location: Woodbury, MN

PostPosted: Wed Oct 03, 2007 4:34 pm    Post subject: Reply with quote

drneau wrote:
I may also just combine "SelfValidating" and "NonValidating" into one type and give you the option of setting the EventLog to either "SelfValidating" or "NonValidating"...but I need to think about the repercussions of that.


And if I did that, you'd be able to change from "Validating" to "Non-Validating" mid-tournament.

In either case, you'd still do eliminations/buy-ins/add-ons/rebuys the same way. The difference would be what happens behind the scenes.

In "Validating":
- You use the elimination wizard. The wizard only lets you do what's valid based on current player states.
- The event is added to the log and the log is validated.
- The state of the tournament is updated based on the log.
- The counts on the console are changed because the state of the player changed.

In "Non-validating":
- You use the elimination wizard. The wizard only lets you do what's valid based on current player states.
- The event is added to the log. The log is NOT revalidated.
- The state of the eliminated player is simply set to "eliminated".
- The counts on the console are changed because the state of the player changed.

Maybe that's the way to go.
_________________
--
Dr. Neau (not a real doctor)
http://drneau.com
http://home.comcast.net/~jneau
Back to top
View user's profile Send private message Send e-mail Visit poster's website
rastapete
Founding Father
Founding Father


Joined: 13 Feb 2005
Posts: 401
Location: 'Ipsa' this, you pissy little bitch!

PostPosted: Thu Oct 04, 2007 9:52 am    Post subject: Reply with quote

Well, you've talked me into it.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    drneau.com Forum Index -> Development and Release News All times are GMT - 6 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group