Arys said:
He lost connection to teamspeak and his ping was spiking. I wasn't the one Robin was in contact with but I'm assuming he saw the ping spike and was shown the disconnect from teamspeak.
Due to those issues he moved to spec, not really sure why or how he didn't crash in-game. He told me he couldn't move and dropped himself, so I was yelling for someone to come in, neither him nor I knew of the rule. Afterwards, Robin steamed one of our guys asking about the drop, and we explained what happened to him.
If you want to punish us for him moving to spectator, I won't throw a fit over it. But we were questioned about it when it took place.
This is pretty much exactly what happened to us. I think there is a tiny problem in the rule set regarding this issue. As of now, if a player doesn't drop from the server, it doesn't matter if he is lagging or dropped from ts, even if we can prove those. We pretty much thought that the admins were using this rule as a broader sense for it's iteration when we saw how it was applied to you guys, since again we do believe the player that you swapped out was having connection issues, just as the player we swapped out, confirmed by the non-action from the referee, since we took that as confirmation to him registering a player of ours was having connections issues and had to swap out.
I think the main problem is caused by the rule being for only a crash from the server, and even then we did comply with the current rule set and not swap a player out on a previous round in the match. On the open map, Thyke had 500 ping for a while(can be confirmed through the stream probably) but we chose to keep him in as he wasn't having issues with ts etc. We will start recording our officials from our end moving forwards so these kinds of conversations are more based on facts, but even then, I think there should be a slight rule change for players that are clearly having issues with the servers, because as of now, there is no way to swap someone out for a connection issue that doesn't cause a server drop. We were focused on the match and the next round, just as you guys were, and since we weren't trying to cheat or anything, after Lidor's problems didn't get resolved, we just chose to swap him out thinking it would be okay in the light of his connection issues, which again, can be proven.
So far the rules are clear, and the only way to fix this issue moving forwards would be through either a slight rule change, or a swift action by the referee. Otherwise, this kinds of backwards decision making, where everyone has a different angle, would be extremely tough. If there was any sort of action or warning by the referee on the server, this issue would have never come to this point.
PS; Thank you to the admin team for taking the issue under review, we are okay with the decision even though it was unfortunate and not entirely our fault, seeing that the other teams are being punished accordingly too. Hopefully moving forwards, in cases that we can prove that a player is having clear connection and technical issues, there would be a way to fix it. All this being said, removing the ban on swapping players mid set could also be an option, as I'm not sure what the rule currently serves for. If the purpose is to "Stop Cheating" as it was suggested in the admin decision, then it doesn't make much sense as of it is since swapping a player/strategy mid set doesn't really cause any cheating as long as the players coming in are a part of the roster. Again, not justifying anything, just making sure that there is a solid rule set with clear purposes.