[diablo 3 MPQ] DRLGParams from worlds

[Valtharak]

Any of you were able to read the DRLGParams from the Worlds sno? i always get 0 item.

and this without using the patchs. i know they blanked the value in some later patch but they should show when not using any patch.

Need those to know where random generated worlds portal go to and so on for my pathing.

Any help on this would be welcome.

[Nesox]

Take a look at 0xA065A0, it seems to initialize the world when you enter a new one, it also set's the SNOPower/Levelarea.
First paramter is the SNOWorld

The World sno files in memory doesn't seem to have any pointer to the DRLG parameters, it's probablly being sent from the server when you enter a new area now.
Haven't looked at the files but i think they stopped storing the parameters in the world sno files a few patches ago.

It's called from their "DispatchServerMessage" func too:

    case 0x3A:
      if ( sub_A05460(message->dword8) )
        goto LABEL_491;
      InitializeClientWorld(
        v5->dwordC,                             // SNOWorld
        v5->dword8,                             
        1,
        LODWORD(v5->float10),
        v5->dword14,
        v5->dword18,
        v5->dword1C,
        v5->dword20,
        v5->dword24);
      return 1;

I guess 0x3A is the "EnteredWorld" opcode.

[Valtharak]

I don't think the server has to send the DRLGInfo. they just have to send the scene with there position and rotation. i think the DRLG info is more the definition of how to build up a random world. the end result is just a set of scene positioned and rotated in different ways that the server can send.

i just need the info to get the World/levelarea portal info for the Entrance and Exit of each worlds. I guess i'll mess a bit with it or ask on mooege forum they might have more idea since they were able to get them in the old patch files.

[Nesox]

I don't think the server has to send the DRLGInfo. they just have to send the scene with there position and rotation. i think the DRLG info is more the definition of how to build up a random world. the end result is just a set of scene positioned and rotated in different ways that the server can send.

i just need the info to get the World/levelarea portal info for the Entrance and Exit of each worlds. I guess i'll mess a bit with it or ask on mooege forum they might have more idea since they were able to get them in the old patch files.

I took a look how mooege reads them, they are store in the mpqdata.db sqlite file
http://dl.dropbox.com/u/4381027/ehl305pc.jpg

They probablly dumped them when the *.wrl files still contained all the DRLG parameters or something.
If you only want the Destination World/LevelArea of a portal/MarkerSet they can be found in the MarkerSetSNO.

[Valtharak]

If you only want the Destination World/LevelArea of a portal/MarkerSet they can be found in the MarkerSetSNO.

Ya i already do that for static worlds. But don't think dynamic world have scenechunk to get the actor and such. you would need the DRLGparams to know what scene are present and get the portal info from the scene.

Ill dig more into that this weekend.

[Nesox]

Ya i already do that for static worlds. But don't think dynamic world have scenechunk to get the actor and such. you would need the DRLGparams to know what scene are present and get the portal info from the scene.

Ill dig more into that this weekend.

Hmm ok, let me know how it goes

[Valtharak]

Ok i figured how to read DRLGParams data from the unpatched World MPQ. at the end of the World.cs comment out the int6 since that's the offset for the tiles and read the DRLGParams as an object and not a serializable list just add a constructor to DRLGParams that call read . this work for unpatched MPQ not patched mpq. i still see data in patched mpq like commands but it's positioned differently, gonna dig some more.

Edit: ok ya the data gone in patched MPQ so might aswell use Mooege dumped data. but atleast i know how to get them :P gonna suck for act 2 3 4. we wont have the DRLGParams for those if they are not in MPQ now

stream.Position += 4;
Float0 = stream.ReadValueF32();
Int5 = stream.ReadValueS32();
SNOScript = stream.ReadValueS32();
//Int6 = stream.ReadValueS32();
DRLGParamsTest = new FileFormats.DRLGParams(stream);
stream.Close();

[Nesox]

Ok i figured how to read DRLGParams data from the unpatched World MPQ. at the end of the World.cs comment out the int6 since that's the offset for the tiles and read the DRLGParams as an object and not a serializable list just add a constructor to DRLGParams that call read . this work for unpatched MPQ not patched mpq. i still see data in patched mpq like commands but it's positioned differently, gonna dig some more.

Edit: ok ya the data gone in patched MPQ so might aswell use Mooege dumped data. but atleast i know how to get them :P gonna suck for act 2 3 4. we wont have the DRLGParams for those if they are not in MPQ now

stream.Position += 4;
Float0 = stream.ReadValueF32();
Int5 = stream.ReadValueS32();
SNOScript = stream.ReadValueS32();
//Int6 = stream.ReadValueS32();
DRLGParamsTest = new FileFormats.DRLGParams(stream);
stream.Close();

Ok, well then we have to hook the func that is responsible for it and get the parameters when the level generation is done at runtime

[Valtharak]

D3 is different then D2 in the way scenes are streamed by the server. you only have scene in memory that are around you. if you move it unload scene too far away. so there no level generation thing like in D2 and since there is no lan play they do need to have this code in. it's all server side. all they have to do is send you this and that scene when you get close.

Also mooege doesn't unload the scene like live do. had to change my code a bit to copy the memory when adding it to my scene listing rather then refer to it with a pointer. When i would move it would no longer point to the right scene.

as for the DLRGParam. for the random generated world, mostly dunjon, all you need is to know the entrance and exit. your pathing will require a Explore and find X scene (the exit) logic to move from level to level till you reach your destination. for static world it's easy i preload the scene since i know where they are. i just flag them as explored when i walk by and since some of the scenes have sub scenes that are random, i can delete the one that will not be used in that game. some of the waypoint have different place they can spawn in a levelarea.

Unless someone found some way to predict a world layout with a seed like D2, i'm all ears.

The empty part of the map are random generated from a select set of scenes from the World SceneClusterSet values