michaeljacobdavis / foos-bot Goto Github PK

some folks have a strong preference for either offense or defense. occasionally i've see teams where both teammates prefer the same position and end up doing very poorly in the match up. not sure if there is a good solution here, maybe we can provide a suggestion when such a team is matched up?

Allow !in @person1 @person2

Allow for tournaments to be held using a bracket system.

Open questions:

• How to decide teams? Should rankings factor in?
• What is the time scale?
• Max/min number of teams

Please chime in on suggestions/comments/questions.
/cc @clogston @jsrubin @joshparolin @therahl

For your consideration,
Bot posts current player list at game start and when players join. Could also post at a fixed interval that a game is waiting for players. 3 minutes? 5 minutes?

Rather than the current ranking system, I propose we use something like https://en.wikipedia.org/wiki/Elo_rating_system that takes into account strength of opponents.

Downsides I can see:

• Doesn't take into account peoples strengths and weaknesses when pairing (two good defensive players that are bad on offense).
• Still might encourage people to play easier matches, but I think it would be better than it is currently.

Opinions?
/cc @clogston

Could also have !stat @name to get the record for an individual.

Customer should always be number 1, with player ranks starting at 2.

I sometimes forget to play foos, and other too, even if we all are available. It is a bad thing since it wastes the precious resource--the-foos-table, makes us fat, and have less fun.

As an example, instead of:

1) Cheryl | 17-3
2) Fred | 4-2
3) Jeff | 4-2
4) Edward | 0-3

show:

1) Cheryl | 17-3
2) Fred | 4-2
2) Jeff | 4-2
4) Edward | 0-3

Using !stats:

Show buttons to choose what kind of stats report.

[Rank List] [Chart Past 7 Days] [Chart Past 30 days]

Should be able to pass in multiple users here to get a chart for X number of players.

Using !stat
[Win-Loss Record] [Chart Past 7 Days] [Chart Past 30 days]

It's possible to !out to where no players are left. The game should auto !stop.

keep statistics on wins by table color to see if a particular side has "home field" advantage effect

Also, if they come back again and again 5+ wins in a row, the retirement period increases to 3, 5, 8, 12 ...

https://api.slack.com/docs/message-buttons

Using !stats or !stat:
Have the ability to choose [Record vs.] @username

Would return your win-loss record in games played against that @user

Saving algorithm ideas for the comments section...

Could also categorize levels of disparity! e.g., heavily favored, favored, slightly favored.