I like your idea but I sadly don't think that this can be implemented properly for various reasons...
ToBeHonest wrote:
Make it so peoples that make an f1 cannot join events, because it's frustrating.
Let's say a player makes an F1 a few minutes before an event starts and no staff member starts to handle it. Should the player be prevented from joining the event? Should the F1 be discarded automatically once the reporter joins an event? Should the player be kicked out of the event once a staff member starts handling their F1? All of these options aren't ideal. Preventing the player from joining the event would be frustrating for them (especially if the player is new and doesen't know that he can't join an even while he has an active F1). Automatically discarding the F1 would mean that potential rule breaks won't be handled properly just because the player wants to get a chance of winning some items / cash. Kicking the player out of the event is even worse in that sense. We don't wanna "punish" or "restrict" players for reporting rule breakers.
ToBeHonest wrote:
Admins should also have access to a tool to kick somebody out of the event, let's say Player A got reported for RDM but upon teleporting him, he instantly goes into the event i can't do anything about it..
But if i have a tool to kick him out of the event, i can teleport him back on my sit and finish it.
Granted, this idea is better than the previous one of automatically preventing / kicking players involved in F1's but it has it's own flaws. I don't think giving admins the ability to kick players out of an event would go well. Surely most admins wouldn't abuse this power and only use it in appropriate situations but there are for sure gonna be a few cases in which admins are gonna accidentally / intentionally use this in unintended circumstances. It's gonna frustrate affected players, prevent them from potentially getting items / cash and cause more work for the lead team. I would personally only make this feature available for lead team members but that would defeat the whole point of your idea.
All in all I don't think that this should be implemented. The additional work and the potential flaws of these implementations just aren't worth it, especially considering this rarely happens.