Leaderboard

Can't wait to leave the clan after a few years of sitting around and then drag other peoples lives down with me. #HypeSquad!

In-Game Name Kiriy Division Team Fortress 2 Previous Member No Identity https://steamcommunity.com/id/kiriythememelord/ Age 17 Previously Banned Yes Time Active on Servers 287+ hours Reason for Joining I want to help the Xeno Gamers community grow and feel that I have improved greatly since previous applications and bans. I wish to help add content to XG servers, especially maps as I enjoy making team fortress 2 maps as a hobby and love recreating old maps .maybe even get staff in the future if I am ever able to prove myself worthy. I hope to prove myself worthy of the xg tags even more after I am accepted.

+1 filters out the peanuts in the server

In the future, please post last ct suggestions to this thread

The ban will stand, 2 days is fairly reasonable for multiple rules broken. Also, banning after the fact is perfectly acceptable, and chat logs show he explained it immediately. As @TheSupremePatriotsaid, if you aren't totally familiar with the rules, maps or jailbreak in general, try to stay off CT and use these 2 days to try and become a little more familiar with the rules.

Just wanted to throw my two cents onto this one sentence. If you are new you really shouldn’t have been on CT until you learned the ropes from listening to CT’s and Wardens provide orders for some time, also you should’ve read the rules and guide before joining CT considering how many rules, steps, and information you need to know to correctly perform the role without breaking rules in the process. No vouch.

I was the other staff member on during the bit where he was playing as warden on clouds. With the amount of rules that were bent and broken I feel like a 2 day team ban is very, very gracious. I will not go into much depth because I was not there when the actual ban was issued on Nexzoid, but I saw enough on Clouds before I had to disconnect. First of all, I would say at least once per round he was in knifing distance of the T's, luckily the T's were giving him a chance and often didn't rush him, but he was killed here and there. Yes there were warnings in voice chat to stay away from the T's and stop baiting by myself and by many of the other players on the server who were getting angry because of it, also I did issue a few slays against him when it got too bad, yet the baiting continued for as long as I was on. Also, he was very quick to shoot as warden. There were many instances were people had asked for repeats and they were killed before a repeat was issued, also here and there T's were killed a mere 1-2 seconds after commands were given. Even more than this sometimes he completely freekilled whether not hearing other wardens commands correctly or moving while shooting and hitting multiple T's. In the 30 minutes or so that I was on the server I remember being randomly freekilled by him 2 times at least and I know other people suffered similar fates. I was personally going to ban him earlier, but me and @MinerTeddy talked a bit more and we decided to be gracious and give him a few more chances. That is what brings us here, after I left I guess he slipped up some more and was banned. With every slip up and freekill that happened I believe 2 days is about the nicest thing that could of been done for him. This ban was well deserved and once again... Its only 2 days, read the rule book once or twice and watch some other players play warden.

@Bot for a witness on clouds @char was freekilled @Genocide was a CT on clouds CT_Slay3r or however it is spelled witnessed a large amount of issues as well. In regards to the swapping and banning, I was just being an idiot with the command and swapped on accident. The 2 day team ban was intended and, as I have explained, was the result of many complains regarding freekilling, baiting, and inexperienced wardening. I (verbally) told CTs multiple times to look at the rules, elaborate better on their commands, and to stop baiting. @Bot also used all chat to make a notice about CTs killing many Ts early on in the rounds and stated that they must be clear with their orders. That means you likely baited for a quarter of your playtime? On Nexzoid you also started as a CT, got swapped to T through autoswap for the guard ratio, and then got re-swapped to CT due to an error. That's still baiting. Throughout the maps you, again as I have said, ran near/adjacent to groups of terrorists. You didn't go down and rules for the dive context, actually. You only stated that "we are taking the first three Ts to the cyan pool," without having stated that we must dive, so we just ran to the cyan pool and froze. The freekill was handled by Bot, but the main issue is how consistently you've had close encounters with your back turned to Ts. For the first incident, I repeated in all chat that it was a freeday and slayed you for freekilling a T who was out. You literally said "Let's thin down the numbers a bit" and killed a T, along with ShiftyKeki, while those terrorists were obeying the afk freeze order. You also fail to mention that I gave verbal warnings on baiting and armory ledge camping, told you not to instruct a T to break down a vent (the plywood on summer), and called out your favoritism during a game of four corners. I repeated multiple times on Nexzoid the reasons for which you were banned, listed instances of your baiting, freekilling, and rulebreaking, and literally gave you the link to the forums for your protest. As I have stated, 2 days was fairly lenient for what I observed in spectator for the entire duration of summer jail and while dead for clouds. Usually for minor rule breaking, an hour or more is sufficient for a newer player to the server to become more familiarized with the rules. However, with the warnings provided and amount of complaints/incidences, I used my judgement to issue you a 2 day ban. Edit: Also, baiting does not always result in a knife death (hence why you make it to LR), but you still did a large amount.

this man is loud

+1 demote danny toxic and freekills, perma b4n for n3gat1v3 3n3rgy b1g m3m3 n0 0ne lik