NBL official admin statement 13.01.2021 Gardekorps vs Rockstars
The fact that 55th had to go into the spec, was not only a decision for balancing but they were not signed up for Wednesday. On Tuesday Rayleigh (55th colonel) and I met on TeamSpeak because he wanted to join the NBL. I had an agreement with him, that he has to ask the other officers, because usually we wanted to play with 3 lines and he would have been the 4th and that, if they agree, start NEXT WEEK. Rayleigh accepted that agreement and told me, that they even wouldn't be there this Wednesday (13.01) because they have another event. But without telling me Rayleigh appeared yesterday. Because the balance was really bad, I send him and his men home, because he wasn't signed up for this match.
Yeah pal this ain’t how it went down. No one knew you wanted this. Hell even our team had invited us to chats, joined our teamspeak and acted as if we where playing on Wednesday. clearly because you must have done something to lead us to believe that. I’m sorry to say but really it was the admins fault that the event went so awful, the 73e or ourselves shouldn’t need to give you second chances. For a supposed ‘comp’ torny as big as this, it needs to be A. Organised better and B. Explained to the participants better, there is too many half-assed rules and because of this the 55th won’t be attending again.
Special thanks to dams. He genuinely tried to make things better. Me and him spent a while in a teamspeak call working out what went wrong and what the admins can do to make things better and tried his best to understand and take onboard things I was saying. He did however say that since we was on the 2lr server he couldn’t tell power fighter to do anything different which I think is shit. If the IVe and the 2lr are co hosting they should have some influence on each other otherwise just host your own tornys separate of each other.
Think another thing to point out is if more than one reg has had an issue, it’s probs the admins fault. Stop blaming everyone else. Your the one clearly doing something wrong and from the looks of thing it was only your event having the issue. The other admins seemed to do fine.
