I was on the server today, and I somehow lost both my tags and my Xp. Matasanos advised me I should disable punkbuster, which I did. I disconnected and reconnected several times to see if my tags would come back, but it seemed like the more times I logged on the more stuff I lost! Somehow after my 2nd login the server listed me as a 0 admin, when I am a lvl 50, and I had no aka tags at all.

I'm still an active member of the clan, playing almost daily on the server. Matasanos was present when this occurred on the server, but he was unable to advise me any further. Maybe later when I return to play, it will have restored itself. I've checked again several times since and according to the server I'm still stripped. If anyone knows this is a glitch or if things can be restored, I'd love to have my admin, tags, and xp restored. This could all just be a temporary glitch but it could also have something to do with my punkbuster.

Thanks for your help! All my best, *CKA*Lord*CKA*

Update: Bartman assisted me with getting back my admin and tags, and I have succeeded in maintaining those items (thanks Bartman!). But my XP continues to reset itself everytime I log onto the server. Its also become rather difficult to connect to the server because I keep receiving the same error message: "try reconnecting, if that doesn't work shut down ET and try again." I'm not sure what it says in-game when I can't log on, so I'm STILL not sure what the problem is. All of my program files seem to be in working order.

I spoke with Raider and was told Brutal will take a look into this problem soon. If anyone else can give ideas for how to repair this problem please feel free to contact me. Until then, see you all on the Battlefield and have a great weekend! *CKA*Lord*CKA*

Loordd so you have your pb enabled and you can find your etkey from ETMain folder?

If thats right, then you should get your pb up to date, and this is good program for it:

http://www.evenbalance.com/index.php?page=pbsetup.php

Thanks to Joumiez, Bartman, and Kraus for their help with this problem! It was repaired by performing the update provided in the link above, just in case anyone else runs into this problem.