Did something change on the account creation on WaR3/TFT? I can no longer make accounts using bnls. I checked on EC and Stealth and they both cant do it. When will be it fixed?

Believe your recieving status code 0x0e in 0x54. I believe this means the client *must* send 0x59 (set email address) before preceeding. After sending 0x59, procede to enter chat

Edit: 100% positive

O so now war3 also have the email thing. cool

Just register an e-mail for your account and you'll be able to log in fine.

thank you UserLoser and Spht

Edit:
+1 for both or you

You can ignore this id and just continue as if it were 0(success). You do not need *need* to send 0x59.

That may be true. However, note that the official clients bring you to an e-mail registration prompt whenever you're registering an account. However, as the only *actual* login confirmed message received is 0x00, it would be intelligent to send 0x59.

I just changed my verbyte to 0x0D and it works :)

[quote author=DaRk-FeAnOr link=board=17;threadid=4297;start=0#msg36100 date=1071711500]
I just changed my verbyte to 0x0D and it works :)
[/quote]

I think it's been shown already that the server doesn't always send 0x0000000e response to the client if you havn't registered your email already. Yesterday, when the patch was released I (and hundreds of others) were logging on fine getting an 0x0 response, then all of a sudden at around 8-8:30~ central time this started to first show up

[quote author=UserLoser. link=board=17;threadid=4297;start=0#msg36108 date=1071712651]
[quote author=DaRk-FeAnOr link=board=17;threadid=4297;start=0#msg36100 date=1071711500]
I just changed my verbyte to 0x0D and it works :)
[/quote]

I think it's been shown already that the server doesn't always send 0x0000000e response to the client if you havn't registered your email already. Yesterday, when the patch was released I (and hundreds of others) were logging on fine getting an 0x0 response, then all of a sudden at around 8-8:30~ central time this started to first show up
[/quote]

Maybe this means they just enabled it? They probably won't turn it off now that it is on.

[quote author=Maddox link=board=17;threadid=4297;start=0#msg36141 date=1071722040]
[quote author=UserLoser. link=board=17;threadid=4297;start=0#msg36108 date=1071712651]
[quote author=DaRk-FeAnOr link=board=17;threadid=4297;start=0#msg36100 date=1071711500]
I just changed my verbyte to 0x0D and it works :)
[/quote]

I think it's been shown already that the server doesn't always send 0x0000000e response to the client if you havn't registered your email already. Yesterday, when the patch was released I (and hundreds of others) were logging on fine getting an 0x0 response, then all of a sudden at around 8-8:30~ central time this started to first show up
[/quote]

Maybe this means they just enabled it? They probably won't turn it off now that it is on.
[/quote]

Maybe this means it's already been proven that it was disabled after it was enabled previously - Unless Feanor is making this up, and did send 0x59 and happens to be lost somehow

[quote author=UserLoser. link=board=17;threadid=4297;start=0#msg36195 date=1071765946]
[quote author=Maddox link=board=17;threadid=4297;start=0#msg36141 date=1071722040]
[quote author=UserLoser. link=board=17;threadid=4297;start=0#msg36108 date=1071712651]
[quote author=DaRk-FeAnOr link=board=17;threadid=4297;start=0#msg36100 date=1071711500]
I just changed my verbyte to 0x0D and it works :)
[/quote]

I think it's been shown already that the server doesn't always send 0x0000000e response to the client if you havn't registered your email already. Yesterday, when the patch was released I (and hundreds of others) were logging on fine getting an 0x0 response, then all of a sudden at around 8-8:30~ central time this started to first show up
[/quote]

Maybe this means they just enabled it? They probably won't turn it off now that it is on.
[/quote]

Maybe this means it's already been proven that it was disabled after it was enabled previously - Unless Feanor is making this up, and did send 0x59 and happens to be lost somehow
[/quote]

I doubt they will turn it off now that its on that would depelt the purpose of even updating warcraft 3 and make the time they spent doing it pointlessly wasted and as we know big companys dont like to waste money.

[quote author=-MichaeL- link=board=17;threadid=4297;start=0#msg36220 date=1071776099]
[quote author=UserLoser. link=board=17;threadid=4297;start=0#msg36195 date=1071765946]
[quote author=Maddox link=board=17;threadid=4297;start=0#msg36141 date=1071722040]
[quote author=UserLoser. link=board=17;threadid=4297;start=0#msg36108 date=1071712651]
[quote author=DaRk-FeAnOr link=board=17;threadid=4297;start=0#msg36100 date=1071711500]
I just changed my verbyte to 0x0D and it works :)
[/quote]

I think it's been shown already that the server doesn't always send 0x0000000e response to the client if you havn't registered your email already. Yesterday, when the patch was released I (and hundreds of others) were logging on fine getting an 0x0 response, then all of a sudden at around 8-8:30~ central time this started to first show up
[/quote]

Maybe this means they just enabled it? They probably won't turn it off now that it is on.
[/quote]

Maybe this means it's already been proven that it was disabled after it was enabled previously - Unless Feanor is making this up, and did send 0x59 and happens to be lost somehow
[/quote]

I doubt they will turn it off now that its on that would depelt the purpose of even updating warcraft 3 and make the time they spent doing it pointlessly wasted and as we know big companys dont like to waste money.
[/quote]
How would it reverse the massive amount of changes made to the game and world editor?