Denied New CI commands

[Fexxyzin]

What does this suggestion change/add/remove:
[ This would add four (or two if combined) commands like "MR Over", "DC Over", "MR Cooldown", and "DC Cooldown".
The first two could only be used by COs to mark the time when the main raid or DC ended.
The third and fourth could be used by any CI member to know when they could do the next raid, and would work like this:

[13:43] CI CO: (! or /) MR Over
MR Over 13:43

[13:53] Any CI member: (! or / MR) cooldown
30 minutes left (14:28)

The DC would work similarly* ]

Has something similar been suggested before? If so, why is your suggestion different?:
[ Not that I’m aware of. ]

Possible Positives of the suggestion (At least 2):
[ Mainly a quality-of-life improvement and helps with cooldown tracking and raid organization. ]

Possible Negatives of the suggestion:
[ I don’t think there would be any negative effects. ]

Based on the Positives & Negatives, why should this suggestion be accepted:
[ In my view, this is a simple quality-of-life feature with no downsides. ]

 

[Holland]

hey @Fexxyzin

Please remove the unnecessary section from this suggestion


This is fine to do as your profile signature but not in the post itself.

 

[Betriv]

bro flexing his positions in his suggestion

-support low effort and is unneeded

 

[Emilia Foddg]

...This is really not necessary.
If COs want to use the chat timestamps as guides to help with the raid timers, they can simply just... Use the chat. Like comms, or even just PM/whisper themselves. Then use that timestamp. There's no need for a command.
-Support

 

[Snake]

I'm not sure if you're aware but raids have to be authed via the in game chat anyway. So in a sense they are timestamped anyway

 

[Niox]

Why?

 

[Fexxyzin]

-support low effort and is unneeded

Where did I put low effort? On the whole suggestion or just a subsection, tell me where so I can try and fix it!

---

...This is really not necessary.
If COs want to use the chat timestamps as guides to help with the raid timers, they can simply just... Use the chat. Like comms, or even just PM/whisper themselves. Then use that timestamp. There's no need for a command.

I'm not sure if you're aware but raids have to be authed via the in game chat anyway. So in a sense they are timestamped anyway

I'm not really sure if y'all are understanding what the objective is. It's NOT mainly to see when the previous raid ended, but more to know when the cooldown for the next one is over. It would still need approval from a CO to perform the raid, but now it would be easier to know when it could be done.
Instead of getting the time from when the previous raid ended and add 45 minutes, you could just type the command and it would tell you when the cooldown will be over and how many minutes are left.

Like I explained here, and throughout the whole suggestion:

This would add four (or two if combined) commands like "MR Over", "DC Over", "MR Cooldown", and "DC Cooldown".
The first two could only be used by COs to mark the time when the main raid or DC ended.
The third and fourth could be used by any CI member to know when they could do the next raid, and would work like this:

[13:43] CI CO: (! or /) MR Over
MR Over 13:43

[13:53] Any CI member: (! or / MR) cooldown
30 minutes left (14:28)

---

Why?

I think it would make it a little bit easier to know when CI can raid.

 

[Emilia Foddg]

I'm not really sure if y'all are understanding what the objective is. It's NOT mainly to see when the previous raid ended, but more to know when the cooldown for the next one is over. It would still need approval from a CO to perform the raid, but now it would be easier to know when it could be done.
Instead of getting the time from when the previous raid ended, you could just type the command and it would tell you when the cooldown will be over and how many minutes are left.

Ohhh, I see.
+Support
Sure.

 

[CyberRecon]

+Support As a CI CO this would be nice but not needed

 

[Holland]

Suggestion Denied

---

Hi @Fexxyzin ,

Thanks for taking the time to make a server suggestion.

The Content Team has chosen to deny your suggestion due to the following reason(s):

We believe that adding this feature is not necessary.
Raids need to be authorised in the /c comms, which allows us to review the timestamp of the authorisation. The current Discord system provides a more accurate and less tedious way to check cooldowns. If this new feature were implemented, issues could arise because GMOD automatically filters time zones in logs or command logs, among other things.

Your suggestion will now be locked and marked as denied.​