I have bad news for this channel. He was just playing SCR as a normal day guarding me as a Airlink Shuttle, but then, he left the train when we were leaving Terminal 1. I asked him what happened, he responded "I just got demoted to DS." I told the #All chat this (we were talking in a whisper), and then everyone was saying "What happened, and how?" He had to drive, and then I found something weird. I saw that he was still a GD rank but he couldn't guard. I went to Terminal 3 alone, and went back to Terminal 2. He said he had a channel, and i decided to Subscribe to him as a loss for his GD rank. I had to despawn my train to subscribe, and then i searched up the channel, and found his channel here. Back story : We have no idea what happened. I told a supervisor about what happened, and then they said. "Sorry, I don't understand what you mean, it's probably a bug." I was so confused, and then i asked other people if they knew what happened, but none of them did. Some people asked him to re-read the guide to see what he did wrong. I thought he whistled on a red light, but I was wrong because the OFF indicator was on when he whistled at Terminal 1. We still have no idea what happened. We are not sure what happened, but it's probably one of these reasons : 1 - Whistled on red 2 - Bug 3 - Moderators got confused 4 - Did something wrong (I don't know what) We are sorry for your loss. :( We hope that you can get back to GD as soon as possible!
Yeah It’s Sad This Is Happening Im Wanting To Go To The Training But It Says I Need To Go To The Discord Server To Get The SG Rank But I Can’t Even Guard, I Will Contact the Moderators
@@EChan-i7v it was a signal issue failure and the signaller was wrong he set a Red as there was a Airlink shuttle at T3 But That Wouldn’t Effect Us and the off signal was lit I guess it was a signal and off signal issue also maybe the signaller fault
That was awesome
Thanks A lot!
Also i was there i am thanked you for liking this! my name is rolucap
Beautiful hairday! I am miki!
Hey, thanks!
I have bad news for this channel.
He was just playing SCR as a normal day guarding me as a Airlink Shuttle, but then, he left the train when we were leaving Terminal 1. I asked him what happened, he responded "I just got demoted to DS." I told the #All chat this (we were talking in a whisper), and then everyone was saying "What happened, and how?" He had to drive, and then I found something weird. I saw that he was still a GD rank but he couldn't guard. I went to Terminal 3 alone, and went back to Terminal 2. He said he had a channel, and i decided to Subscribe to him as a loss for his GD rank. I had to despawn my train to subscribe, and then i searched up the channel, and found his channel here.
Back story :
We have no idea what happened. I told a supervisor about what happened, and then they said. "Sorry, I don't understand what you mean, it's probably a bug." I was so confused, and then i asked other people if they knew what happened, but none of them did.
Some people asked him to re-read the guide to see what he did wrong. I thought he whistled on a red light, but I was wrong because the OFF indicator was on when he whistled at Terminal 1. We still have no idea what happened.
We are not sure what happened, but it's probably one of these reasons :
1 - Whistled on red
2 - Bug
3 - Moderators got confused
4 - Did something wrong (I don't know what)
We are sorry for your loss. :( We hope that you can get back to GD as soon as possible!
Yeah It’s Sad This Is Happening Im Wanting To Go To The Training But It Says I Need To Go To The Discord Server To Get The SG Rank But I Can’t Even Guard, I Will Contact the Moderators
I have finally retained my guarding rank and the moderators have patched the bug
@@AlwaysBusIt Did you know what the bug is?
@@EChan-i7v it was a signal issue failure and the signaller was wrong he set a Red as there was a Airlink shuttle at T3 But That Wouldn’t Effect Us and the off signal was lit I guess it was a signal and off signal issue also maybe the signaller fault
@@AlwaysBusIt Ok, so it's probably the signaller's fault, but I thought the signaller was doing a different zone