It should start a DM and it should tell you both of your pairings, their rating, your scheduled times and/or results and perhaps a "countdown" till your game time:

example:

Lonewolf: you play endrawes0 (1687) on Sunday at 17:00 which is in 2day, and 3 hours.
Team: You played jaivl (1987) on Saturday at 08:00 and lost.

looking at this now and realizing we need some organization...

go through all the logging and verify errors go to stderr

When updating ratings from lichess, we should probably have chesster also check to see if a particular user is marked as an engine users and inform the mods. I realize that engine use in casual and correspondence games might be allowed, but it's probably worth it for the league.

pairing currently gives "theino will play Pasternak(2019). The game is unscheduled."

Color should be added. Ex: "theino will play white against Pasternak(2019). The game is unscheduled."

all of pairing and pairing lakinwecker and pairing r-mena fail.

pairing @r-mena and pairing @lakinwecker are working

@lakinwecker - per our convo on slack

it seems like new players - at least spacemodulator wasn't updated by chesster until there was a rating request - see attached image

Do it after the gamelink parsing is finished.

i'm not sure how hard this would be, but assuming we have everyone's email this might be a very nice feature - i thank cal invites could even be used by people that don't have a gmail address - but i'm not sure about that

one risk might be exposing league member's emails, maybe there's a way around that...

to build on this, if chesster had a public calendar he could be included on the invites - then we'd have an easily viewable calendar of games.

just spit-ballin ideas - i missed my round 8 game because i messed up my own calendar entry...

E.g. @chesster captains
Et Cetera...

would avoid people repeating the same request over and over when they realize it is a rate limit issue.

When the position is stalemate and someone attempts to post the result, chesster thinks the game is ongoing.

Create a message for the case when no subscriptions are found.

remove isPotentialSchedule from chesster.js because this local is not necessary. We can simply return from inside the catch clause

Tell them to ask a moderator.

README is lacking some detail now that we have reorganized the code base and refactored.

lonewolf 45+45 this is a long sentence, maybe it requires a long sentence, and some numbers 24 2

Example: @jagvillspelaschack: vs @mooserohde 0-1

Allow mods to update anything

It's not overly difficult to keep an eye on the spreadsheet. But, since almost everything at this point can be managed from slack, it'd be nice to have an easy way for captains to keep track of if their team has scheduled or not.

Maybe even a ping on Wednesday if a teammate hasn't scheduled yet.

Thanks for what you're doing!

This command should store your preferences in a local data storage and ensure that whenever a gamelink is posted for the player you have posted, chesster will tell you that they are playing

Needs a spaced after mods: and before @endrawes0

Pick one and fix it.

We should be consistent going forward.

We are still using callbacks in a few places, notably in the spreadsheets.js - we should use promises as that means our exceptions will be caught and logged for us.

Currently, trying to schedule an unknown pairing will take him down.

It hasn't picked up my schedule for round 2 of lonewolf

`@chesster subscribe @endrawes game-start``

@chesster unsubscribe @endrawes0 game-start

events.publish('game-start', target='endrawes0')

`````` 'game-scheduled'```

'game-forfeited'

for
botExceptionHandler
exceptionHandler
and criticalPath

For some reason it thought it was too late?

its not used or useful when you compare to what git offers. get rid of it.

Currently returns https://githaub.com/endrawes0/Chesster, should return https://github.com/endrawes0/Chesster. I was going to submit a PR for this, but it doesn't look like the config is in the repository.

/home/endrawes0/Chesster/chesster.js:1602
if( details.winner && result.result == "1/2-1/2" ){
^

TypeError: Cannot read property 'winner' of undefined
at validate_user_result (/home/endrawes0/Chesster/chesster.js:1602:16)
at /home/endrawes0/Chesster/chesster.js:1637:28
at IncomingMessage. (/home/endrawes0/Chesster/chesster.js:1533:17)
at emitNone (events.js:72:20)
at IncomingMessage.emit (events.js:166:7)
at endReadableNT (_stream_readable.js:913:12)
at nextTickCallbackWith2Args (node.js:442:9)
at process._tickCallback (node.js:356:17)
/
~/Chesster /

8:51 PM]
kirschwasser @cheesehead04 v @Kirschwasser 0-1
[8:52 PM]
lakinwecker hrmm
[8:53 PM]
@cheesehead04 0-1 @Kirschwasser
[8:53 PM]
chessterBOT Sorry, you do not have permissin to update that pairing.
[8:53 PM]
lakinwecker Try that format
[8:53 PM]
not sure why yours didn't work
[8:54 PM]
kirschwasser @cheesehead04 0-1 @Kirschwasser
[8:54 PM]
not working
[8:54 PM]
lakinwecker huh
[8:54 PM]
That is really odd
[8:55 PM]
@Kirschwasser: can you try it again?
[8:55 PM]
kirschwasser @cheesehead04 0-1 @Kirschwasser
[8:55 PM]
lakinwecker There is a bug
[8:55 PM]
it's trying to read your game link and failing, for some reason
[8:55 PM]
I'll file a bug and ensure a mod updates it for you

https://github.com/endrawes0/Chesster/blob/master/chesster.js#L1607

probably format(...) is nicer mechanism

I am UTC-6, but I got this notification today:
forhavu vs r-mena has been scheduled for 2016-07-06 @ 11:00 UTC, which is Wed @ 13:00 for you.

Which is (for some reason) converting it it to UTC+2 !? I have tested locally and it's converting properly for me when testing locally. Note that the notification I got for my own game was also incorrect.

mooserohde vs lakinwecker has been scheduled for 2016-07-10 @ 20:00 UTC, which is Sun @ 22:00 for you.

it can go back in when its a real possibility... follow up item: implement a challenge command...

During testing, I saw the round appeared to be over after midnight. Need to review the cause.