That is just what im guessing the client tag will be(W3XP), but who will be the first one to get a working "Warcraft III: The Frozen Throne" login?  Meaning when the beta is released...

*besides skywing* ;)

to my knowledge SphT was actually the first person to get the war3 beta working....so it might be him :P

[quote]to my knowledge SphT was actually the first person to get the war3 beta working....so it might be him :P[/quote]

I was the first person to support the Battle.net logon server (BNLS). Which, at the time, only supported Warcraft III beta. Skywing figured the Warcraft III logon.

Seeing as I don't believe anyone else has figured the logon for Warcraft III (or, the new logon system), I'd bet that in no time Skywing will have figured out the Warcraft III expansion logon which will very likely use the new logon system. The game is an expansion, so like Starcraft and Brood War's relationship, the logon between the two games will probably be very similar.

As an additive, I don't think there will be a new product for the expansion (i.e., your suggestion: W3XP). If you notice in the current Warcraft III statstring, there is a WORD which has 'W3' - this will probably come in to use when the expansion is released (possibly 'XP'). It will be the identification of expansion from the original game.

I never thought of that...hmm...

Although it would fly in the face of every previous precedent Blizzard has established. Every time there's been an expansion they changed the client tag for it.

ah thanks for clearing that up SphT. I actually thought you reversed engineered the war3 beta to log on it (like Skywing has down with reg War3) my mistake.

Spht:  Before someone has played a ladder game of War3 currently, they display no statstring at all.  So if the client was determined from the statstring, it would be impossible to tell if people are on the expansion or not when they are on new accounts and such.

everybody has a statstring, some of the fields may be null or 0's but there is ALWAYS a statstring.

What SoulTaker means is that a War3 statstring for someone who has played no games consists of '3RAW' and nothing else.

Well, Zakath is correct, so they must either have to change the statstring again, or just have a new client tag which im guessing they will.

i know what he meant, but even with a statstring like that, if they do the same with the expansion, it would be "3EXP" or whatever its gonna be, something to indicate its the expansion game.

Wouldn't putting the expansion tag in the statstring require all clients to be patched? Since atm, they can just add the new icon to the relevant icons.bni and it would be displayed automatically - wearas non-WAR3 clients probably don't check the statstring when assigning icons to WAR3 clients...

Only if a Starcraft user should care whether it is w3 or w3 exp.

They made Starcraft care whether it was D2DV or D2XP...I would guess they'll do the same with War3.

[quote]They made Starcraft care whether it was D2DV or D2XP...I would guess they'll do the same with War3.[/quote]
By the way, Warcraft III already has it's own format for downloadable icons which are based on the contents of a user's statstring.  No, these are not in regular .bni format, nor are they available for previous clients.

I had to use a MPQViewer to view the icons-WAR3.bni, the icon viewer i used can be found at:

http://www.wc3network.com/download.php?cat=1&file=16

What i found in the icons-WAR3.bni is just Game Fixx, and KBK... if you look in war3.mpq, you can find the icons for best race, friends list ect. in the MPQ at:

UI\Widgets\BattleNet\ChatIcons\

Could anyone tell me which .bni file has the lag icons in it?

Hmm...Sky, didn't you say that the lag icons are stored locally? The client (and BinaryChat) just draws as many of them as it needs to when someone joins the channel...

Note that the "built-in" icons are also stored in those same paths.  In case you don't know how MPQs work, it's pretty clear that icons-WAR3.bni is an archive with a higher priority than the default MPQ, and can thus override any icons provided there.

Yes, the lag bars are stored locally.