Told That I have an AASA Ban

[DustyDog]

After playing AA2 for a couple hours, decided to play on a few of my 'alt' characters.  I tried to join =[C]= the Company Clan server and the admin booted me.  So, after finding there web site to find out why, it was 'posted' and says a 'toon' has an AASA ban.  It gave me the following information:

name: [BFG]Dysfunctional
guide:F733B9978396AE5A7DAD4BAA96C39984
last seen: Aug 09, 2009 16:09:12
Current Bans: AASA

then it gives 4 'violations':
3 (MD5TOOL) Violations and a (COMFAIL) #131 Violation

It also shows Other Name:  APE.BRIG.GEN.HITMAN, [BFG]Anarchist.  These are not any of my 'toons' though I do know who it is.  (BTW, the 'toon' I was playing was $pud$, if it helps any.  I would really appreciate you guys looking into this, and look forward to hearing back from you.

[-Chaotic-]

Code: [Select]

[2005-08-09 23:52:25] VIOLATION (CVAR) #9001: frontyardbackyard (slot #x) Cvar KillerBot.MainInteraction AimLocation * = (X=0.000000,Y=0.000000,Z=0.000000) [f733b9978396ae5a7dad4baa96c39984(-) 0.0.0.0:xxxxx]
Is the known cheat violation that account was kicked for.

Whatever other information you have found is not related to AASA - those issues will need to be reported to wherever you found the info.

[DustyDog]

well, my question would be this.  Is it possible that this CVAR violation is from the other person mentioned? APE.BRIG.GEN.HITMAN aka [BFG]Anarchist.  As i rember the only time I was ever banned from a server, we were playing one of the 'new player made' maps.  There was a non-[BFG] member using cheats (was all opfor, had a Hind and a cave) that we had asked numerous times to stop, and he refused.  So we continuously VK'd him, he got someone from the server and they banned us.  Now, I have never used a hack within the game, ever, but I could not say the same thing with [BFG]Anarchist.  Reason I ask, it shows him tied to my account on this ban, at the time, I was playing all my 'toons', why wouldn't it show up on them as well?

[DustyDog]

This is the information that was provided:       
 


 Subject: $pud$   Today at 12:44 am 

--------------------------------------------------------------------------------
 
banned server

Quote:
Current Info
Name: $pud$
GUID: EF742A238DCCBF000FDC2543E2E9DF4F
IP: 76.178.67.217
MAC: 00173124C4XX
Last seen: Feb 09, 2010 23:41:29

Current Bans: None

Previous Info
Other Name: $pud$
Other IPs: 71.223.242.242, 71.223.248.150, 75.167.4.83, 76.178.67.217, 76.178.79.196, 76.178.83.111, 98.145.8.41
Other MACs: 00173124C4XX

Linked Accounts
F733B9978396AE5A7DAD4BAA96C39984
D4CAD83741C73DAA1C07688215969FE9
EF742A238DCCBF000FDC2543E2E9DF4F
9C4A542804F66FABF85530644DE37C75
D63A2E59FD5040F6486F3B8618B69435

Information copyright ©2008 Anticheat Incorporated and Rifle[lame]. All Rights Reserved.
Visit the America's Army Account History page for more great tools.


linked

Quote:
Current Info
Name: [BFG]Dysfunctional
GUID: F733B9978396AE5A7DAD4BAA96C39984
IP: 76.178.79.196
MAC: 00173124C4XX
Last seen: Aug 09, 2009 16:09:12

Current Bans: AASA

Previous Info
Other Name: APE.BRIG.GEN.HITMAN, [BFG]Anarchist, [BFG]Dysfunctional
Other IPs: 71.223.242.242, 71.223.244.120, 71.223.250.157, 75.167.4.83, 75.167.13.143, 75.167.18.118, 76.178.79.196, 76.178.83.111, 76.178.90.5, 210.49.233.147
Other MACs: 00173124C4XX

Linked Accounts
F733B9978396AE5A7DAD4BAA96C39984
D4CAD83741C73DAA1C07688215969FE9
EF742A238DCCBF000FDC2543E2E9DF4F
D63A2E59FD5040F6486F3B8618B69435
9C4A542804F66FABF85530644DE37C75
CEB07DA34A954297CA536EFF4D23ACFC
6927667D7FD98727AE59BCA39BE11C07
969B70E6105E53683184077C021438E3

Violation History
[03.26.2007 17:46:58] |7074| VIOLATION (COMFAIL) #131: [BFG]Dysfunctional (slot #20) PB Client Not Responding [f733b9978396ae5a7dad4baa96c39984(-) 76.178.83.111:3812]

[03.23.2007 09:02:39] |1960| VIOLATION (MD5TOOL) #9002: [BFG]Dysfunctional (slot #2) MD5Tool Mismatch: Maps/SFSnakePlain.aao (len=2048) [f733b9978396ae5a7dad4baa96c39984(-) 76.178.83.111:1893]
[03.23.2007 09:02:39] |1959| MD5Tool ["Maps/SFSnakePlain.aao" SZ65400019 AT0 LEN2048 607B8899CC5FCE1EC7F982C11B10F05F] from (slot# 2) [BFG]Dysfunctional

[03.23.2007 08:56:59] |3149| VIOLATION (MD5TOOL) #9002: [BFG]Dysfunctional (slot #2) MD5Tool Mismatch: Animations/A_AA2_CharactersOpfor.ukx (len=2048) [f733b9978396ae5a7dad4baa96c39984(-) 76.178.83.111:1320]
[03.23.2007 08:56:59] |3148| MD5Tool ["Animations/A_AA2_CharactersOpfor.ukx" SZ4939402 AT0 LEN2048 0BC9037C1A381E27B64960FC58C870EC] from (slot# 2) [BFG]Dysfunctional


Information copyright ©2008 Anticheat Incorporated and Rifle[lame]. All Rights Reserved.
Visit the America's Army Account History page for more great tools.
 
 

[-Chaotic-]

That info isn't necessarily accurate - it is nothing to do with AASA. Will get the actual kick data. With it being an old log this may take a couple of days.

[DustyDog]

np. thank you for taking the time to look into it

[-Chaotic-]

Code: [Select]

[08.09.2005 23:50:44] |4030| Player GUID Computed f733b9978396ae5a7dad4baa96c39984(-) (slot #3) 210.49.234.136:1384 frontyardbackyard
[08.09.2005 23:52:25] |4035| VIOLATION (CVAR) #9001: frontyardbackyard (slot #3) Cvar KillerBot.MainInteraction AimLocation * = (X=0.000000,Y=0.000000,Z=0.000000) [f733b9978396ae5a7dad4baa96c39984(-) 210.49.234.136:1384]
[08.09.2005 23:52:26] |4036| Kick Command Issued (Cvar KillerBot.MainInteraction AimLocation * = (X=0.000000,Y=0.000000,Z=0.000000)) for (3) frontyardbackyard
Is the full log and kick information taken from the original server logs. With this information there is no chance of this being attached to the wrong GUID/Account. At that point in time the account in question was cheated with. Obviously I cannot say if it was you or someone else that was cheating with it, only that it was cheated with.

[-Chaotic-]

Any linking information from that other site in question should be taken with a pinch of salt, however if the above account with that GUID is the one you tried to play with, it was cheated with.

[DustyDog]

Well, I do not really know what to tell you.  No one else played my account, or even this computer but me.  I know I did not hack, so .... the only thing I can/will say is that the data is simply wrong.  -Chaotic-, I sincerely thank you for looking into this matter, and for your prompt and courteous responses.  I have had quite a few laughs out of this, and to those that know me who e-mailed and pm'd, thanks for those laughs as well. As I hardly ever really play anymore as it is, I think I'll just let the matter lie and stop playing AA.  To my friends in AA, good luck and good hunting! 

[usaf_pride]

You can believe what you want. 
 Closed

[DustyDog]

K, bud I don't know what your problem is, maybe mommy didn't breast feed enough or maybe she dropped you on your head not enough, but wtf?  The thread was already closed by -Chaotic-, the issue was over, and you have to re-open it add your little 2 cents, and then close it?  Son, it's not what I think, it's what I know.  You can sit on your little pedestal and think your 'stuff' doesn't stink and all, good for you!  But if you are trying to say that there is NO possible way that anyone is innocent and the data is ALWAYS right you live in La La land.  Let me remind you of what you are 'SUPPOSSED' to be doing, because apperently you seem to have forgotten.  People get banned, they come here to address the issue, you are suppossed to review it and respond to it and say 'yes' or 'no'.  Simple I would think.  But no, you want to use a great tool like AASA and demean it's true purpose as your own 'bashing' instrument, so you can feel good about yourself?  I think your actions here bring great discredit to AASA and the work that it has done in the past.  In parting, I'd like to once again thank -Chaotic- for his hard work and candor in reviewing my appeal, this is in no way against you or your decision.  As for USAF_Pride and his assinine actions, USAF_Pride = pussy in my book. 

Feel free to 'delete', I have spoken
"I'ts not what I believe, it's what I know"


CLOSED

[=ACES=I_pee_freely]

Thanks for the feedback.........now be a good boy or you will find it really hard to appeal your next banned account.