XeNTaX

Nimba explains

So they're using the same for all branches again? Not that getting the dev client would make any difference in-game; you'd just download more stuff and there is still the chance of it not working for the Live (Beta) servers. I'd just extract it and get the BGM again to check if there is anything new anyway...

Well the dev client will 100 percent not work with the Live beta servers. The dev client is what it is, its used by the developers to play and test their content. Though figuring out one of the dev accounts would be interesting but thats another ball game .
Edit: Another strong speculation I have is they they run their own server for the dev client which they test shit on so it would be always online and if you happen to have one of the dev accounts...... anyways.

Ok, since things are getting a bit out of hand, here is some info.

The new cookies are Branch specific. The new cookie I have is only for branch 102. It will not work on any other branch. They have the branch specific numbers in the cookie and the paths are locked to the branch. SO you can no use the cookie I have for anything other than the 102 branch.

Second, no one needs the new cookie except those that work on reversing the DAT file.

I repeat. IT IS USELESS FOR BWE, IT WILL NOT WORK ON BWE. they use different login servers. They are always up, and they are used by the DEVs.

I have given it to a select few people that I know are using it for reverse engineering the DAT file. That is its only purpose atm.

Even I will have to download the new BWE client from scratch because this one wont work.

I will not be updating the scripts. The scripts work 100% fine with the new cookie. Those that have the new cookie, just need to update the script with it.

Second, BWE is in a few days. a good 90% of you dont need the Dev Client. I have turned away many people in the last few days because they think they can just get the cookie from me to download. I do not want us hammering their CDN for Dev client stuff.

Anything that is worth releasing publicly has been released. The new GW2DatBrowser works, and once you get the BWE client, you can use it. The Unpacker kinda works, it will get you some stuff. For a majority of you, that will be plenty.

Hey,

As the patcher does not work for now, I had a question that I can't verify until I have the bwe client.

I did some digging some time ago to understand how to navigate inside the various files in the DAT, I found that a good entry point was the "RootManifest" that you get from the latest query as it points to all the subsequent submanifests, etc, etc..

Now, after fixing the issue with big files for the new unpacker, it seems that I can't find this "RootManifest" in the dat archive.
Does anyone know if the client is always making a query to retrieve it at boot ? I could do it myself but, without the client working I can't check the logic of the outgoing http queries.

Thanks !

Loumie wrote:Hey,

As the patcher does not work for now, I had a question that I can't verify until I have the bwe client.

I did some digging some time ago to understand how to navigate inside the various files in the DAT, I found that a good entry point was the "RootManifest" that you get from the latest query as it points to all the subsequent submanifests, etc, etc..

Now, after fixing the issue with big files for the new unpacker, it seems that I can't find this "RootManifest" in the dat archive.
Does anyone know if the client is always making a query to retrieve it at boot ? I could do it myself but, without the client working I can't check the logic of the outgoing http queries.

Thanks !

Well, the patcher seems to download 2 files when it queries for a new build. it queries /latest, which returns 5 numbers.

build exeFile# exeFileSize unknownFile# and unknownFileSize.

The thing is, when i downloaded the unknownFile it looks kinda like a bare manifest, had some info in it, but it wasnt much, and i thoguht it was either some header or something.

There might be a chance that it is that RootManifest you want. Give me a little bit to grab the latest one, and I will post it here for you to look over and see if it is what you are looking for.

Here is the file. Hopefully it is what you are looking for. Seems to have some kind of Manifest info in it at the bottom. Anyways, GL!

BobSaget wrote:Yes the whole issue is the cookie they dont have routing issues. etc etc etc

...and now that the gateway issue has been fixed your argument is even more invalid.

Nimba wrote:

Loumie wrote:Hey,

As the patcher does not work for now, I had a question that I can't verify until I have the bwe client.

I did some digging some time ago to understand how to navigate inside the various files in the DAT, I found that a good entry point was the "RootManifest" that you get from the latest query as it points to all the subsequent submanifests, etc, etc..

