Skip to content
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

Command aliases #102

Open
lanslide-team opened this issue Dec 6, 2023 · 4 comments
Open

Command aliases #102

lanslide-team opened this issue Dec 6, 2023 · 4 comments

Comments

@lanslide-team
Copy link
Contributor

lanslide-team commented Dec 6, 2023

Adding some aliases might be nice

Player Commands

!r / .r =>ready
!stay /.stay => stay on the same team after veto
!switch / .switch => switch team after veto

Admin Commands

!lc => load remote config
!lcf => load local config file
!fs => force start a match starting at 0-0
!cm / !nl => cancel/stop match or not live
!ch => cancel half
!sm => start match
!match_state => Current match state [PugSharp.Match.Contract.MatchState]
!map_score => Returns the correct map score, eg: Team 1 [4] vs Team 2 [5]
!team1_name => The name of Team 1
!team1_map_score => The current round wins for Team 1
!team1_series_score => The overall score for Team 1 in this series
!team1_side => Either T or CT
!team2_name => The name of Team 1
!team2_map_score => The current round wins for Team 2
!team2_series_score => The overall score for Team 2 in this series
!map_score_json => Return the current map score as json, eg: {"team1":{"name":"Team 1","score":4,"side":"T"},"team2":{"name":"Team 2","score":5}}
!series_score_json => Returns the series score as json, eg: {"team1":{"name":"Team 1","score":0},"team2":{"name":"Team 2","score":1}}

@lanslide-team
Copy link
Contributor Author

lanslide-team commented Dec 8, 2023

Having !match_state and !map_score_json would be a game changer :)

@TheR00st3r
Copy link
Member

TheR00st3r commented Dec 11, 2023

Hi,

I started adding the aliases and Commands.

Current State:

  • !r / .r =>ready

  • !stay /.stay => stay on the same team after veto

  • !switch / .switch => switch team after veto

  • !lc => load remote config

  • !lcf => load local config file

  • !fs => force start a match starting at 0-0

  • !cm / !nl => cancel/stop match or not live

  • !ch => cancel half

  • !sm => start match

  • !match_state => Current match state [PugSharp.Match.Contract.MatchState]

  • !map_score => Returns the correct map score, eg: Team 1 [4] vs Team 2 [5]

  • !team1_name => The name of Team 1

  • !team1_map_score => The current round wins for Team 1

  • !team1_series_score => The overall score for Team 1 in this series

  • !team1_side => Either T or CT

  • !team2_name => The name of Team 1

  • !team2_map_score => The current round wins for Team 2

  • !team2_series_score => The overall score for Team 2 in this series

  • !map_score_json => Return the current map score as json, eg: {"team1":{"name":"Team 1","score":4,"side":"T"},"team2":{"name":"Team 2","score":5}}

  • !series_score_json => Returns the series score as json, eg: {"team1":{"name":"Team 1","score":0},"team2":{"name":"Team 2","score":1}}

@TheR00st3r
Copy link
Member

TheR00st3r commented Dec 12, 2023

@lanslide-team I am not sure if i undestood !ch correctly. What should happen for !ch? What should happen if it is called in the first half, in the second half, in overtime? Is it really required?

@lanslide-team
Copy link
Contributor Author

First half would be the same as restarting the game at 0-0.
Second half would be back to half-time (eg: 6-6).
Overtime: Similar rules

It may be needed if there are multiple technical issues (server is lagging, multiple player drops). You could restore the match to a certain round, but this would be easier.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants