Board for everybody who is interested in BrainKing itself, its structure, features and future.
If you experience connection or speed problems with BrainKing, please visit Host Tracker and check "BrainKing.com" accessibility from various sites around the world. It may answer whether an issue is caused by BrainKing itself or your local network (or ISP provider).
Fencer: This is not really a Feature Request, more of an idea for Brainking Teams playing a bigger part. My first thought was about having a Team Backgammon League, but after talking to a couple of players it could take alot of sorting out. So to a new idea which should be alot easier as i think nearly all the code is already written, it just needs modifying. How about we have TEAM Backgammon stairs. Backgammon is the obvious choice as most Fellowships have a Team for it, if it works then other Stairs could be introduced. All that we need is Rules set, as in number of players(6 seems good), changing Team players, amount of challenges at one time etc.... There would have to be a good way to check players are not chopping & changing Teams every few days though. What do you think ?
Změněno uživatelem coan.net (1. listopadu 2006, 15:04:01)
MadMonkey: Working from your idea, this is what I see:
Each fellowship has 1 team of 6 players in the stairs. Or beter yet, maybe 7 players, that way there will be less ties. But getting 7 might be hard for some fellowships. Maybe 5, but allow fellowship to enter 2 teams for those who have a lot. But now I'm getting into more work for Fencer.
Since it's backgammon, I would say just do a 1 game per 2 players.
Each team captain can challenge 1 team, and can also be challenged by another team. So no more then 2 team stair matchs can go on at the same time. (like current stairs)
The players on the team when the challenge started stays until that match is done.
I'm not sure what I like beter: 1) Limit a team to changing 1 player once a month (or) 2) A player has to stay with a team at least a month before they can be removed or leave. (which means every month, a fellowship could technicly change their team completly.
I kind of like #2 beter since sometimes you will get a few people who will all of a sudden not want any more games and may need to be replaced.
Of course the extra rule would be that if a person drops their membership to a pawn level, they can be removed and replaced right away without the limits above getting in the way. (*** When I say right away - they can complete current games, but no new challenges can be made or accepted until the pawn is replaced by a knight/rook fellowship member ***)
Other then that, most of the regular stairs rules would work. The time limit of 4-5 days I found work for the majority of players (a few find it too slow, a few find it too fast - but most find 4-5 days pretty good).
So this is my more complete thoughts about MadMonkey's team stairs.
BIG BAD WOLF: Sounds good. I prefer #2 idea better like you do. I also thing there should be an option for players where they can add whether they are available to play a match or not, an active/non-active box they can change on the team sheet. Some players may be going on holiday or not want any more games as you say. This way the Captain would know who to pick from, it would save players leaving and re-joining Teams.
Time is the only issue i was thinking of. At present there are some players who do keep Tournaments running as they do not move till just before there time is up for a move. I can see this irritating some other players who would like to get on with Matches. I think either 3-4 days per move or have 2 sets of Stairs, one Fast & one Slow or use the Fischer's clock to set how long a match should last.
Hrqls: Yep, i agree with that totally. Fencer (and Liquid of course) would be the only ones able to move players in/out of Teams for what they deem a valid reason at ant other times.
(skrýt) Při psaní příspěvků nebo zpráv můžete použít jednoduché HTML tagy. Platící členové mají možnost zapnout Rich Text Editor. (pauloaguia) (zobrazit všechny tipy)