| |
BGonline.org Forums
Barring Players from ABT Events
Posted By: Chuck Bower In Response To: Barring Players from ABT Events (Coolrey)
Date: Thursday, 28 August 2008, at 1:49 p.m.
Two (unrelated) comments:
1) Even though I believe what you (Ray) have said, I learned long ago that there are almost always two sides to every story. Often the two sides can't agree on the exact details. Sometimes one side leaves out an incident, possibly not even realizing it was part of the 'event'. I think before people choose to skip EF's tournaments based solely upon Ray's treatment they should try to get "the rest of the story" (Paul Harvey short, in case you don't listen to daytime radio). Having said that, I repeat that if she were planning on banning you before she went out to dinner with you she should have declined the dinner invitation (and any compensation/reimbursement for the dinner, for SURE). If it were merely (or additionally) the dinner conversation that sent her over the edge, well, maybe, but it would have to be a seriously egregious dinner incident, which we certainly haven't heard about from your 'testimony'. BTW, did she merely 'ask' you not to come back, tell you that you would "not be welcome", or go all out and use one of the b-words or equivalent? Probably a technicality, anyway.
2) I wish tournament directors would contact entrants upon receipt of entry. I often wonder "did my entry actually arrive"? It's not the $ issue which I expect would be easily resolved since all the ABT directors I know are 100% honest+trustworthy. But, for example, events which have limited entry slots and it's first-come, first-served. If the entry gets lost (or it's even possible I forget to mail it!), I could correct the situation in time to still make the field. (This problem has never happened to me, that I can remember, but I bet it has to someone. And it certainly COULD happen -- I have a friend who works for the P. O. and you should hear the stories he tells!)
| |
BGonline.org Forums is maintained by Stick with WebBBS 5.12.