-
Notifications
You must be signed in to change notification settings - Fork 25
Added waiting for staff and fixed sam #69
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
base: next-version
Are you sure you want to change the base?
Conversation
Added support for waiting for staff
Fixed remove slays command for sam
|
Awesome thank you! |
|
Awesome, |
|
Sorry I will need to test this tomorrow/later this week. I didn't have time today. |
|
Hm. I gave it a test, but for some reason the menu still showed the report as "Waiting" From what I could tell, the status I shall have to give it another test |
|
The status is changed to waiting for staff when the victim has decided to keep the report and not forgive them. So you will need to report a player that can respond to your report and when you see their response you are giving two options keep or forgive. If you select keep then the status of the report is set to waiting for staff. I tested with players not bots and a dedicated server. |
|
Hey! Sorry for the delay on this. Busy few days for me. |
callumok2004
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When a report status is set to in progress or finished, there is a check to ensure the previous status was "waiting", this does not check if the previous status could have also been "waiting for staff" causing the pending reports to be invalid.
|
Hey. Thanks for taking a look at this @callumok2004 |
|
I have found a few more SAM related issues that I would like to fix in this PR before merge. @callumok2004 I believe that should fix the issue. |
|
This weekend I'll have time to fix all the remaining SAM issues. |
|
I am testing all of the changes on my TTT server. |
|
Ready to be merged |
|
Fixed #51 |
The base branch was changed.
BadgerCode
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall it looks fine, but I think this could do with some comprehensive testing as introducing a new status for reports is quite a significant change.
Added comment for timer
|
@Minc3 EDIT: I believe that SAM related changes should be made in seperate PR to merge them right now, while new status will be waiting for it's time. |

No description provided.