Now, after fixing the issue with big files for the new unpacker, it seems that I can't find this "RootManifest" in the dat archive.
Does anyone know if the client is always making a query to retrieve it at boot ? I could do it myself but, without the client working I can't check the logic of the outgoing http queries.

Thanks !

Well, the patcher seems to download 2 files when it queries for a new build. it queries /latest, which returns 5 numbers.

build exeFile# exeFileSize unknownFile# and unknownFileSize.

The thing is, when i downloaded the unknownFile it looks kinda like a bare manifest, had some info in it, but it wasnt much, and i thoguht it was either some header or something.

There might be a chance that it is that RootManifest you want. Give me a little bit to grab the latest one, and I will post it here for you to look over and see if it is what you are looking for.

Thanks for the file, Nimba!

Yes that's exactly the file I was talking about, it is actually a very important file in term of navigation/categorization in the DAT archive.
I was trying to understand if each time it boots (even if it's up to date) the program retrieves this file or not, as I can't find it in the DAT but only in the latest query.

Finally, for informations, these kinds of files are easy to understand, if you look at the bottom they actually tells you what it is, globally for each "category" (global, maps, languages, etc...) this files points you to the submanifest of these different categories, so it is a really good entry point. (By the way this file is slightly updated compared to the last one I have, maybe because it's DEV version though, the MapEventUnitTests/MapPvpDOTA made me laugh ;D)

So for example here we have:

uint32 buildId = 14049
uint32 manifests = 123

then 123 records of the second struct.. etc...

But I will wait for the bwe client to verify my though, anyway it should be available really soon

Cheers!

Edit: By the way, if someone is working on this (I'm more interested in actual game data more than textures/sounds) and wants to team-up, let me know via PM ;D
I'm looking at the txtm file for now, to see how they map the strs files~

http://cloudfront.guildwars2.com/pVRS48 ... 1J/Gw2.zip

Beta client. It works again. Run it and it will update itself to the new one that will work for bwe

kthackeray wrote:

BobSaget wrote:Yes the whole issue is the cookie they dont have routing issues. etc etc etc

...and now that the gateway issue has been fixed your argument is even more invalid.

What routing issues?..... They just enabled the old auth cookie again. There were never any routing issues.

So "old" NDA-Beta client works =)
patience was the key

BobSaget wrote:What routing issues?..... They just enabled the old auth cookie again. There were never any routing issues.

salamando wrote:When I try to grab the 101 client...
502 - Web server received an invalid response while acting as a
gateway or proxy server. There is a problem with the page you are
looking for, and it cannot be displayed. When the Web server (while acting as a
gateway or proxy) contacted the upstream content server, it received an invalid
response from the content server.

Keep telling yourself that.

Loumie wrote:Does anyone know if the client is always making a query to retrieve it at boot ?

If the build matches the latest query, it just launches the game and doesn't look at either manifest.

Loumie wrote:I'm looking at the txtm file for now, to see how they map the strs files~

The strs files themselves are actually pretty interesting. Using the same format as the original game.

kthackeray obviously if I recieved that error thats another story. But I never ever had issues connecting to their server at any time, I would know I query the branchs every 30 minutes for any modified exe. I bet most of the people never got a 502. Just because you or someone else was having issues doesnt mean everyone else is.
Edit: And dont forget you dont directly connect to arenanetworks.com, depending on your location you get bounced to a "patch server" for better speeds.

BobSaget wrote:Edit: And dont forget you dont directly connect to arenanetworks.com, depending on your location you get bounced to a "patch server" for better speeds.

kthackeray wrote:As for the public one, the valid cookie only tells the Akamai mirror to forward the request to the origin server and that is what is happening here.

Not sure why you bring up things that have already been covered in the thread.

It actually just happened to them again though. They could use a few pointers when it comes to load balancing.