Jump to content
  • We are looking for staff for the Wiki area!
    If interested please
    click here and select "Documentation Team"

  • WDL File


    WDL files contain a low-resolution heightmap for a world. This is probably what the WoW client uses to draw the solid-colored mountain ranges in the background ('in front of' the sky, but 'behind' the fog and the rest of the scenery). It can also be conveniently used to construct a minimap - however, since no water level information is present, the best guess is 0 (sea level) - this results in some lower-than-sea-level areas being blue on the WoWmapview minimap. Oh well. :)

    • ''Someone told me that the use of WDL files was actually to determine pathing (especially for NPCs). We still need a confirmation on what they're for though. -DG''

    *Chunked structure.

    MWMO, MWID and MODF chunk

    These chunks seem to have been added to every WDL and contain information about low resolution [[WMO]] used to create a silhouette.


    • *'''Filenames for [[WMO]] that appear in the low resolution map.''' Zero terminated strings.


    • *'''List of indexes into the MWMO chunk.'''


    • *'''Placement information for the [[WMO]].''' Appears to be the same 64 byte structure used in the [[WDT]] and [[ADT]] MODF chunks.

    MAOF chunk

    • *'''Map Area Offset.'''
    • Contains 64*64 = 4096 unsigned 32-bit integers, these are absolute offsets in the file to each map tile's MapAreaLow-array-entry. For unused tiles the value is 0.
    • /*000h*/ UINT32 areaLowOffsets[4096];
    • ''or''
    • /*000h*/ UINT32 areaLowOffsets[64][64];

    MapAreaLow array

    MARE chunks

    • *'''Map Area'''

    Heightmap for one map tile. Contains 1717 + 1616 = 545 signed 16-bit integers. So a 17 by 17 grid of height values is given, with additional height values in between grid points. Here, the "outer" 17x17 points are listed (in the usual row major order), followed by 16x16 "inner" points. The height values are on the same scale as those used in the regular height maps.

    MAHO chunks

    After each MARE chunk there follows a MAHO (MapAreaHOles) chunk. It may be left out if the data is supposed to be 0 all the time.

    It's an array of 16 shorts. Each short is a bitmask. If the bit is not set, there is a hole at this position.

    User Feedback

    Recommended Comments

    There are no comments to display.

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy Terms of Use