-
Notifications
You must be signed in to change notification settings - Fork 688
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Less text in terminal #10
Labels
enhancement
New feature or request
Comments
Ok maybe I exaggerated with the logs, I have a 21: 9 |
i would remove the 'seconds' as well.. since it's not a busy log. |
I'm not agree to remove 'seconds' , I will remove the year in the 'less version' |
Yes much better! |
Tkd-Alex
added a commit
that referenced
this issue
Jan 22, 2021
Tkd-Alex
added a commit
that referenced
this issue
Jan 22, 2021
Tkd-Alex
added a commit
that referenced
this issue
Jan 22, 2021
ghost
mentioned this issue
Apr 24, 2021
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There should be an option in run.py that would simplify the displayed text in the terminal. I think I already saw something commented in some file that just said "xx channel points for yy". Why not have that for everything that can happen? So for example:
21/01/21 23:33:19 - INFO - [on_message]: +10 → Streamer(username=streamer_username, channel_id=x, channel_points=y) - Reason: WATCH.
would just be
21/01/21 23:33:19 - +10 cp for streamer_username
or
21/01/21 23:45:44 - INFO - [on_message]: +50 → Streamer(username=streamer_username, channel_id=x, channel_points=y) - Reason: CLAIM.
would just be
21/01/21 23:33:19 - +50 cp for streamer_username.
Especially bets fill up the screen really quick. So they could just be "streamer_username has started a bet called name_of_bet" and "Placing a bet for streamer_username for name_of_bet_" and at the end just "Won/Lost bet for x cp on name_of_bet of streamer_username" or whatever.
I like having it on the second monitor but I don't like that its filling up the screen if a lot of nonsense to me.
The text was updated successfully, but these errors were encountered: