Duplolas

Can you give us an overview of what happened before you were CT Banned? And by who possibly?

You guys dont need to do anything, it didnt stop and they have located the persons computer through their mac address. So they are gone. They will be found sometime tomorrow :D Hope they like prison.

Hes using multiple ips to do it. So its a DDos.

Im just putting this message out there. After a while I went back and checked my security log I found a single ip out of the lots of ones from different countries and this one came up from Columbia University. 128.59.14.101 If this is your ip, and you go to this college you have less than an hour before your school security calls me back to stop. I dont know if this is a person in our clan, but im just putting this out there so they dont have to get fined/go to jail/get kicked out of their college, because im not a complete faggot, unlike who ever is doing it.

+1 Ban on HaaDron for looking so sexy in his xG profile picture. Its like his 12th offense because ive seen it 12 times.

Im sorry to say that I find this hard to believe. A mod/admin made fun of your name and treatened to ban you and then did after he told you to mass freekill, considering the fact that a perm CT ban is for a mass freekill and then not leaving. Theres either way more to the story than your telling or we got a mod/admin about to be demoted... Do you remember who banned you, who ordered you to kill the T(s), was it the same person who banned you, and the exact reason you got banned for? Also if you give me your ingame name when you were banned ill check the logs.

What was your in game name, i think waiting 3 weeks would be good. Ill check the logs.

I mean being good and hacking are two completely unrealated things. When you hear someone yell hacks because its takibo its probably true, but hes also very good :P You can be really good and still hack or be horrible and hack. Hacking more often happens in people who are bad at the game, but you cant go off that as a argument. Now really quick id like to note that posting 3 times and answering your own questions with a video of you not hacking is kinda suspicious to me. Its not proof for or against you too considering its not of the game you were assumed to be hacking on. I trust shaggy, hes a great admin and so is duke. Theres really no proof against you other than them saying you did. I vote to make it a 2 week ban. Because two admins said you were, but there was no proof against you posted.

What do you guys think? Because when the time comes for us to have a server, it will probably be with only one of these games. DayZ will be using the Arma 3 engine which is good, but it also means delayed patches. WarZ is its own game and will be realeased sooner than DayZ (almost certain on that)

If hes willing to steal money for xG, give it to him. He knows the rules and was a SUPER-ADMIN previously. We should be begging him to just settle for mod. +1

