Time Clock |
---|
FINAL |
Team | 1st | 2nd | 3rd | Total |
---|---|---|---|---|
TBL | 2 | 0 | 0 | 2 |
WSH | 2 | 0 | 2 | 4 |
Team | Shots | Hits | Blocked | FO Wins | Giveaways | Takeaways | Power Plays |
---|---|---|---|---|---|---|---|
TBL | 34 | 25 | 15 | 50.0% | 3 | 11 | 0/1 |
WSH | 34 | 57 | 14 | 50.0% | 7 | 13 | 1/3 |
Period | Time | Team | Strength | Goalie | Description |
---|---|---|---|---|---|
3rd | 16:46 | WSH | Even Strength | Nic Dowd (11) snap shot, assists: Beck Malenstyn (15), Trevor van Riemsdyk (14) | |
3rd | 08:29 | WSH | Power Play | John Carlson (9) snap shot, assists: Dylan Strome (39), Tom Wilson (16) | |
1st | 16:24 | TBL | Even Strength | Brandon Hagel (25) backhand shot, assists: Steven Stamkos (39), Anthony Cirelli (25) | |
1st | 14:00 | WSH | Even Strength | Sonny Milano (15) wrist shot, assists: None | |
1st | 13:06 | TBL | Even Strength | Anthony Duclair (23) deflected shot, assists: Brayden Point (44), Darren Raddysh (26) | |
1st | 09:56 | WSH | Even Strength | Sonny Milano (14) backhand shot, assists: Max Pacioretty (19), Hendrix Lapierre (14) |
Period | Time | Team | Type | Min | Description |
---|---|---|---|---|---|
3rd | 07:17 | TBL | Minor | 2 | Nicholas Paul tripping against Sonny Milano |
3rd | 06:24 | TBL | Minor | 2 | Tanner Jeannot boarding against Vincent Iorio |
2nd | 15:22 | WSH | Minor | 2 | Dylan Strome hooking against Brayden Point |
2nd | 11:01 | WSH | Major | 5 | Nic Dowd fighting against Michael Eyssimont |
2nd | 11:01 | TBL | Major | 5 | Michael Eyssimont fighting against Nic Dowd |
2nd | 02:39 | TBL | Minor | 2 | Steven Stamkos cross-checking against T.J. Oshie |
Start Times
PT | MT | CT | ET | AT |
---|---|---|---|---|
02:30PM | 03:30PM | 04:30PM | 05:30PM | 06:30PM |
I am open source! Report issues, contribute, and fund me on my GitHub page!
Just testing this, everyone.
Advantages of this bot: It’s automatic. It will automatically post a GDT one hour before puck drop.
Disadvantages: It doesn’t have the personality (and Ovi tracker) that u/[email protected]’s threads do.
It isn’t very configurable…basically what you see now is what you get. Opinions?
Hi All! I am the developer of this bot. I just wanted to drop in and say hello and make sure it is working as expected. Y’all are only the third deployment behind [email protected] and [email protected], so I am a bit nervous that something is gonna break if I don’t check on it constantly. 😅
It looks like in the conversation here, some folks are asking about customization. An issue has already been created for customizing when the post is made. If anyone has any other suggestions, either shoot me a message here on lemmy or create an issue on github.
I will admit that I have been spending less and less time developing this bot as other projects have been taking priority. But if there is renewed interest in this project, I will do my best to commit the time to it that is needed.
So far, so good. Thanks for your help getting it running.
I’d like to see an option for less logging. I’m a little afraid to keep it running full time because of that issue. Or if it could clean out the log every so often. I was going to write an issue for that request but haven’t gotten around to it yet.
I’d also like to find a way to not run out as root on my machine. Just a security thing. I think I need to set up another user and put them in the docker group.
I guess great minds think alike, because I actually created an issue for customizable log levels earlier today! I do have it configured though to only allow either 10 or 20 MBs of logs before it starts overwriting the old ones. Perhaps I could make that customizable as well. Early on, I was running into tons of issues, so I needed extremely verbose logging to track them all down. But the main issues have been taken care of (until the NHL decides to change their API again. 😭)
I’m not running mine as root. That’s a pet peeve of mine as well. It’s why I use podman instead of docker. Podman has rootless built-in and default, whereas a lot of configuration is required to make docker run rootless. Nothing about the bot requires root, and I plan on keeping it that way forever.
Hell, I even figured out a way to get my Lemmy instance to run rootless with podman. I often wonder if I was the first one to figure that one out. Though I have since taken my instance down, as I the other Lemmy instances have stabilized.
I just thought of something else. It’s probably a good idea to be able to put a contact person in the post automatically.
Yes, that’s a great idea. Would a customizable message at the bottom of the post be sufficient? You could have it mention the contact person and word it however you want.
Yeah, that’s good.
I’m glad to hear it limits the logs. That makes me feel much better about that.
I have to admit, I’ve been using Linux for a few decades now, but docker et al are pretty new to me, so I’m just kind of fumbling my way through that.
As far as basic end of game box stats, it does its job wonderfully. As far as personality, do you have a GitHub link for the bot repo? maybe some open sourcing can help?
Edit: just saw the GitHub link at the bottom of the bots post. Looks like I’ll be taking a look when I get to a PC
Yeah the original coder did a great job. And losing the personality might be worth it to save yo’s workload!
Seems like an accurate analysis, but I’ll just point out that as I see it the advantage would be for yo_scottie_oh specifically, while the disadvantage affects everyone else.
Pretty much! I told him I’d test this, and it seems to work. I wish it was more configurable, but my knowledge and time to edit code are limited.
Of course it also relies on someone’s server to work, in this case mine. So if that server went down or my internet was offline (both rare events, but not impossible), it would fail.
Thanks for getting this up and running! We should definitely try it for the next couple games and see how it goes.
I have the bot set to run for the game tonight. I’m actually going to the game and will be leaving well more than an hour ahead of puck drop, so…hopefully things go okay. The bot should post one hour ahead of time. It went okay the other day, so I’m not expecting issues.