Question about my account being banned for code 045

Hi there, I recently just logged on to find my account was banned for third party program usage. :-( I know for sure I had nothing to do with that, I guess I could've been seen as a bot for doing some LB points grind out of Basion or grinding a certain spot for xp on my Legendary survivor war.. but eh.

I was wondering if someone can send me a link/steps on how to contact/send an email to Anet to hopefully get my account unbanned. I never was banned for anything on my account, and not too sure how I would contact them. Any help is much appreciated, I'm a pretty big GW addict and would hate to have to get another account or quit!

Guildwars.com, support.

Guild Wars Support

Click on that link. Choose the Support For your Region. it will take you to the PlayNC Support place, where you can fill out a ticket.
By doing that, just click on CONTACT SUPPORT and at the Bottom of the Page there should be something that says "Not finding what you are looking for? Ask a Question. Click that. Fill that out as detailed as possible and explain your situation. They will look into the matter and you should get a response from them (hopefully for the better). Hope that helps.

If that is too much to do and you don't want to read all that then just use this link and fill out a Ticket Ask a Question

Thanks a lot for the responses, I sent my question.

And I apologize as this is probably the one millionth question about account being banned, was just a little panicky. :-P This topic can be closed please!

If they reject you the first time, keep trying until they fix it (assuming you really are innocent )

Just took one email, well two. To confirm what chars were on account I suppose. But I got a reply like 10 mins after I sent the first one, few mins after next one. It appeared my account was blocked in error. So I'm back in action! Go support team!

*goes off to give away free things*

And the last person I heard that happened to, got banned a second time. Then NC claimed it wasn't in error that time. It took Gaile to sort it out.

Issue's been resolved, so

Thread Closed.