Seems like everyone on the shitlist had been promoted to admin by now. Everyone except me :( Maybe in the next promo-demo. Just maybe I can then rule the world...

And thats great. But it would be good to have things like what you discuss in a actual thread so that everyone could be able to put in their ideas and then actually have something on paper for those punishments. That way, if someone fucks up, they dont have an excuse as to why they did. There will always be some things that will always be up in the air about, but thats how all rules are. Even the Constitution is really just the base rules that we have to follow.

Im sorry if I didn't express it well enough. Imeant this idea as more of a community rep idea. It would be that everyone who took part in the thread would be able to help the mod receive credit for some of the things that they have seen the mod do in the community that others would not. Like say, a member asks for a mod to get on but no one does, he's being trolled and wants a mod to intervene. Some mod who is friends with the player then gets on and helps the member. Because no one was around to see it happen, know one really knows about it. In the end the higher ups have more information to look at before they decide. This helps. It would be more there to commend or make aware of of what they have done. The community wouldn't be the judge of if they got admin or not.

So for awhile now ive been waiting and waiting for both these to be updated. A long time ago in a galaxy far far away, all mods, admins, divs, coleaders, got together and discussed proper punishment times and adding/removeing rules. This has yet to happen. With the increasing number of mods and players on our servers, this really needs to happen soon. With the recent events (you know which ones) even higher-ups are disagreeing with each other. Someone or a group of people needs to sit down and talk about updating it. It needs to be people who play on our servers an average amount and wont give bias upon which team they play as. Im not saying we need a complete revamp of it all, but it needs to be changed. If needed we should have a thread for those mods and up to debate different punishments and times for them, along with changing anything in the motd that might not work as well as it should. Ive been in this community for awhile, not as long as some, but long enough to know that xG is reaching a new stage in its development. New players = more exploits, new mods = more screw ups.

I was thinking about this last night as I realized how many mods we have now. I think we should have a place for Mods to post admin submissions. I know being promoted to admin is really up to the higher-ups, but I think that in some cases, some mods are overlooked. Or in other times, things that have done are overlooked as well, wether they are positive or negative. So member submissions and mod submissions have their own restrictions on who can apply and who can +1 other people. For admins it would be anyone who could. This is so that everyone would be able to voice their opinions before the mod gets promoted, and if the higher-ups are not so sure about a mod being promoted, the community could help with their decisions. Its an idea. I dont know how well it will work because in the end the higher-ups decide, but it would still help in their decisions.

Im mad im not up there lol, but srsly. Zilch should be up there. He constantly ddosed our servers and it was only a 12 YEAR OLD KID! I think zilch should be added.

+1 Obviouslly he is responsible enough if he is a Div. I mean come on! I say give him a chance, if he abused, looses mod and div probably. Honestly, if someone has been in this community long enough, I think anyone should be able to have mod. They should just have to make the decision if they are maturate enough to handle it.

Hey guise! I set up a honey pot ip! So basically all the attacks have swarmed to that dummy ip and little to none are getting to my computer! So ill be playing this weekend!

So, I went around comcast because they wanted to charge me $150 to fix it. And I went into my crawl space, disconnected the main Ethernet line for around 12 hours, and im getting atacked less. So, half full/half empty, have internet, still being atacked. Hopefully ill have this fixed by the weekend.

I would win either way.

You said my voice was nice but told me to stop using HLDJ. APOLOGIZE. jK. Thanks for being awesome.

So, im still waiting on comcast. Only thing they are doing for me is blasting 70s music in my ear. So. Im probably going to be gone for a while guys until this gets fixed.

Apparently I pissed off a whole bunch of post-war communists and a texan.

Heres the log. Help if you can. Security log: Wed Sep 19 06:41:25 2012 =>Found attack from 212.109.49.206. Source port is 8844 and destination port is 22 which use the TCP protocol. Wed Sep 19 06:51:44 2012 =>Found attack from 79.140.235.235. Source port is 42521 and destination port is 23 which use the TCP protocol. Wed Sep 19 07:18:04 2012 =>Found attack from 1.202.148.70. Source port is 39523 and destination port is 5900 which use the TCP protocol. Wed Sep 19 08:04:03 2012 =>Found attack from 221.123.162.77. Source port is 6000 and destination port is 6666 which use the TCP protocol. Wed Sep 19 08:41:45 2012 =>Found attack from 58.218.199.250. Source port is 12200 and destination port is 9090 which use the TCP protocol. Wed Sep 19 08:41:45 2012 =>Found attack from 58.218.199.250. Source port is 12200 and destination port is 808 which use the TCP protocol. Wed Sep 19 08:51:02 2012 =>Found attack from 64.31.45.61. Source port is 12200 and destination port is 6515 which use the TCP protocol. Wed Sep 19 08:51:02 2012 =>Found attack from 64.31.45.61. Source port is 12200 and destination port is 36081 which use the TCP protocol. Wed Sep 19 08:51:02 2012 =>Found attack from 64.31.45.61. Source port is 12200 and destination port is 8123 which use the TCP protocol. Wed Sep 19 09:12:13 2012 =>Found attack from 58.218.199.227. Source port is 12200 and destination port is 8085 which use the TCP protocol. Wed Sep 19 09:12:13 2012 =>Found attack from 58.218.199.227. Source port is 12200 and destination port is 9000 which use the TCP protocol. Wed Sep 19 09:12:13 2012 =>Found attack from 58.218.199.227. Source port is 12200 and destination port is 2479 which use the TCP protocol. Wed Sep 19 09:26:40 2012 =>Found attack from 74.55.87.138. Source port is 35100 and destination port is 25 which use the TCP protocol. Wed Sep 19 09:50:56 2012 =>Found attack from 201.57.40.70. Source port is 28830 and destination port is 22 which use the TCP protocol. Wed Sep 19 10:20:53 2012 =>Found attack from 64.31.45.58. Source port is 12200 and destination port is 6515 which use the TCP protocol. Wed Sep 19 10:20:53 2012 =>Found attack from 64.31.45.58. Source port is 12200 and destination port is 36081 which use the TCP protocol. Wed Sep 19 10:20:53 2012 =>Found attack from 64.31.45.58. Source port is 12200 and destination port is 8123 which use the TCP protocol. Wed Sep 19 11:07:23 2012 =>Found attack from 222.236.46.212. Source port is 6000 and destination port is 3389 which use the TCP protocol. Wed Sep 19 11:07:53 2012 =>Found attack from 122.228.161.226. Source port is 4935 and destination port is 3389 which use the TCP protocol. Wed Sep 19 11:16:39 2012 =>Found attack from 14.8.249.132. Use the ICMP protocol. Wed Sep 19 11:29:33 2012 =>Found attack from 71.209.231.129. Source port is 3265 and destination port is 23 which use the TCP protocol. Wed Sep 19 11:42:27 2012 =>Found attack from 210.5.153.130. Source port is 4935 and destination port is 3389 which use the TCP protocol. Wed Sep 19 11:45:01 2012 =>Found attack from 58.218.199.250. Source port is 12200 and destination port is 27977 which use the TCP protocol. Wed Sep 19 11:45:01 2012 =>Found attack from 58.218.199.250. Source port is 12200 and destination port is 2301 which use the TCP protocol. Wed Sep 19 11:45:01 2012 =>Found attack from 58.218.199.250. Source port is 12200 and destination port is 7212 which use the TCP protocol. Wed Sep 19 11:50:42 2012 =>Found attack from 59.127.188.37. Source port is 2024 and destination port is 23 which use the TCP protocol. Wed Sep 19 11:51:43 2012 =>Found attack from 64.31.29.59. Source port is 12200 and destination port is 6515 which use the TCP protocol. Wed Sep 19 11:51:43 2012 =>Found attack from 64.31.29.59. Source port is 12200 and destination port is 36081 which use the TCP protocol. Wed Sep 19 11:51:43 2012 =>Found attack from 64.31.29.59. Source port is 12200 and destination port is 8123 which use the TCP protocol. Wed Sep 19 11:53:46 2012 =>Found attack from 71.38.115.209. Source port is 1952 and destination port is 23 which use the TCP protocol. Wed Sep 19 12:03:34 2012 =>Found attack from 58.218.199.227. Source port is 12200 and destination port is 2479 which use the TCP protocol. Wed Sep 19 12:03:34 2012 =>Found attack from 58.218.199.227. Source port is 12200 and destination port is 8000 which use the TCP protocol. Wed Sep 19 12:13:54 2012 =>Found attack from 71.208.38.16. Source port is 4384 and destination port is 23 which use the TCP protocol. Wed Sep 19 12:22:09 2012 =>Found attack from 222.236.46.212. Source port is 6000 and destination port is 3389 which use the TCP protocol. Wed Sep 19 12:23:41 2012 =>Found attack from 213.111.233.132. Use the ICMP protocol. Wed Sep 19 12:36:04 2012 =>Found attack from 64.31.29.58. Source port is 12200 and destination port is 6515 which use the TCP protocol. Wed Sep 19 12:36:04 2012 =>Found attack from 64.31.29.58. Source port is 12200 and destination port is 36081 which use the TCP protocol. Wed Sep 19 12:36:04 2012 =>Found attack from 64.31.29.58. Source port is 12200 and destination port is 8123 which use the TCP protocol. Wed Sep 19 13:41:40 2012 =>Found attack from 220.181.168.156. Source port is 6000 and destination port is 1433 which use the TCP protocol. Wed Sep 19 13:49:56 2012 =>Found attack from 184.164.150.13. Source port is 48641 and destination port is 65533 which use the TCP protocol. Wed Sep 19 14:00:46 2012 =>Found attack from 93.37.144.237. Source port is 4219 and destination port is 25 which use the TCP protocol. Wed Sep 19 14:01:16 2012 =>Found attack from 93.37.144.237. Source port is 4219 and destination port is 25 which use the TCP protocol. Wed Sep 19 14:02:17 2012 =>Found attack from 64.31.29.60. Source port is 12200 and destination port is 6515 which use the TCP protocol. Wed Sep 19 14:46:42 2012 =>Found attack from 58.218.199.250. Source port is 12200 and destination port is 9000 which use the TCP protocol. Wed Sep 19 14:46:42 2012 =>Found attack from 58.218.199.250. Source port is 12200 and destination port is 8088 which use the TCP protocol. Wed Sep 19 14:46:42 2012 =>Found attack from 58.218.199.250. Source port is 12200 and destination port is 8008 which use the TCP protocol. Wed Sep 19 14:46:42 2012 =>Found attack from 64.31.29.62. Source port is 12200 and destination port is 6515 which use the TCP protocol. Wed Sep 19 14:46:42 2012 =>Found attack from 64.31.29.62. Source port is 12200 and destination port is 36081 which use the TCP protocol. Wed Sep 19 14:46:42 2012 =>Found attack from 64.31.29.62. Source port is 12200 and destination port is 8123 which use the TCP protocol. Wed Sep 19 14:55:29 2012 =>Found attack from 58.218.199.227. Source port is 12200 and destination port is 8085 which use the TCP protocol. Wed Sep 19 14:55:29 2012 =>Found attack from 58.218.199.227. Source port is 12200 and destination port is 2479 which use the TCP protocol. Wed Sep 19 14:55:29 2012 =>Found attack from 58.218.199.227. Source port is 12200 and destination port is 9090 which use the TCP protocol. Wed Sep 19 15:01:40 2012 =>Found attack from 50.9.134.250. Source port is 4935 and destination port is 3389 which use the TCP protocol. Wed Sep 19 15:30:35 2012 =>Found attack from 27.122.12.130. Source port is 14129 and destination port is 22 which use the TCP protocol. Wed Sep 19 16:07:45 2012 =>Found attack from 77.222.40.20. Source port is 2969 and destination port is 22 which use the TCP protocol. Wed Sep 19 16:10:49 2012 =>Found attack from 116.6.210.181. Source port is 10852 and destination port is 5900 which use the TCP protocol. Wed Sep 19 16:20:06 2012 =>Found attack from 64.31.29.61. Source port is 12200 and destination port is 6515 which use the TCP protocol. Wed Sep 19 16:20:06 2012 =>Found attack from 64.31.29.61. Source port is 12200 and destination port is 36081 which use the TCP protocol. Wed Sep 19 16:20:06 2012 =>Found attack from 64.31.29.61. Source port is 12200 and destination port is 8123 which use the TCP protocol. Wed Sep 19 16:36:36 2012 =>Found attack from 142.217.7.61. Source port is 51343 and destination port is 3389 which use the TCP protocol. Wed Sep 19 16:56:12 2012 =>Found attack from 87.106.31.37. Source port is 3389 and destination port is 3389 which use the TCP protocol. Wed Sep 19 17:01:52 2012 =>Found attack from 195.244.62.206. Source port is 4935 and destination port is 3389 which use the TCP protocol. Wed Sep 19 17:01:52 2012 =>Found attack from 60.190.63.62. Source port is 36801 and destination port is 25 which use the TCP protocol. Wed Sep 19 17:05:28 2012 =>Found attack from 64.31.29.59. Source port is 12200 and destination port is 6515 which use the TCP protocol. Wed Sep 19 17:05:28 2012 =>Found attack from 64.31.29.59. Source port is 12200 and destination port is 36081 which use the TCP protocol. Wed Sep 19 17:05:28 2012 =>Found attack from 64.31.29.59. Source port is 12200 and destination port is 8123 which use the TCP protocol. Wed Sep 19 17:25:06 2012 =>Found attack from 70.36.101.50. Source port is 30664 and destination port is 3389 which use the TCP protocol. Wed Sep 19 17:29:13 2012 =>Found attack from 117.211.92.122. Source port is 22186 and destination port is 22 which use the TCP protocol. Wed Sep 19 17:48:19 2012 =>Found attack from 58.218.199.227. Source port is 12200 and destination port is 9415 which use the TCP protocol. Wed Sep 19 17:48:19 2012 =>Found attack from 58.218.199.227. Source port is 12200 and destination port is 9000 which use the TCP protocol. Wed Sep 19 17:48:19 2012 =>Found attack from 58.218.199.227. Source port is 12200 and destination port is 8000 which use the TCP protocol. Wed Sep 19 17:49:51 2012 =>Found attack from 58.218.199.250. Source port is 12200 and destination port is 9415 which use the TCP protocol. Wed Sep 19 17:49:51 2012 =>Found attack from 58.218.199.250. Source port is 12200 and destination port is 9000 which use the TCP protocol. Wed Sep 19 17:49:51 2012 =>Found attack from 58.218.199.250. Source port is 12200 and destination port is 8000 which use the TCP protocol. Wed Sep 19 17:53:27 2012 =>Found attack from 64.31.45.62. Source port is 12200 and destination port is 6515 which use the TCP protocol. Wed Sep 19 17:53:27 2012 =>Found attack from 64.31.45.62. Source port is 12200 and destination port is 36081 which use the TCP protocol. Wed Sep 19 17:53:27 2012 =>Found attack from 64.31.45.62. Source port is 12200 and destination port is 8123 which use the TCP protocol. Wed Sep 19 17:54:59 2012 =>Found attack from 222.240.166.9. Source port is 37627 and destination port is 21 which use the TCP protocol. Wed Sep 19 18:05:49 2012 =>Found attack from 66.197.134.79. Source port is 6000 and destination port is 3389 which use the TCP protocol.

@@GoatFace LOL no. Also, he doesnt want to pay for a game prone to breaking every hour, because that means a lot more work, and the money can go to better things. He waited like 3 months to try this a second time. So dont expect to get one until warz or dayz comes out.