https://elijahketchersid.com/forums/ Wed, 13 May 2026 14:23:02 +0000 MyBB https://elijahketchersid.com/forums/thread-33.html Tue, 28 Oct 2025 13:28:51 +0000 rektbyfaith]]> https://elijahketchersid.com/forums/thread-33.html Disclaimer.
Depending on what you want to do this can get very far from being user friendly, convenient or devoid of problems, modern clients are complicated and are not as well documented as 3.3.5. The guide itself is pretty basic since I'm sure more convenient tools will come with time. I will try to update this as the knowledge of the community grows, more tools become available.
If you are familiar with WoW modding skip to the ADT and WDT sections 2 and 3.

I.  Essential things to understand and the basics of clientside WoW modding.

a) WoW file formats and general terminology

ADT - tiles with terrain and object information on a map grid. Example to visualize.
WDT - a file that specifies how and which ADT map tiles should be loaded on a 64x64 grid. Example to visualize.
WDL - low level of detail height map that forms the "horizon mountains", is generated for each ADT map tile present. Example to visualize.
M2 - small static objects, spell and particle effects, animated models.
WMO - bigger static objects, can have M2 files in them (think M2 chairs in a WMO house).
BLP - texture files.
GroundEffects - also called Detail Doodads, if properly set up they render additional small M2s on ground textures.
GameObject - a serverside object that your client is told to render in a particular location.

b) Simplified differences in clients from 3.3.5 to 8.1+

MPQ vs CASC - WoW clients use archives to store their data. In wrath the type of archive is called MPQ, starting with WoD blizzard transitioned to CASC. Changes how the files are stored, changed and added.
FileDataID - a unique id of a file in the game data.
Listfile - a list of files and their FileDataID.
-On 3.3.5 the client reads files looking for references to particular paths in the MPQ archive.
Example: world/maps/azeroth/azeroth.wdt will load world/maps/azeroth/azeroth.wdl; world/maps/azeroth/azeroth_29_29.adt which will load world/wmo/azeroth/buildings/human_farm/farm.wmo
-Post-8.1.X the client is looking for a FileDataID of a file,  WDT files are split into several sub-files, same with ADT.
Example: 775971 will load 775970; 777332, 777333, 777334, 777335, 1287004 which will load 106965
So the core principle is that after the editing of a map is done on 3.3.5, every reference to a particular file path needs to be translated into an appropriate FileDataID by looking them up in the Listfile. And in general files need to be adjusted to a new format with a converter tool.

c) Tools to have.

     Bare minimum for work on wrath-era maps
MPQ Editor - Download Here - allows you to open the wrath MPQ archives in your335client/Data/ folder and add/extract files.
Noggit - Download Here - a community map editor for ADT files. Very stable. Takes a bit to get into, not too beginner friendly.
and/or
Noggit Red - Download Here - an attempt at modernizing Noggit. Many user friendly features. In active development, can be highly unstable/problematic based on the build.
I personally have 3 versions - an old 3.2 version of Noggit, the latest 3.3 Noggit and the latest Noggit Red. There are drawbacks and issues with all of them.
Converters. Check the ADT conversion section below.
     ...for WDT Editing
WDT Filedata Tool - Download Here - allows you to add new tiles with their FileDataID to a WDT.
010 Editor - Download Here - allows you to view and edit raw data in files.
WDT Template - a template that allows 010 Editor to read WDT files in a somewhat understandable way, comes together with the wdt tool.
GruulMe - Download Here - optional editor for 3.3.5 WDT files, incompatible by themselves with modern clients, this is only for Noggit.
     ...for modern map editing
Downported Assets - Download Here and Here - Since ADT files are just terrain files and object information, you need assets compatible with 3.3.5 to see them in the map editor. I don't use any packs myself as they often contain poorly ported files but here is a potential one you can use, download the MPQ and place it in your335client/Data/ folder. If any files are missing/there is a WMO or M2 that you want to add then get their respective converters below.
ADT converter - Download Here - replaces FileDataID in raw modern ADT files with file paths. Follow the instructions and MultiConvert after. Check Noggit guides on how to set up a map, I will link some in a section below.
WMO converter - Download Here - replaces FileDataID in raw modern WMO files with file paths. Edit the .bat file for folders that you would be using, place raw root and group WMO files in them and run the converter, MultiConvert after.
M2 converter - Download Here - replaces FileDataID in raw modern M2 files with file paths. Place M2 and skin (and maybe anim files?) in the tool and MultiConvert after (I think?).
MultiConverter - Download Here - converts modern files with file paths (anything before 8.1) into their 3.3.5 versions. As part of the process it does delete non-wrath GroundEffects in ADT files though.

d) Potentially helpful resources

YouTube tutorials for Noggit and the 3.3.5 client in general.
Also this website has a lot of tutorials on pretty much everything.
Check the WoW modding discord.
A bunch of maps already converted to the modern format.
A great tool pack for 3.3.5 modding.

II. ADT conversion

Converter 1 (recommended) can be downloaded here.
Made, tested and documented by: Binary, Helnesis, Antani, Drakes, Moine, Elenwe.
Features: closed source; errors when a file is not in the Listfile.
How-to: download the converter, run it once, place your 3.3.5 WDT and ADT files in INPUT, run the converter again, if there are any errors read the log and add the missing file into the listfile.csv with format of filedataid;blizzardfilepath or substitute with something similar, converted files will be in OUTPUT.
Important: the tool doesn't convert WDT files, just reads the flags, so make sure your vertex shading or big/old alpha flags are properly set.
Converter 2 can be found on GitHub. You can also check the guide there.
Made by AcoStar. 
Features: open source; substitutes models and textures if they are not in the Listfile.
How-to: download the converter, extract it, place your 3.3.5 files in input, run the converter, the files will be in output.

III. WDT and WDL

Note: If you are just doing edits to ADT tiles that are there in the actual game (e.g. you want to add an island in the northrend sea) - no need to mess with WDT or WDL, the game already knows to load them, you just need the modified terrain.  
If you need a modified WDT - this is where things get a bit more complicated. The editor for post-8.1.5 WDT files I linked above doesn't actually write the FileDataID MAID chunk, only enables files by default. So here are three progressively problematic scenarios and how to approach them:
Scenario 1 - you want to add something that used to be part of the game but was cut, that is easy, just extract a modern WDT, run the tool and add the appropriate files from the list.
Scenario 2 -  you only have an old or a fully custom WDT file. Will provide screenshots for this in the example conversion section.
- open the WDT in 010 Editor
- run the WDTTemplate
- set the "has MAID" 0x0200 flag to 1, while you are there you can also set 0x100 and 0x8000 to 0 (if you have any weirdness with low level of detail files).
- put in all the _occ.wdt, .wdl etc. filedataids. If you don't have those files put 1249780 in tex, 1668535 in fogs, 1249658 in lgt, 1249561 in occ,  2495665 in mpv (this one might not be required?), WDL file should be accurately generated, more on that below. The flexibility of the _misc.wdt files is not really known so not sure what and when can cause crashes with these,  currently no way to generate relevant ones either.
- add donor MAID chunk at the very end of the file
- save
- start the tool, open the WDT
- add ADT files from the list, it looks up root file filedata from the listfile -> looks up filedata in split files listfile
- save
Scenario 3 -  you need to have files that are not in the Listfile. The only way is to add them, the tool needs _obj0 _obj1 _tex0 in splitfiles01.csv and root files in listfileonlyadts.csv. After that check back to Scenario 2.
Important: WDL should be accurate in modern clients, for every loaded ADT file there should be a WDL entry for it. There is a WDL generator inside just drop a folder with modern ADT files on the exe (doesn't work with 3.3.5 files).

If you want to create a map from scratch

There is a way to skip all WDT work. Pick a map that is in the Listfile (I would recommend  Nzoth, will use it as an example here ). Generate a map of the same size on 3.3.5 from 14_11 to 47_45. If you want to make it feel smaller you can fill it with holes or cover with water. Do your edits and after conversion paste the ADT files over this patch for Epsilon, it should have everything properly referenced.
If you need to you can rename your map files with Bulk Rename Utility e.g. nzoth.wdt, and the name of all terrain files nzoth_x_y (don't actually touch the coordinates, x_y is an example).

IV. Example of a full conversion

  Hide contents
For this example I will be converting a part of the leaked blizzard Development Land map to 8.3 to run on Epsilon. For this I will need raw files, MultiConverter to port ADT files down, GruulMe, Noggit, MPQEditor, Converter 1 to port up, 010 Editor and the WDT FileDataID converter.
1. I extract the raw Cata WDT and ADT files that I need. Place them into MultiConverter and convert. The result is singular files compatible with 3.3.5.

2. I load the WDT in GruulMe, go into ADT Grid, Delete all since I only need a 3x3 of tiles, Scan dir, return to General, Save.

3. I want to double check that everything is good so I go into 335folder/Data and open my MPQ, place the files in the correct folders.

4. Check in Noggit, Programmer Isle looks good.

5. Since I'm using Converter 1, I place the WDT, ADT files in the INPUT folder, run the converter. This time there were no errors and everything converted fine. If something would be missing I would check the log. If it's a BLP file ending in _s.blp (a specular texture) I would find the same one but without _s and add a new entry for the missing file with the filedataid of a normal one. If it's a model ending in .mdx I would find the same model but with newer extension of M2, add an entry for MDX using the filedata of the M2 one.

6. I transfer the OUTPUT files into a separate folder, add the WDT there. Open it in 010 Editor, run the WDTTemplate, add all the necessary information and set "has MAID" flag to 1. FileDataID for the miscellaneous files like occ etc. files can be looked up in the Listfile or use the IDs from Scenario 2 in the WDT section above.

7. Open the WDT FileDataID converter folder and the Donor Maid file there in 010, copy the whole right column, go back to the WDT, scroll down and insert the Donor Maid at the very end. Save the file.

8. In the same folder go into the one called "wdl", drop the folder with converted ADT files on WDLcreator3.exe, it will generate a WDL with the name of the map folder. Move it.

9. Open the the WDT FileDataID tool and open the WDT. Find the needed files from the list and add them. I have a 3x3 and I'm looking for files from development_0_0 to development_2_2.

10. The files are ready to be added - Epsilon, Kuretar, other SL RP servers, CascHost, Arctium, use whatever you want. Before making the patch I will add _occ.wdt, _fogs, _lgt, _tex for development since I have them.

11. All done. Teleport to the proper coordinates and mapid, have fun! Do note that Epsilon sometimes takes a bit to start streaming the files.

V. Potential problems and solutions

Chunks of the map don't render on certain angles or disappear/flicker - problem with mapname_occ.wdt, open the main WDT and try to substitute occFileDataID with 1249561 in 010 Editor.
Weird spots on textures - wrong alpha format. For example, modern Azeroth uses new alpha, classic Azeroth uses old alpha. Noggit can convert your map to either, use whatever is needed for the modern WDT you will be using.
A texture is green or a model is a white-blue textured box - something is missing, green textures = missing BLP, box = missing M2.
Streaming error - something important is missing, WDT or WDL can be improperly done, missing ADT or WMO.
Streaming error and you are sure no files are missing and everything is done right - Epsilon takes a bit to index files, while on character select screen wait for disk usage for epsilon to go down to practically 0, disabling additional patches might help with that too. If that doesn't help try summoning your main out to a different mapid and teleport in again.
WoW Error with a particular number - since those aren't really documented for modern clients it will be hard to tell. Likely something is in the wrong format or some flags are incorrect. For now the only documented ones for 8.3 are:
0x00007ff71813f9a0 referenced memory at 0x0000000000000000 - WDL is missing some ADT tiles that are referenced in the WDT, generate a new one with a full map. Don't use WotLK WDLs.
0x00007ff7181436d7 referenced memory at 0x00000***********  - WDL related. If you are using one from WotLK generate a post-MoP(?) one.
0x00007ff718137b98 referenced memory at 0x0000000000000044 - ADT are likely missing filedataid.
0x00007ff718143689 referenced memory at 0x0000000000001c94 - WDT may be is missing MAID or one of the misc_wdt/tex/wdl filedataids.
0x00007ff718132ef1 referenced memory at 0x00000*********** - WDT flags are wrong or missing.]]> Disclaimer.
Depending on what you want to do this can get very far from being user friendly, convenient or devoid of problems, modern clients are complicated and are not as well documented as 3.3.5. The guide itself is pretty basic since I'm sure more convenient tools will come with time. I will try to update this as the knowledge of the community grows, more tools become available.
If you are familiar with WoW modding skip to the ADT and WDT sections 2 and 3.

I.  Essential things to understand and the basics of clientside WoW modding.

a) WoW file formats and general terminology

ADT - tiles with terrain and object information on a map grid. Example to visualize.
WDT - a file that specifies how and which ADT map tiles should be loaded on a 64x64 grid. Example to visualize.
WDL - low level of detail height map that forms the "horizon mountains", is generated for each ADT map tile present. Example to visualize.
M2 - small static objects, spell and particle effects, animated models.
WMO - bigger static objects, can have M2 files in them (think M2 chairs in a WMO house).
BLP - texture files.
GroundEffects - also called Detail Doodads, if properly set up they render additional small M2s on ground textures.
GameObject - a serverside object that your client is told to render in a particular location.

b) Simplified differences in clients from 3.3.5 to 8.1+

MPQ vs CASC - WoW clients use archives to store their data. In wrath the type of archive is called MPQ, starting with WoD blizzard transitioned to CASC. Changes how the files are stored, changed and added.
FileDataID - a unique id of a file in the game data.
Listfile - a list of files and their FileDataID.
-On 3.3.5 the client reads files looking for references to particular paths in the MPQ archive.
Example: world/maps/azeroth/azeroth.wdt will load world/maps/azeroth/azeroth.wdl; world/maps/azeroth/azeroth_29_29.adt which will load world/wmo/azeroth/buildings/human_farm/farm.wmo
-Post-8.1.X the client is looking for a FileDataID of a file,  WDT files are split into several sub-files, same with ADT.
Example: 775971 will load 775970; 777332, 777333, 777334, 777335, 1287004 which will load 106965
So the core principle is that after the editing of a map is done on 3.3.5, every reference to a particular file path needs to be translated into an appropriate FileDataID by looking them up in the Listfile. And in general files need to be adjusted to a new format with a converter tool.

c) Tools to have.

     Bare minimum for work on wrath-era maps
MPQ Editor - Download Here - allows you to open the wrath MPQ archives in your335client/Data/ folder and add/extract files.
Noggit - Download Here - a community map editor for ADT files. Very stable. Takes a bit to get into, not too beginner friendly.
and/or
Noggit Red - Download Here - an attempt at modernizing Noggit. Many user friendly features. In active development, can be highly unstable/problematic based on the build.
I personally have 3 versions - an old 3.2 version of Noggit, the latest 3.3 Noggit and the latest Noggit Red. There are drawbacks and issues with all of them.
Converters. Check the ADT conversion section below.
     ...for WDT Editing
WDT Filedata Tool - Download Here - allows you to add new tiles with their FileDataID to a WDT.
010 Editor - Download Here - allows you to view and edit raw data in files.
WDT Template - a template that allows 010 Editor to read WDT files in a somewhat understandable way, comes together with the wdt tool.
GruulMe - Download Here - optional editor for 3.3.5 WDT files, incompatible by themselves with modern clients, this is only for Noggit.
     ...for modern map editing
Downported Assets - Download Here and Here - Since ADT files are just terrain files and object information, you need assets compatible with 3.3.5 to see them in the map editor. I don't use any packs myself as they often contain poorly ported files but here is a potential one you can use, download the MPQ and place it in your335client/Data/ folder. If any files are missing/there is a WMO or M2 that you want to add then get their respective converters below.
ADT converter - Download Here - replaces FileDataID in raw modern ADT files with file paths. Follow the instructions and MultiConvert after. Check Noggit guides on how to set up a map, I will link some in a section below.
WMO converter - Download Here - replaces FileDataID in raw modern WMO files with file paths. Edit the .bat file for folders that you would be using, place raw root and group WMO files in them and run the converter, MultiConvert after.
M2 converter - Download Here - replaces FileDataID in raw modern M2 files with file paths. Place M2 and skin (and maybe anim files?) in the tool and MultiConvert after (I think?).
MultiConverter - Download Here - converts modern files with file paths (anything before 8.1) into their 3.3.5 versions. As part of the process it does delete non-wrath GroundEffects in ADT files though.

d) Potentially helpful resources

YouTube tutorials for Noggit and the 3.3.5 client in general.
Also this website has a lot of tutorials on pretty much everything.
Check the WoW modding discord.
A bunch of maps already converted to the modern format.
A great tool pack for 3.3.5 modding.

II. ADT conversion

Converter 1 (recommended) can be downloaded here.
Made, tested and documented by: Binary, Helnesis, Antani, Drakes, Moine, Elenwe.
Features: closed source; errors when a file is not in the Listfile.
How-to: download the converter, run it once, place your 3.3.5 WDT and ADT files in INPUT, run the converter again, if there are any errors read the log and add the missing file into the listfile.csv with format of filedataid;blizzardfilepath or substitute with something similar, converted files will be in OUTPUT.
Important: the tool doesn't convert WDT files, just reads the flags, so make sure your vertex shading or big/old alpha flags are properly set.
Converter 2 can be found on GitHub. You can also check the guide there.
Made by AcoStar. 
Features: open source; substitutes models and textures if they are not in the Listfile.
How-to: download the converter, extract it, place your 3.3.5 files in input, run the converter, the files will be in output.

III. WDT and WDL

Note: If you are just doing edits to ADT tiles that are there in the actual game (e.g. you want to add an island in the northrend sea) - no need to mess with WDT or WDL, the game already knows to load them, you just need the modified terrain.  
If you need a modified WDT - this is where things get a bit more complicated. The editor for post-8.1.5 WDT files I linked above doesn't actually write the FileDataID MAID chunk, only enables files by default. So here are three progressively problematic scenarios and how to approach them:
Scenario 1 - you want to add something that used to be part of the game but was cut, that is easy, just extract a modern WDT, run the tool and add the appropriate files from the list.
Scenario 2 -  you only have an old or a fully custom WDT file. Will provide screenshots for this in the example conversion section.
- open the WDT in 010 Editor
- run the WDTTemplate
- set the "has MAID" 0x0200 flag to 1, while you are there you can also set 0x100 and 0x8000 to 0 (if you have any weirdness with low level of detail files).
- put in all the _occ.wdt, .wdl etc. filedataids. If you don't have those files put 1249780 in tex, 1668535 in fogs, 1249658 in lgt, 1249561 in occ,  2495665 in mpv (this one might not be required?), WDL file should be accurately generated, more on that below. The flexibility of the _misc.wdt files is not really known so not sure what and when can cause crashes with these,  currently no way to generate relevant ones either.
- add donor MAID chunk at the very end of the file
- save
- start the tool, open the WDT
- add ADT files from the list, it looks up root file filedata from the listfile -> looks up filedata in split files listfile
- save
Scenario 3 -  you need to have files that are not in the Listfile. The only way is to add them, the tool needs _obj0 _obj1 _tex0 in splitfiles01.csv and root files in listfileonlyadts.csv. After that check back to Scenario 2.
Important: WDL should be accurate in modern clients, for every loaded ADT file there should be a WDL entry for it. There is a WDL generator inside just drop a folder with modern ADT files on the exe (doesn't work with 3.3.5 files).

If you want to create a map from scratch

There is a way to skip all WDT work. Pick a map that is in the Listfile (I would recommend  Nzoth, will use it as an example here ). Generate a map of the same size on 3.3.5 from 14_11 to 47_45. If you want to make it feel smaller you can fill it with holes or cover with water. Do your edits and after conversion paste the ADT files over this patch for Epsilon, it should have everything properly referenced.
If you need to you can rename your map files with Bulk Rename Utility e.g. nzoth.wdt, and the name of all terrain files nzoth_x_y (don't actually touch the coordinates, x_y is an example).

IV. Example of a full conversion

  Hide contents
For this example I will be converting a part of the leaked blizzard Development Land map to 8.3 to run on Epsilon. For this I will need raw files, MultiConverter to port ADT files down, GruulMe, Noggit, MPQEditor, Converter 1 to port up, 010 Editor and the WDT FileDataID converter.
1. I extract the raw Cata WDT and ADT files that I need. Place them into MultiConverter and convert. The result is singular files compatible with 3.3.5.

2. I load the WDT in GruulMe, go into ADT Grid, Delete all since I only need a 3x3 of tiles, Scan dir, return to General, Save.

3. I want to double check that everything is good so I go into 335folder/Data and open my MPQ, place the files in the correct folders.

4. Check in Noggit, Programmer Isle looks good.

5. Since I'm using Converter 1, I place the WDT, ADT files in the INPUT folder, run the converter. This time there were no errors and everything converted fine. If something would be missing I would check the log. If it's a BLP file ending in _s.blp (a specular texture) I would find the same one but without _s and add a new entry for the missing file with the filedataid of a normal one. If it's a model ending in .mdx I would find the same model but with newer extension of M2, add an entry for MDX using the filedata of the M2 one.

6. I transfer the OUTPUT files into a separate folder, add the WDT there. Open it in 010 Editor, run the WDTTemplate, add all the necessary information and set "has MAID" flag to 1. FileDataID for the miscellaneous files like occ etc. files can be looked up in the Listfile or use the IDs from Scenario 2 in the WDT section above.

7. Open the WDT FileDataID converter folder and the Donor Maid file there in 010, copy the whole right column, go back to the WDT, scroll down and insert the Donor Maid at the very end. Save the file.

8. In the same folder go into the one called "wdl", drop the folder with converted ADT files on WDLcreator3.exe, it will generate a WDL with the name of the map folder. Move it.

9. Open the the WDT FileDataID tool and open the WDT. Find the needed files from the list and add them. I have a 3x3 and I'm looking for files from development_0_0 to development_2_2.

10. The files are ready to be added - Epsilon, Kuretar, other SL RP servers, CascHost, Arctium, use whatever you want. Before making the patch I will add _occ.wdt, _fogs, _lgt, _tex for development since I have them.

11. All done. Teleport to the proper coordinates and mapid, have fun! Do note that Epsilon sometimes takes a bit to start streaming the files.

V. Potential problems and solutions

Chunks of the map don't render on certain angles or disappear/flicker - problem with mapname_occ.wdt, open the main WDT and try to substitute occFileDataID with 1249561 in 010 Editor.
Weird spots on textures - wrong alpha format. For example, modern Azeroth uses new alpha, classic Azeroth uses old alpha. Noggit can convert your map to either, use whatever is needed for the modern WDT you will be using.
A texture is green or a model is a white-blue textured box - something is missing, green textures = missing BLP, box = missing M2.
Streaming error - something important is missing, WDT or WDL can be improperly done, missing ADT or WMO.
Streaming error and you are sure no files are missing and everything is done right - Epsilon takes a bit to index files, while on character select screen wait for disk usage for epsilon to go down to practically 0, disabling additional patches might help with that too. If that doesn't help try summoning your main out to a different mapid and teleport in again.
WoW Error with a particular number - since those aren't really documented for modern clients it will be hard to tell. Likely something is in the wrong format or some flags are incorrect. For now the only documented ones for 8.3 are:
0x00007ff71813f9a0 referenced memory at 0x0000000000000000 - WDL is missing some ADT tiles that are referenced in the WDT, generate a new one with a full map. Don't use WotLK WDLs.
0x00007ff7181436d7 referenced memory at 0x00000***********  - WDL related. If you are using one from WotLK generate a post-MoP(?) one.
0x00007ff718137b98 referenced memory at 0x0000000000000044 - ADT are likely missing filedataid.
0x00007ff718143689 referenced memory at 0x0000000000001c94 - WDT may be is missing MAID or one of the misc_wdt/tex/wdl filedataids.
0x00007ff718132ef1 referenced memory at 0x00000*********** - WDT flags are wrong or missing.]]> https://elijahketchersid.com/forums/thread-32.html Tue, 28 Oct 2025 13:28:01 +0000 rektbyfaith]]> https://elijahketchersid.com/forums/thread-32.html https://www.wowmodding.net/topic/1579-ho...adowlands/

[b]Before using this tutorial, make sure there are no better tools (like noggit red for shadowlands).[/b]
With this guide, you will be able to convert your custom adts from LK to SL. You will probably need CascHost or Arctium Launcher to upload converted files to the game. This guide will not help you create a map from scratch, it only explains the process of replacing the existing adt in the game with your own. Converted adt will not have texture scaling or other cool features of new versions
[b]Step 1: Download compiled converter script here[/b]
[b]Step 2: Unpack archive into empty folder[/b]
[b]Step 3: Put your 3.3.5 adt files to the "input" folder[/b]
[b]Step 4: Run"Convert.exe"[/b]
[b]Step 5: Take converted files from "output" folder[/b]
If you want to edit the map of a continent, such as the Eastern Kingdoms or Kalimdor, you will probably also need to remove two flags in your shadowlands wdt file. This is because the converter does not update the terrain LOD. In this regard, the terrain in the far distance may not be displayed correctly.
The flags you need to remove are 0x100 and 0x8000. You can do it manually using the 010 editor or use the second script.
[b]Step 1: Download compiled WDT fixer here[/b]
[b]Step 2: Extract map.wdt file from your shadowlands client or download it from wow.tools[/b]
[b]Step 3: Drag and drop the wdt file to "WDT flags fixer.exe"[/b]
While running, the script uses two additional converters. Links to their repositories:
Luzifix ADTConvert
Varent ObjOptimizer
You don't need to download them separately. Their executables already exists in the archive.]]> https://www.wowmodding.net/topic/1579-ho...adowlands/

[b]Before using this tutorial, make sure there are no better tools (like noggit red for shadowlands).[/b]
With this guide, you will be able to convert your custom adts from LK to SL. You will probably need CascHost or Arctium Launcher to upload converted files to the game. This guide will not help you create a map from scratch, it only explains the process of replacing the existing adt in the game with your own. Converted adt will not have texture scaling or other cool features of new versions
[b]Step 1: Download compiled converter script here[/b]
[b]Step 2: Unpack archive into empty folder[/b]
[b]Step 3: Put your 3.3.5 adt files to the "input" folder[/b]
[b]Step 4: Run"Convert.exe"[/b]
[b]Step 5: Take converted files from "output" folder[/b]
If you want to edit the map of a continent, such as the Eastern Kingdoms or Kalimdor, you will probably also need to remove two flags in your shadowlands wdt file. This is because the converter does not update the terrain LOD. In this regard, the terrain in the far distance may not be displayed correctly.
The flags you need to remove are 0x100 and 0x8000. You can do it manually using the 010 editor or use the second script.
[b]Step 1: Download compiled WDT fixer here[/b]
[b]Step 2: Extract map.wdt file from your shadowlands client or download it from wow.tools[/b]
[b]Step 3: Drag and drop the wdt file to "WDT flags fixer.exe"[/b]
While running, the script uses two additional converters. Links to their repositories:
Luzifix ADTConvert
Varent ObjOptimizer
You don't need to download them separately. Their executables already exists in the archive.]]> https://elijahketchersid.com/forums/thread-31.html Tue, 28 Oct 2025 13:27:33 +0000 rektbyfaith]]> https://elijahketchersid.com/forums/thread-31.html Method 1: GIMPOriginal Post:" 
  Hide contentsA
! This method should only be used by beginners. Once you are familiar with the workflow, use the bash script instead as it is significantly faster.
Requirements
Noggit Red
GIMP
Ofnuts' Tiles plug-inOriginal Post: https://www.wowmodding.net/topic/1577-he...oggit-red/
Extract the "ofnuts-tiles.py" file into your GIMP install directory at "GIMP 2/lib/gimp/2.0/plug-ins/"
___________________________________________________________________________________
Step 0

• Get a heightmap and matching alphamaps. You can generate them with a program like Gaea or find some online for free. Download the files used in this tutorial here.
  

        (Heightmaps should be in 16-bit .png or .exr format to ensure maximum detail.)
___________________________________________________________________________________
Step 1 - Tiling the Heightmap

• Load your heightmap into GIMP.
  

        (If you're using the files supplied in this tutorial, the heightmap is "height.png")
 

• Resize the heightmap with Image > Scale Image... to match your WoW map dimensions in ADTs x 257. 
  

        
        (Our map will have 10x10 ADTs, so we need a 2570x2570 heightmap.)
 

• Export your heightmap tiles with File > Export tiles > Export tiles (by rows and columns). 
  

        (If you don't see this option, the plug-in isn't installed correctly.)
 

• In the Export tiles options box use the following settings.
  

       
        Directory: Create a folder somewhere for your heightmap tiles
        Tile Name: Mountains_{column1}_{row1}_height.png
        Rows: 10
        Columns: 10
 

• Click OK and sit back while GIMP exports the image as 100 individual tiles using the naming convention we supplied, which matches what Noggit Red is expecting for heightmaps.
  

___________________________________________________________________________________
Step 2 - Tiling the Alphamaps

• Load your layer1 alphamap into GIMP.
  

        (If you're using the files supplied in this tutorial, the layer1 alphamap is "layer1.png")
 

• Resize the image with Image > Scale Image... to match your WoW map dimensions in ADTs x 1024 using 3.780 pixels/mm resolution.
  

              
        (Our map will have 10x10 ADTs, so we need 10240x10240 alphamaps.)
 
NOTE: The alphamaps supplied in this tutorial are being scaled up from 4k to 10k, but this is only done for convenience and will produce a blurry texture mask. For best results your heightmaps and alphamaps should be as close to the intended size as possible, or scaled down if necessary.
 

• Export your layer1 alphamap tiles with File > Export tiles > Export tiles (by rows and columns).
  

 

• In the options box that pops up, use the following settings.
  
  

        Directory: Create a folder somewhere for your alphamap tiles
        Tile Name: Mountains_{column1}_{row1}_layer1.png
        Rows: 10
        Columns: 10
 

• Click OK and wait for GIMP to finish.
   
  

• Repeat the process for the layer2 and layer3 alphamaps.
  

 
 
Method 2: Bash script (Recommended)
  Hide contents
Requirements
Noggit Red
Git Bash
ImageMagick (16-bit HDRI)
___________________________________________________________________________________
Step 0

• Get a heightmap and matching alphamaps. You can generate them with a program like Gaea or find some online for free. Download the files used in this tutorial here.
          (Heightmaps should be in 16-bit .png or .exr to ensure maximum detail.)
  

___________________________________________________________________________________
Step 1

• Download the Noggify bash script and place it in a folder with your texturemaps. Open the file with a text editor and check the variables. (They are preset to follow the rest of this tutorial.)
  

___________________________________________________________________________________
Step 2

• Double-click the bash script to run it and generate the height and alphamap tiles.
  

 
 
___________________________________________________________________________________
Step 3 - Noggit Red Setup

• Launch Noggit Red and create a new project.
  

 

• Create a new map named Mountains with 10x10 ADTs starting at 1-1.(Set the map expansion to latest for maximum in-game view distance.)
  

 

• Copy the heightmap and alphamap tiles into your Noggit Red project folder at "/world/maps/mountains/".
  

        
        (The folder contents should look like this, with one heightmap and three alphamaps for each ADT.)
 
___________________________________________________________________________________
Step 4 - Importing the Heightmap

• Enter your map in Noggit Red and import the heightmaps with Assist > Global > Import > Import heightmaps using a multiplier of 3000.
  

        (You can play around with the multiplier to increase or decrease the vertical "stretch" of the terrain.)
 

• The terrain should now be deformed.
  

 

• Load all ADTs with Assist > Global > Debug > Load all tiles
  

 

• Reset the lighting and shadows on the terrain by using a sculpting tool with maximum brush size and 0.00 speed.
  

 

• Fix gaps in the terrain with Assist > Loaded ADTs > Fix gaps 
  

 

• If you come across impassable tiles, go into Impass Designator mode and use ctrl+left click on the greyed-out squares.
  

 
___________________________________________________________________________________
Step 5 - Applying Texture Layers

• Press U to enter tile mode and zoom out so you can see the entire map.(If you see black spots on your map in tile mode, go back to the normal view and raise your camera height with Q.)
  

        

• Using the largest brush possible, paint your map with a base texture at 100% opacity. I used rock. 
   
  
• Repeat the process with a second texture. This is the texture that will be masked off by your layer1 alphamap. I used soil
   
  
• Repeat the process with a third texture. This is the texture that will be masked off by your layer2 alphamap. I used grass.
  
  

 

• Repeat the process with a fourth texture. This is the texture that will be masked off by your layer3 alphamap. I used sand.
  

 

• In Texture Painter mode, ctrl+click somewhere on your terrain to bring up the texture picker. You should see 4 textures.
  

        
___________________________________________________________________________________
 
A Note on Alphamapping
  Hide contents
(Color used for visual purposes only, alphamaps must be in grayscale)

Get your alphamaps from an RGBA splatmap to avoid overlap between layers. The R/G/B channels define the opacity of layer 1-3 and the alpha channel defines the base texture.
 
___________________________________________________________________________________
Step 6 - Importing the Alphamaps

• Import the alphamaps with Assist > Global > Import > Import alphamaps. After everything loads you should see the final product.
   
  

 
https://www.youtube.com/watch?v=IqBvcjdh...ing.net%2F]]> Method 1: GIMPOriginal Post:" 
  Hide contentsA
! This method should only be used by beginners. Once you are familiar with the workflow, use the bash script instead as it is significantly faster.
Requirements
Noggit Red
GIMP
Ofnuts' Tiles plug-inOriginal Post: https://www.wowmodding.net/topic/1577-he...oggit-red/
Extract the "ofnuts-tiles.py" file into your GIMP install directory at "GIMP 2/lib/gimp/2.0/plug-ins/"
___________________________________________________________________________________
Step 0

• Get a heightmap and matching alphamaps. You can generate them with a program like Gaea or find some online for free. Download the files used in this tutorial here.
  

        (Heightmaps should be in 16-bit .png or .exr format to ensure maximum detail.)
___________________________________________________________________________________
Step 1 - Tiling the Heightmap

• Load your heightmap into GIMP.
  

        (If you're using the files supplied in this tutorial, the heightmap is "height.png")
 

• Resize the heightmap with Image > Scale Image... to match your WoW map dimensions in ADTs x 257. 
  

        
        (Our map will have 10x10 ADTs, so we need a 2570x2570 heightmap.)
 

• Export your heightmap tiles with File > Export tiles > Export tiles (by rows and columns). 
  

        (If you don't see this option, the plug-in isn't installed correctly.)
 

• In the Export tiles options box use the following settings.
  

       
        Directory: Create a folder somewhere for your heightmap tiles
        Tile Name: Mountains_{column1}_{row1}_height.png
        Rows: 10
        Columns: 10
 

• Click OK and sit back while GIMP exports the image as 100 individual tiles using the naming convention we supplied, which matches what Noggit Red is expecting for heightmaps.
  

___________________________________________________________________________________
Step 2 - Tiling the Alphamaps

• Load your layer1 alphamap into GIMP.
  

        (If you're using the files supplied in this tutorial, the layer1 alphamap is "layer1.png")
 

• Resize the image with Image > Scale Image... to match your WoW map dimensions in ADTs x 1024 using 3.780 pixels/mm resolution.
  

              
        (Our map will have 10x10 ADTs, so we need 10240x10240 alphamaps.)
 
NOTE: The alphamaps supplied in this tutorial are being scaled up from 4k to 10k, but this is only done for convenience and will produce a blurry texture mask. For best results your heightmaps and alphamaps should be as close to the intended size as possible, or scaled down if necessary.
 

• Export your layer1 alphamap tiles with File > Export tiles > Export tiles (by rows and columns).
  

 

• In the options box that pops up, use the following settings.
  
  

        Directory: Create a folder somewhere for your alphamap tiles
        Tile Name: Mountains_{column1}_{row1}_layer1.png
        Rows: 10
        Columns: 10
 

• Click OK and wait for GIMP to finish.
   
  

• Repeat the process for the layer2 and layer3 alphamaps.
  

 
 
Method 2: Bash script (Recommended)
  Hide contents
Requirements
Noggit Red
Git Bash
ImageMagick (16-bit HDRI)
___________________________________________________________________________________
Step 0

• Get a heightmap and matching alphamaps. You can generate them with a program like Gaea or find some online for free. Download the files used in this tutorial here.
          (Heightmaps should be in 16-bit .png or .exr to ensure maximum detail.)
  

___________________________________________________________________________________
Step 1

• Download the Noggify bash script and place it in a folder with your texturemaps. Open the file with a text editor and check the variables. (They are preset to follow the rest of this tutorial.)
  

___________________________________________________________________________________
Step 2

• Double-click the bash script to run it and generate the height and alphamap tiles.
  

 
 
___________________________________________________________________________________
Step 3 - Noggit Red Setup

• Launch Noggit Red and create a new project.
  

 

• Create a new map named Mountains with 10x10 ADTs starting at 1-1.(Set the map expansion to latest for maximum in-game view distance.)
  

 

• Copy the heightmap and alphamap tiles into your Noggit Red project folder at "/world/maps/mountains/".
  

        
        (The folder contents should look like this, with one heightmap and three alphamaps for each ADT.)
 
___________________________________________________________________________________
Step 4 - Importing the Heightmap

• Enter your map in Noggit Red and import the heightmaps with Assist > Global > Import > Import heightmaps using a multiplier of 3000.
  

        (You can play around with the multiplier to increase or decrease the vertical "stretch" of the terrain.)
 

• The terrain should now be deformed.
  

 

• Load all ADTs with Assist > Global > Debug > Load all tiles
  

 

• Reset the lighting and shadows on the terrain by using a sculpting tool with maximum brush size and 0.00 speed.
  

 

• Fix gaps in the terrain with Assist > Loaded ADTs > Fix gaps 
  

 

• If you come across impassable tiles, go into Impass Designator mode and use ctrl+left click on the greyed-out squares.
  

 
___________________________________________________________________________________
Step 5 - Applying Texture Layers

• Press U to enter tile mode and zoom out so you can see the entire map.(If you see black spots on your map in tile mode, go back to the normal view and raise your camera height with Q.)
  

        

• Using the largest brush possible, paint your map with a base texture at 100% opacity. I used rock. 
   
  
• Repeat the process with a second texture. This is the texture that will be masked off by your layer1 alphamap. I used soil
   
  
• Repeat the process with a third texture. This is the texture that will be masked off by your layer2 alphamap. I used grass.
  
  

 

• Repeat the process with a fourth texture. This is the texture that will be masked off by your layer3 alphamap. I used sand.
  

 

• In Texture Painter mode, ctrl+click somewhere on your terrain to bring up the texture picker. You should see 4 textures.
  

        
___________________________________________________________________________________
 
A Note on Alphamapping
  Hide contents
(Color used for visual purposes only, alphamaps must be in grayscale)

Get your alphamaps from an RGBA splatmap to avoid overlap between layers. The R/G/B channels define the opacity of layer 1-3 and the alpha channel defines the base texture.
 
___________________________________________________________________________________
Step 6 - Importing the Alphamaps

• Import the alphamaps with Assist > Global > Import > Import alphamaps. After everything loads you should see the final product.
   
  

 
https://www.youtube.com/watch?v=IqBvcjdh...ing.net%2F]]> https://elijahketchersid.com/forums/thread-30.html Tue, 28 Oct 2025 13:25:51 +0000 rektbyfaith]]> https://elijahketchersid.com/forums/thread-30.html https://www.wowmodding.net/topic/1570-no...%E2%99%A5/
Video: https://www.youtube.com/watch?v=sHh-KIH7...ing.net%2F]]> https://www.wowmodding.net/topic/1570-no...%E2%99%A5/
Video: https://www.youtube.com/watch?v=sHh-KIH7...ing.net%2F]]> https://elijahketchersid.com/forums/thread-29.html Tue, 28 Oct 2025 13:25:18 +0000 rektbyfaith]]> https://elijahketchersid.com/forums/thread-29.html

1. Original Post: https://www.wowmodding.net/topic/1565-ho...in-noggit/ Create a project folder where you store all your custom work, including the folders used in your custom patch-x.mpq (DBFilesClient &  Interface etc)
2.  Copy your "Data" folder from your wow client folder to your newly created project folder.
    Copy your "World" folder (custom maps) to your newly created project folder.
   
3.  Make sure that your custom patch-x.mpq is in the "Data" folder you just copied to your project folder.
   
4. Open Noggit (I use Noggit version 3.2771) and go to your "Settings"
   
5. Check the first options "Game Path" and "Project Path" and link both these to your project folder
   
6. Hit "Save" and restart Noggit.
   
7. Finito!  You should now have your custom map visible in your Noggit!
   

]]>

1. Original Post: https://www.wowmodding.net/topic/1565-ho...in-noggit/ Create a project folder where you store all your custom work, including the folders used in your custom patch-x.mpq (DBFilesClient &  Interface etc)
2.  Copy your "Data" folder from your wow client folder to your newly created project folder.
    Copy your "World" folder (custom maps) to your newly created project folder.
   
3.  Make sure that your custom patch-x.mpq is in the "Data" folder you just copied to your project folder.
   
4. Open Noggit (I use Noggit version 3.2771) and go to your "Settings"
   
5. Check the first options "Game Path" and "Project Path" and link both these to your project folder
   
6. Hit "Save" and restart Noggit.
   
7. Finito!  You should now have your custom map visible in your Noggit!
   

]]> https://elijahketchersid.com/forums/thread-28.html Tue, 28 Oct 2025 13:24:46 +0000 rektbyfaith]]> https://elijahketchersid.com/forums/thread-28.html https://www.wowmodding.net/topic/1563-no...%E2%99%A5/

Link: https://www.youtube.com/watch?v=-P0CSr0R...ing.net%2F]]> https://www.wowmodding.net/topic/1563-no...%E2%99%A5/

Link: https://www.youtube.com/watch?v=-P0CSr0R...ing.net%2F]]> https://elijahketchersid.com/forums/thread-27.html Tue, 28 Oct 2025 13:23:13 +0000 rektbyfaith]]> https://elijahketchersid.com/forums/thread-27.html https://www.wowmodding.net/topic/1562-cu...orial-335/
[b]Introduction[/b]
What is a skybox? The answer is fairly simple, a skybox is a way to light up your zone in WoW. Aside from lightning up the environment, it also allows us to manipulate the way the sky looks (that is why it is called the skybox, but I consider this to be the 2nd order importance of it).The undeniable truth is, that it is really important to light up your zone properly, this produces a very good impression of your zone. However, this process can be quite tidious and certainly it is not easy to do. In this tutorial I will do my best to show you how to produce such a skybox!
[b]This is a super huge tutorial, I did my best to  nail out the details, however, due to its size I am aware that there will be lots of minor spelling errors, grammar errors and such, please, do let me know about those, I will do my best to get those fixed! Also if you have any suggestions about the tutorial, I will welcome them![/b]
 
All files required for this tutorial can be downloaded via this link:
[b][u]https://mega.nz/file/yEhEnDoK#NQ-zIGSnHjVMXP2tjw_Jcjvqwnf1ZrTyY_5R8ZB9MPk[/b][/u]
 
You'll be better off with these files. When we get to DBC works in this tutorial it is good just to see how it works and once we are done, you can just go ahead and try changing some cells here and there.
 
[b]What software we need[/b]
-        MyDbcEditor – simple Dbc files editor
-        WDBX Editor – more advanced Dbc editor, you can use this instead of MyDbcEditor, however, we are going to use this one to produce BGR codes for our skybox (BGR is pretty much RGB in reverse order).
 
[b]Lets get all the files that we might need[/b]
-        From the latest client patch, we need to extract these: Light.dbc, LightParams.dbc, LightSkyBox.dbc, LightIntBands.dbc, LightFloatBands.dbc a Map.dbc.
-        In case you want to put there a skybox model to represent your sky, it is good to get your model in advance. The easiest way is just to take a model from higher expansions and downport it to 3.3.5.. It is certainly possible to produce your own 3D model for the skybox, but that is mostly a 3D modeling stuff, and we are not going concern ourselves about this.
 
[b]Basic information about light Dbc files[/b]
First of all, lets make a little excursion into light Dbc files and lets try to understand what each file does.
 
1)      [b]Light.dbc[/b] –this perhaps the most important Dbc file we are going to work with today. This Dbc file is essential when defining a new skybox. In case you want to purely copy a already existing skybox, then this is the only Dbc file you need to edit. The structure is following:
 
Collums:
1. Id of each skybox – not really interesting for us
2. Id of map –  this Id comes from Map.Dbc, Id of map on which we want to place our skybox
3. X client side coordinate – X coor. For skybox placement, [b]has to be multiplied by 36![/b]
4. Z client side coordinate –  Z coor. For skybox placement, [b]has to be multiplied by 36![/b]
5. Y client side coordinate –  Y coor. For skybox placement, [b]has to be multiplied by 36![/b]
6. Inner radius of skybox – at this radius, the skybox won't overlap with other skyboxes, [b]has to be multiplied by 36![/b]
7. Outer radius of skybox – at this radius, the skybox will overlap with other skyboxes, [b]has to be multiplied by 36![/b]
8. Row Id from Lightparams.dbc, for normal weather
9. Row Id from Lightparams.dbc, for normal weather under water
10. Row Id from Lightparams.dbc, for rainy weather
11. Row Id from Lightparams.dbc, for rainy weather under water
12. Row Id from Lightparams.dbc, for spirit world
13. & other - Row Ids for other phases
You can read more at:  [b][u]https://wowdev.wiki/DB/Light[/b][/u]
[b]BEWARE! WoWDevWiki states the order of cooridinates in the standard way (x,y,z), but in fact it is switeched in case of Light.dbc (x,z,y)[/b]
 
2)      LightParams.dbc – we have already touched this Dbc when talking about Light.dbc, each row in this Dbc file defines a unique lightning (skybox) setting, those settings can then be used in Light.dbc.
Collums:
1. Defines Id of each lightning (skybox), this Id is then used in Light.dbc, it is also used as reference for rows in LightIntBand.dbc & LightFloatBand.dbc
2. Boolean value – Hightlight sky – not sure on this one
3. Id of skybox model (refence to row # in LightSkybox.dbc – we will also mention it later
4. Integer value, defines the clouds
5. Defines how much brightness/ fog will be added, float 0 - 1
6. Defines transparency of shallow  River Water
7. Defines transparency of deep  River Water
8. Defines transparency of shallow  Ocean Water          
9. Defines transparency of deep  Ocean Water
10. Values from 0 -1, now sure on this one
You can read more at:  [b][u]https://wowdev.wiki/DB/LightParams[/b][/u]
 
3)      [b]LightIntBand.dbc[/b] – this Dbc file defines colours of our skybox, in fact, this is super important Dbc, because it really allows you to customise lightning in your zone. To edit this Dbc file we are going to use WDBX editor. The reason why is fairly simple, WDBX allows us to read and produce BGR codes (simillar to RGB). These BGR codes are then used by the skybox. Functionality of this file is following: for each Id (row) in LightParams.dbc there is 18 rows in LightIntBand.dbc, for instance, for row #1 in LightParams.dbc the first 18 rows in LightIntBand.dbc are bound to this LightParams.dbc row. Generally if we wanted to know what are the numbers of rows that correspond to our LightParams.dbc row the pattern is following: multiply the # of row in LightParams.dbc by 18, then we subtract 17 and the following 17 rows are bound to our original row in LightParams.dbc.
Collums in each row:
1. Id of row –has to correspond to LightParams.dbc!
2. Integer value, defines how many lightning phases there are, max number is 15
3. - 18.  Time values for each phases (if we wrote 2 in collum # 2 we need to fill in first 2 collums), time is give in half minutes. Say we wanted to put in there 7 am, value 840 corresponds to this time.
19. - 34. BGR codes,these define the colours of our skybox, they follow the same order as our time phases, in case we work with 2 phases, then we need to fill in only first 2 collumds, to produce these BGR codes we can use Colour function in WDBX editor.
 
Each rows – below are described functionalities of each row's collums from 19. to 34.
1. Defines colour of general lightning
2. Defines colour of dispersed light
3. Colour of topmost part of sky
4. Colour of middle part of sky
5. Colour of sky going to the horizon
6. Colour of sky just above the horizion
7. Colour of the horizon
8. Colour of fog in the background (mountains and such)
9. ???
10. Colour of sun, solar disk and sunrays
11. First colour of clouds
12. Second colour of clouds
13. Third colour of clouds
14. ???
15. Colour of shallow Ocean Water
16. Colour of deep Ocean Water
17. Colour of shallow River Water
18. Colour of deep River Water
You can read more at: [b][u]https://wowdev.wiki/DB/LightIntBand[/b][/u]
 
4)      [b]LightFloatBand.dbc[/b] – this Dbc has simillar structure to LightIntBand.dbc, however, this Dbc controls the amount of fox, its density, clouds density, and Moon shine. For every Id from LightParams.dbc there are 6 rows in LightFloatBand.dbc. This Dbc uses very same logic as LightIntBand.dbc, to get the 6 rows corresponding with your LightParams.dbc row you need to multiply the original # by 6 and subtract 5, to get your first row in LightParams.dbc.
Collums in each row:
1. Row Id – has to correspond to Id row from (first row is LightParams.dbc * 6 - 5)
2. Integer value, defines how many phases of lightning there are, maximum is 15
3. - 18.  Time values for each phase (if we wrote 2 in collum # 2 we need to fill in first 2 collums), time is give in half minutes. Say we wanted to put in there 7 am, value 840 corresponds to this time.
Uses very same logic as LightIntBand.dbc
19. - 34. float values, in case we defined only 2 phases of lightning we need to fill in only first 2 collums.
               
Functionality of collums in each row  (collums 19. - 34, down below are rows)
1. Defines distance of fog multiplied by 36, from this distance on everything will be shrouded in fog
2. Fog density value, this says at which distance value the fog starts, float values from 0 – 0.999
3. Brightness of Sun and Moon when overlapped by clouds
4. Cloud density float value from 0 - 1
5. ???
6. ???
You can read more at: [b][u]https://wowdev.wiki/DB/LightFloatBand[/b][/u]
 
5)      [b]LightSkybox.dbc[/b] – the simpliest Dbc of all, this file allows us to add skybox models, and edit their properties (such as transparency), we are not going to use this Dbc in our tutorial, but you can definetly go ahead and try experimenting with this one.
Collums:
1. Defines Id of each skybox model, this Id is then used in LightParams.dbc
2. Path to our model: „Environments/Stars/[MODEL].mdx“
3. Integer values flagy, defines properties of the model, such as transparency, 0 – skybox used animation based on time, 2 – shows Sun, Moon and clouds, skybox can be transparent, 4 – produces procedural mist. The most commonly used value is 2.
You can read more at: [b][u]https://wowdev.wiki/DB/LightSkybox[/b][/u]
 
Right now we have covered all the important things about the Dbc files. I admit there were lots of it, for sure you don't have to know all of it, but it is good to have a decent image of the structure. You can also read more at WoWDevWiki. Now we will proceed with the creation of a skybox.

[b]Creation of custom skybox:[/b]
Now lets try to make use of our newly gained knowledge of Light Dbc files and lets try producing a custom WoW skybox at Hyjal!
First of all, we need to get our client coordinates of the place – X=20540 Y= 11690 Z=1600
We can get these fairly easily in Noggit.

First we insert a new row in LightParams.dbc – 954. For now we can leave this row be, or we can copy parameters of some other row. We will return to this later.

 
Now we continue by adding a new row in Light.dbc –first of all lets write our X, Z,Y coordinates 3 multiplied by 36. Then we need to think of the inner and outer radius of our skybox. Lets say 1388 and 1666, once again we have to multiply these numbers by 36. After that we can insert the Id of our row from LightParams.dbc - 954.

 
Now lets move to the harder part – LightIntBand.dbc and LightFloatBand.dbc.
Lets continue with LightIntband.dbc. It is nessesary to open this Dbc files in WDBX editor. First we need to add 18 new lines starting with number:  954*18 – 17 down to number 954*18. To make things easier for us, it is always good to fill in all general datas to our newly added row, so that we can just copy it to all that will follow. All together we will be adding 3 phases of lightning – early morning – day – night. So we will use 3 collums of datas – se we will use 3 collums for time and 3 collums for data. First lets put in time value for morning phase, lets say we want to be from Midnight to 8:00, that means we put 960 (480 minutes * 2) into 3rd collum, day-time phase will be untill 19:00, that means 2280 will go into the 4th colum. Same datas can be used for following 17 rows, but it is not must do, you could have different number of phases for each setting.
Right now we can move to BGR codes, lets get back to our first row #(954*18 – 17) – starting with collum #19 there are our collums with BGR codes. Lets say we want our skybox to have purple-blue-white like colour. So we generate our colours using Color function. Do 19. We proceed with filling in datas for morning, day and night, for each setting (yep, it is lots of work). At this point I highly recommend you using the Dbc files attached for this tutorial, makes everything much simplier, and to elevate your understanding of topic, just spend some time playing with the Dbcs.
 
Now we are about to edit LightFloatBand.dbc. We no longer need to use WDBX editor, but you can surely use it if you feel comfortable in it. Once again we need to insert 6 new rows, once again their Ids need to correspond to our original Id in LightParams.dbc. The first row has to have Id:  954*6 - 6, 5 more rows follow.
 
We want it to be pretty foggy in the morning,lets set the fog distance in collum #19 (1st row) to 9000 , for following collums lets set the value a bit higher. Simillarly we go on with the next row, this time we put in values from 0 – 1. Next row we fill in 0s or 1s, this one shouldn't really convern us, next row is about cloud density, lets say we want morning to be clouds, whereas nights should be clear (it is good to work with this row in case you don't want to add in skybox model, which is our case). That is all for LightFloatBand.dbc.

Next Dbc is LightSkyBox.dbc, I don't want to put in any skybox model this time, so we are not going to use this Dbc. But feel free to give it a try yourself, it is a good starting exercise.
If we had added in custom skybox model, we would have returned back to LightParams.dbc to fill in our skybox model row Id, defaulty this value in LightParams.dbc should be set to 0. (Collum 3)
 
As of now we are done! Lets put all our edited Dbcs, blps and m2s into patch, and lets také a look what it looks like in-game
]]> https://www.wowmodding.net/topic/1562-cu...orial-335/
[b]Introduction[/b]
What is a skybox? The answer is fairly simple, a skybox is a way to light up your zone in WoW. Aside from lightning up the environment, it also allows us to manipulate the way the sky looks (that is why it is called the skybox, but I consider this to be the 2nd order importance of it).The undeniable truth is, that it is really important to light up your zone properly, this produces a very good impression of your zone. However, this process can be quite tidious and certainly it is not easy to do. In this tutorial I will do my best to show you how to produce such a skybox!
[b]This is a super huge tutorial, I did my best to  nail out the details, however, due to its size I am aware that there will be lots of minor spelling errors, grammar errors and such, please, do let me know about those, I will do my best to get those fixed! Also if you have any suggestions about the tutorial, I will welcome them![/b]
 
All files required for this tutorial can be downloaded via this link:
[b][u]https://mega.nz/file/yEhEnDoK#NQ-zIGSnHjVMXP2tjw_Jcjvqwnf1ZrTyY_5R8ZB9MPk[/b][/u]
 
You'll be better off with these files. When we get to DBC works in this tutorial it is good just to see how it works and once we are done, you can just go ahead and try changing some cells here and there.
 
[b]What software we need[/b]
-        MyDbcEditor – simple Dbc files editor
-        WDBX Editor – more advanced Dbc editor, you can use this instead of MyDbcEditor, however, we are going to use this one to produce BGR codes for our skybox (BGR is pretty much RGB in reverse order).
 
[b]Lets get all the files that we might need[/b]
-        From the latest client patch, we need to extract these: Light.dbc, LightParams.dbc, LightSkyBox.dbc, LightIntBands.dbc, LightFloatBands.dbc a Map.dbc.
-        In case you want to put there a skybox model to represent your sky, it is good to get your model in advance. The easiest way is just to take a model from higher expansions and downport it to 3.3.5.. It is certainly possible to produce your own 3D model for the skybox, but that is mostly a 3D modeling stuff, and we are not going concern ourselves about this.
 
[b]Basic information about light Dbc files[/b]
First of all, lets make a little excursion into light Dbc files and lets try to understand what each file does.
 
1)      [b]Light.dbc[/b] –this perhaps the most important Dbc file we are going to work with today. This Dbc file is essential when defining a new skybox. In case you want to purely copy a already existing skybox, then this is the only Dbc file you need to edit. The structure is following:
 
Collums:
1. Id of each skybox – not really interesting for us
2. Id of map –  this Id comes from Map.Dbc, Id of map on which we want to place our skybox
3. X client side coordinate – X coor. For skybox placement, [b]has to be multiplied by 36![/b]
4. Z client side coordinate –  Z coor. For skybox placement, [b]has to be multiplied by 36![/b]
5. Y client side coordinate –  Y coor. For skybox placement, [b]has to be multiplied by 36![/b]
6. Inner radius of skybox – at this radius, the skybox won't overlap with other skyboxes, [b]has to be multiplied by 36![/b]
7. Outer radius of skybox – at this radius, the skybox will overlap with other skyboxes, [b]has to be multiplied by 36![/b]
8. Row Id from Lightparams.dbc, for normal weather
9. Row Id from Lightparams.dbc, for normal weather under water
10. Row Id from Lightparams.dbc, for rainy weather
11. Row Id from Lightparams.dbc, for rainy weather under water
12. Row Id from Lightparams.dbc, for spirit world
13. & other - Row Ids for other phases
You can read more at:  [b][u]https://wowdev.wiki/DB/Light[/b][/u]
[b]BEWARE! WoWDevWiki states the order of cooridinates in the standard way (x,y,z), but in fact it is switeched in case of Light.dbc (x,z,y)[/b]
 
2)      LightParams.dbc – we have already touched this Dbc when talking about Light.dbc, each row in this Dbc file defines a unique lightning (skybox) setting, those settings can then be used in Light.dbc.
Collums:
1. Defines Id of each lightning (skybox), this Id is then used in Light.dbc, it is also used as reference for rows in LightIntBand.dbc & LightFloatBand.dbc
2. Boolean value – Hightlight sky – not sure on this one
3. Id of skybox model (refence to row # in LightSkybox.dbc – we will also mention it later
4. Integer value, defines the clouds
5. Defines how much brightness/ fog will be added, float 0 - 1
6. Defines transparency of shallow  River Water
7. Defines transparency of deep  River Water
8. Defines transparency of shallow  Ocean Water          
9. Defines transparency of deep  Ocean Water
10. Values from 0 -1, now sure on this one
You can read more at:  [b][u]https://wowdev.wiki/DB/LightParams[/b][/u]
 
3)      [b]LightIntBand.dbc[/b] – this Dbc file defines colours of our skybox, in fact, this is super important Dbc, because it really allows you to customise lightning in your zone. To edit this Dbc file we are going to use WDBX editor. The reason why is fairly simple, WDBX allows us to read and produce BGR codes (simillar to RGB). These BGR codes are then used by the skybox. Functionality of this file is following: for each Id (row) in LightParams.dbc there is 18 rows in LightIntBand.dbc, for instance, for row #1 in LightParams.dbc the first 18 rows in LightIntBand.dbc are bound to this LightParams.dbc row. Generally if we wanted to know what are the numbers of rows that correspond to our LightParams.dbc row the pattern is following: multiply the # of row in LightParams.dbc by 18, then we subtract 17 and the following 17 rows are bound to our original row in LightParams.dbc.
Collums in each row:
1. Id of row –has to correspond to LightParams.dbc!
2. Integer value, defines how many lightning phases there are, max number is 15
3. - 18.  Time values for each phases (if we wrote 2 in collum # 2 we need to fill in first 2 collums), time is give in half minutes. Say we wanted to put in there 7 am, value 840 corresponds to this time.
19. - 34. BGR codes,these define the colours of our skybox, they follow the same order as our time phases, in case we work with 2 phases, then we need to fill in only first 2 collumds, to produce these BGR codes we can use Colour function in WDBX editor.
 
Each rows – below are described functionalities of each row's collums from 19. to 34.
1. Defines colour of general lightning
2. Defines colour of dispersed light
3. Colour of topmost part of sky
4. Colour of middle part of sky
5. Colour of sky going to the horizon
6. Colour of sky just above the horizion
7. Colour of the horizon
8. Colour of fog in the background (mountains and such)
9. ???
10. Colour of sun, solar disk and sunrays
11. First colour of clouds
12. Second colour of clouds
13. Third colour of clouds
14. ???
15. Colour of shallow Ocean Water
16. Colour of deep Ocean Water
17. Colour of shallow River Water
18. Colour of deep River Water
You can read more at: [b][u]https://wowdev.wiki/DB/LightIntBand[/b][/u]
 
4)      [b]LightFloatBand.dbc[/b] – this Dbc has simillar structure to LightIntBand.dbc, however, this Dbc controls the amount of fox, its density, clouds density, and Moon shine. For every Id from LightParams.dbc there are 6 rows in LightFloatBand.dbc. This Dbc uses very same logic as LightIntBand.dbc, to get the 6 rows corresponding with your LightParams.dbc row you need to multiply the original # by 6 and subtract 5, to get your first row in LightParams.dbc.
Collums in each row:
1. Row Id – has to correspond to Id row from (first row is LightParams.dbc * 6 - 5)
2. Integer value, defines how many phases of lightning there are, maximum is 15
3. - 18.  Time values for each phase (if we wrote 2 in collum # 2 we need to fill in first 2 collums), time is give in half minutes. Say we wanted to put in there 7 am, value 840 corresponds to this time.
Uses very same logic as LightIntBand.dbc
19. - 34. float values, in case we defined only 2 phases of lightning we need to fill in only first 2 collums.
               
Functionality of collums in each row  (collums 19. - 34, down below are rows)
1. Defines distance of fog multiplied by 36, from this distance on everything will be shrouded in fog
2. Fog density value, this says at which distance value the fog starts, float values from 0 – 0.999
3. Brightness of Sun and Moon when overlapped by clouds
4. Cloud density float value from 0 - 1
5. ???
6. ???
You can read more at: [b][u]https://wowdev.wiki/DB/LightFloatBand[/b][/u]
 
5)      [b]LightSkybox.dbc[/b] – the simpliest Dbc of all, this file allows us to add skybox models, and edit their properties (such as transparency), we are not going to use this Dbc in our tutorial, but you can definetly go ahead and try experimenting with this one.
Collums:
1. Defines Id of each skybox model, this Id is then used in LightParams.dbc
2. Path to our model: „Environments/Stars/[MODEL].mdx“
3. Integer values flagy, defines properties of the model, such as transparency, 0 – skybox used animation based on time, 2 – shows Sun, Moon and clouds, skybox can be transparent, 4 – produces procedural mist. The most commonly used value is 2.
You can read more at: [b][u]https://wowdev.wiki/DB/LightSkybox[/b][/u]
 
Right now we have covered all the important things about the Dbc files. I admit there were lots of it, for sure you don't have to know all of it, but it is good to have a decent image of the structure. You can also read more at WoWDevWiki. Now we will proceed with the creation of a skybox.

[b]Creation of custom skybox:[/b]
Now lets try to make use of our newly gained knowledge of Light Dbc files and lets try producing a custom WoW skybox at Hyjal!
First of all, we need to get our client coordinates of the place – X=20540 Y= 11690 Z=1600
We can get these fairly easily in Noggit.

First we insert a new row in LightParams.dbc – 954. For now we can leave this row be, or we can copy parameters of some other row. We will return to this later.

 
Now we continue by adding a new row in Light.dbc –first of all lets write our X, Z,Y coordinates 3 multiplied by 36. Then we need to think of the inner and outer radius of our skybox. Lets say 1388 and 1666, once again we have to multiply these numbers by 36. After that we can insert the Id of our row from LightParams.dbc - 954.

 
Now lets move to the harder part – LightIntBand.dbc and LightFloatBand.dbc.
Lets continue with LightIntband.dbc. It is nessesary to open this Dbc files in WDBX editor. First we need to add 18 new lines starting with number:  954*18 – 17 down to number 954*18. To make things easier for us, it is always good to fill in all general datas to our newly added row, so that we can just copy it to all that will follow. All together we will be adding 3 phases of lightning – early morning – day – night. So we will use 3 collums of datas – se we will use 3 collums for time and 3 collums for data. First lets put in time value for morning phase, lets say we want to be from Midnight to 8:00, that means we put 960 (480 minutes * 2) into 3rd collum, day-time phase will be untill 19:00, that means 2280 will go into the 4th colum. Same datas can be used for following 17 rows, but it is not must do, you could have different number of phases for each setting.
Right now we can move to BGR codes, lets get back to our first row #(954*18 – 17) – starting with collum #19 there are our collums with BGR codes. Lets say we want our skybox to have purple-blue-white like colour. So we generate our colours using Color function. Do 19. We proceed with filling in datas for morning, day and night, for each setting (yep, it is lots of work). At this point I highly recommend you using the Dbc files attached for this tutorial, makes everything much simplier, and to elevate your understanding of topic, just spend some time playing with the Dbcs.
 
Now we are about to edit LightFloatBand.dbc. We no longer need to use WDBX editor, but you can surely use it if you feel comfortable in it. Once again we need to insert 6 new rows, once again their Ids need to correspond to our original Id in LightParams.dbc. The first row has to have Id:  954*6 - 6, 5 more rows follow.
 
We want it to be pretty foggy in the morning,lets set the fog distance in collum #19 (1st row) to 9000 , for following collums lets set the value a bit higher. Simillarly we go on with the next row, this time we put in values from 0 – 1. Next row we fill in 0s or 1s, this one shouldn't really convern us, next row is about cloud density, lets say we want morning to be clouds, whereas nights should be clear (it is good to work with this row in case you don't want to add in skybox model, which is our case). That is all for LightFloatBand.dbc.

Next Dbc is LightSkyBox.dbc, I don't want to put in any skybox model this time, so we are not going to use this Dbc. But feel free to give it a try yourself, it is a good starting exercise.
If we had added in custom skybox model, we would have returned back to LightParams.dbc to fill in our skybox model row Id, defaulty this value in LightParams.dbc should be set to 0. (Collum 3)
 
As of now we are done! Lets put all our edited Dbcs, blps and m2s into patch, and lets také a look what it looks like in-game
]]> https://elijahketchersid.com/forums/thread-26.html Tue, 28 Oct 2025 13:22:20 +0000 rektbyfaith]]> https://elijahketchersid.com/forums/thread-26.html https://www.wowmodding.net/topic/1559-hi...wotlk-335/

https://www.youtube.com/watch?v=jXYsRrva...ing.net%2F


Use any Terrain Editor that you want, i recommend: 
GAEA
There are two tools Included, THEY ARE NOT MADE BY ME:
(Had some Problems with Upload so i included the GDRIVE: (https://drive.google.com/drive/folders/1-fX4DQobVAS2P0s0BGLThIH6sj0P86v4?usp=sharing)
ObjtoADT and (FUTA) ill Inculde these Tools are included inside the Package
[b]HOW DOES IT WORK ?[/b]
It uses the two main keys for great Terrain Generation
OBJtoADT to print Model Height Data into an ADT.
Futa to Extract all 3 Layers into an ADT.
[b]HOW TO USE ?[/b]
Firstly you need to Generate a Terrain through your Favorite Terrain Generator, i use Gaea:
So i split the Terrain into 4 Pieces 
Heightmap:

and the 3 Layers:

So i have 4 Outputs:
Heightmap, Layer1, Layer2 and Layer3.
(1024 Heightmap and 4096 Layer1-3 Textures) 1k and 2k works aswell with the standart edition but loose a bit of quality.
As soon you have those Raw Files you need to Convert the Heightmap into an 3d Object with the ADT4x4 file Through The Displacement Modifier:

 
 
 
 
 
 
 
 
 
 
As soon youre done accept the modifier and copy the object into the OBJtoADT File:

Select the ADT_Template and Set Target inside the Modifier and Select your Terrain.
IMPORTANT: Now you need to lock every object or Hide them and only export the Objects from the Modifier like this 

The ADT_Template needs to be Hidden and press a to select everything now only the Objects from the Modifier Should be selected and Export the Object after the settings in the Folder: 

It should be named after your ADT File as an example NAME_1_1.obj -> NAME_1_1.adt you need todo that for every ADT Piece save it inside your OBJtoADT Folder and as soon you have it you need to put your Empty ADT Files inside that folder and run the OBJtoADT.bat which prints the Data inside your ADT.
Put your ADTs back and open Noggit and Add 3 Textures with it.
Open TerrainTextureGen i recommend adding the Addon ScriptstoButton there are 3 Scripts included you only need to Change the Path and press the Button to generate Layer1-3 Files otherwise they overwrite eachother.

You only need to Add your Textures inside the Given Image Nodes we have 3 Materials for Every Layer. Select the Material and click the Button Layer 1 it saves all 16 Textures in the Path you set inside the Scripts. Select the 2nd Material and button Layer 2 the same for the 3rd. The last step is to open Futa and import the Single images for all 16 ADTS. 
Thats it, some Result Pictures:]]> https://www.wowmodding.net/topic/1559-hi...wotlk-335/

https://www.youtube.com/watch?v=jXYsRrva...ing.net%2F


Use any Terrain Editor that you want, i recommend: 
GAEA
There are two tools Included, THEY ARE NOT MADE BY ME:
(Had some Problems with Upload so i included the GDRIVE: (https://drive.google.com/drive/folders/1-fX4DQobVAS2P0s0BGLThIH6sj0P86v4?usp=sharing)
ObjtoADT and (FUTA) ill Inculde these Tools are included inside the Package
[b]HOW DOES IT WORK ?[/b]
It uses the two main keys for great Terrain Generation
OBJtoADT to print Model Height Data into an ADT.
Futa to Extract all 3 Layers into an ADT.
[b]HOW TO USE ?[/b]
Firstly you need to Generate a Terrain through your Favorite Terrain Generator, i use Gaea:
So i split the Terrain into 4 Pieces 
Heightmap:

and the 3 Layers:

So i have 4 Outputs:
Heightmap, Layer1, Layer2 and Layer3.
(1024 Heightmap and 4096 Layer1-3 Textures) 1k and 2k works aswell with the standart edition but loose a bit of quality.
As soon you have those Raw Files you need to Convert the Heightmap into an 3d Object with the ADT4x4 file Through The Displacement Modifier:

 
 
 
 
 
 
 
 
 
 
As soon youre done accept the modifier and copy the object into the OBJtoADT File:

Select the ADT_Template and Set Target inside the Modifier and Select your Terrain.
IMPORTANT: Now you need to lock every object or Hide them and only export the Objects from the Modifier like this 

The ADT_Template needs to be Hidden and press a to select everything now only the Objects from the Modifier Should be selected and Export the Object after the settings in the Folder: 

It should be named after your ADT File as an example NAME_1_1.obj -> NAME_1_1.adt you need todo that for every ADT Piece save it inside your OBJtoADT Folder and as soon you have it you need to put your Empty ADT Files inside that folder and run the OBJtoADT.bat which prints the Data inside your ADT.
Put your ADTs back and open Noggit and Add 3 Textures with it.
Open TerrainTextureGen i recommend adding the Addon ScriptstoButton there are 3 Scripts included you only need to Change the Path and press the Button to generate Layer1-3 Files otherwise they overwrite eachother.

You only need to Add your Textures inside the Given Image Nodes we have 3 Materials for Every Layer. Select the Material and click the Button Layer 1 it saves all 16 Textures in the Path you set inside the Scripts. Select the 2nd Material and button Layer 2 the same for the 3rd. The last step is to open Futa and import the Single images for all 16 ADTS. 
Thats it, some Result Pictures:]]> https://elijahketchersid.com/forums/thread-25.html Tue, 28 Oct 2025 13:21:47 +0000 rektbyfaith]]> https://elijahketchersid.com/forums/thread-25.html https://www.wowmodding.net/topic/1549-no...%E2%99%A5/




https://www.youtube.com/watch?v=bjIuoF_C...ing.net%2F]]> https://www.wowmodding.net/topic/1549-no...%E2%99%A5/




https://www.youtube.com/watch?v=bjIuoF_C...ing.net%2F]]> https://elijahketchersid.com/forums/thread-24.html Tue, 28 Oct 2025 13:20:43 +0000 rektbyfaith]]> https://elijahketchersid.com/forums/thread-24.html Original Post: https://www.wowmodding.net/topic/1543-ho...it-on-725/



You must make your custom files on Noggit or you can get your maps modified parsed to Cata, MoP or WoD and convert this to Legion.
If you use the ADT Converter and you use "-l" this convert to Legion, but this can give error because the wdts, wdl and tex fails and the water dissapear. For fix this, you must parse your maps from Wotlk to Cata/MoP/WoD with this tool ADT Converter
After you must put on the data folder yours maps modified and you must make click in the .bat file, this parse alls files to WoD (Cata and mop too). Now you must download the script file and .bat modified for me, this files [u]Adt Converter to Legion[/u]
You must unrar, after you must edit the bat file and you find:
010editor "%%i" -script:"PATH\ADT-Legion-Conversion.1sc" "%%i" -nowarnings -noui
Now you must edit the PATH for your path folder of script file, after you save this.
After you must copy your ADTs files only from Cata/MoP/WoD to ADT folder and now you must click in the .bat. When this program closed, you must get the ADTs and put on the path folder patch (World/Maps/example/example.adt) in your World of Warcraft root folder.
Et voila, your maps it's working. (Delete WDT, WDL, TEX files for this work)
Like the post if you like it! and sorry for my english.
 
Credits: Luzifix (Adt Converter), Arektor (Script 010editor of Wod to Legion), Me, Darkkang for make the tutorial and the .bat file and testing this.
http://www.modcraft.io/index.php?topic=10780.0
http://www.modcraft.io/index.php?topic=13869.0



]]> Original Post: https://www.wowmodding.net/topic/1543-ho...it-on-725/



You must make your custom files on Noggit or you can get your maps modified parsed to Cata, MoP or WoD and convert this to Legion.
If you use the ADT Converter and you use "-l" this convert to Legion, but this can give error because the wdts, wdl and tex fails and the water dissapear. For fix this, you must parse your maps from Wotlk to Cata/MoP/WoD with this tool ADT Converter
After you must put on the data folder yours maps modified and you must make click in the .bat file, this parse alls files to WoD (Cata and mop too). Now you must download the script file and .bat modified for me, this files [u]Adt Converter to Legion[/u]
You must unrar, after you must edit the bat file and you find:
010editor "%%i" -script:"PATH\ADT-Legion-Conversion.1sc" "%%i" -nowarnings -noui
Now you must edit the PATH for your path folder of script file, after you save this.
After you must copy your ADTs files only from Cata/MoP/WoD to ADT folder and now you must click in the .bat. When this program closed, you must get the ADTs and put on the path folder patch (World/Maps/example/example.adt) in your World of Warcraft root folder.
Et voila, your maps it's working. (Delete WDT, WDL, TEX files for this work)
Like the post if you like it! and sorry for my english.
 
Credits: Luzifix (Adt Converter), Arektor (Script 010editor of Wod to Legion), Me, Darkkang for make the tutorial and the .bat file and testing this.
http://www.modcraft.io/index.php?topic=10780.0
http://www.modcraft.io/index.php?topic=13869.0



]]> https://elijahketchersid.com/forums/thread-23.html Tue, 28 Oct 2025 13:19:56 +0000 rektbyfaith]]> https://elijahketchersid.com/forums/thread-23.html Original Post: https://www.wowmodding.net/topic/1519-co...ustom-map/

Hiya,

Today I'm going to explain how to copy existing light setting to your own custom map.
[b]*Note: This will only work if you only use one light source.[/b]

For this tutorial you will need the following tools.

MyDbcEditor
Lightmapper
The first things you will need to do is decide which light settings you wish to copy. Once you have located that zone within World of Warcraft is it time to open Lightmapper. For this tutorial we are going for Lake sunspring in Nagrand.

Within Lightmapper navicate to the correct zone and search for the light.dbc entry (A red dot on the map) that is controlling your desired area. Memorize that ID number.



Head over to MyDbcEditor and open Light.dbc.
Search in the first column for the ID number we have found within lightmapper.

Right click on that ID line, Copy line to... and enter the last ID (of column one) plus one.
(Last ID is 2156, You enter 2157)

Edit column two to your map ID that can be found within map.dbc
Edit Column three, four and five to 0

[b]Left: Light.dbc Right: Map.dbc[/b]

Save light.dbc and place it within your your DBFilesClient folder inside your patch folder.
Succes! Your custom map should now have the copied light settings.
Thank you for reading, Be sure to ask any questions when needed.
Special thanks to Nightquest and Valium for helping me figure it out on skype.]]> Original Post: https://www.wowmodding.net/topic/1519-co...ustom-map/

Hiya,

Today I'm going to explain how to copy existing light setting to your own custom map.
[b]*Note: This will only work if you only use one light source.[/b]

For this tutorial you will need the following tools.

MyDbcEditor
Lightmapper
The first things you will need to do is decide which light settings you wish to copy. Once you have located that zone within World of Warcraft is it time to open Lightmapper. For this tutorial we are going for Lake sunspring in Nagrand.

Within Lightmapper navicate to the correct zone and search for the light.dbc entry (A red dot on the map) that is controlling your desired area. Memorize that ID number.



Head over to MyDbcEditor and open Light.dbc.
Search in the first column for the ID number we have found within lightmapper.

Right click on that ID line, Copy line to... and enter the last ID (of column one) plus one.
(Last ID is 2156, You enter 2157)

Edit column two to your map ID that can be found within map.dbc
Edit Column three, four and five to 0

[b]Left: Light.dbc Right: Map.dbc[/b]

Save light.dbc and place it within your your DBFilesClient folder inside your patch folder.
Succes! Your custom map should now have the copied light settings.
Thank you for reading, Be sure to ask any questions when needed.
Special thanks to Nightquest and Valium for helping me figure it out on skype.]]> https://elijahketchersid.com/forums/thread-22.html Tue, 28 Oct 2025 13:19:17 +0000 rektbyfaith]]> https://elijahketchersid.com/forums/thread-22.html Original Post: https://www.wowmodding.net/topic/1516-im...to-noggit/


First of all, why the heck do I even bother with something what seems to be so basic? Well, apparently it is not, because there are a few tips and tricks which aren't very commonly known, at least beginners don't know them and there's no tutorial really describing them. I will also link my simple WIP tool which can be very usefull for you here. I will start with things you probably do already know, if that bothers you, just skip to the last heading.

First of all, how can we get models into our map in Noggit? A short list of possibilities:

• Ctrl+c and ctrl+v. No magic hidden here.
  
• Import from MV.
  
• Import from a text file (Import.txt).
  

Import from MV

MV is a model viewer. WoW Model Viewer is an application which enables you to browse WoW models. Great thing, but here comes a problem - current Noggit's import functions aren't compatible with quite a lot of WMV's versions. As far as I know, importing WMOs in general tends to work. In order to import models from WMV, simply change ImportPath in noggit.conf, so it points to log.txt file in userSettings folder in your WMV's folder. An example follows.:

ImportFile = D:\Modding\Projekty\Arathor\WMV\userSettings\log.txt

When you have this set, you can simply open a WMV, select a model, then go to Noggit and shift+c to import M2, alt+c to import WMO. There were slightly bugged versions of Noggit where both shortcuts actually imported M2, keep this on mind please. The newest version should have this fixed by now.

If your import functions don't work (mostly M2 tends to not), you can try a different version of WMV. Version which is definitely compatible with Noggit's import function for M2s can be downloaded on Modcraft.:

http://modcraft.superparanoid.de/viewtopic.php?f=48&t=4797

The problem is, that this version is really an ancient one, and tends to crash frequently, especially when it comes to retro-ported stuff.

Import from text file

Import.txt is a file located in Noggit's installation folder. It contains paths to models separeted by line breaks. You can delete models from here simply by opening a file and deleting them. To reload a file, just deselect any model you may have selected in Noggit and go to Assist menu, choose To Text File function, and here you go, Import file is reloaded. If you have any model selected while clicking on To Text File button, its path will be written at the end of the file. This can be very useful when you need to copy a model from different map, or when you need to copy multiple models. To acces list of models in your Import.txt, simply go to Assist menu and click on From Text File. Then you can just start clicking on model names and models will appear on your mouse cursor or in model you have currently selected, or on selected coordinates, if Auto select mode in Edit menu is turned off (does anyone even use this thing?).

So, why this tutorial? Where are those secret tips?

Yep, its a little bit strange to write them at the end of tutorial which was supposed to be dedicated to this, but I needed to explain stuff above. Import.txt is actually quite a powerful thing to use, as long as you can get list of models you want to import into Noggit, separated by line breaks, and filter them. Such lists do exist in WoW - they are called listfiles. In each MPQ, you can find (listfile) (as long as it wasn't made as listfile-free MPQ). (listfile) is a list of all file paths to all files in MPQ. And we will make a good use of this. First of all, download my Toolkit. Its a WIP application and poorly written, I've got to admit, but it works for what we are going to do with it absolutely fine. There's also a simple .bat included.:

https://www.dropbox.com/s/hh8i859hb9ebxve/AmarothsToolkit.rar?dl=0

Open your WMV. Go to File menu and select Export textures... option. In new panel which appears, make sure that Path preserved option is checked. Then just browse M2s. Everytime you find some you want to use, just click on Export all button in panel which have appeared. In the end, you will have model files in Export folder in WMV's directory, and they will be all in paths into which they belong.

Now, you have basically two options. You can either place cleanup.bat script into Export folder and run it. It will delete all .skin and .blp files in all directories in Export folder. If you want to change list of extensions which should be deleted, simply right-click that cleanup.bat, click on Edit and you surely will figure out how to change it on your own. Then create a new, empty MPQ and place all folders in Export directory into it. The second option is skipping whole cleanup.bat part and continuing to another paragraph of this tutorial.

When you have any sort of MPQ with (listfile) which contains files you don't want to use in Import.txt (like BLPs, SKINs or maybe even more stuff, it may be your server's patch you are giving to players or whatever else), you need to clean that (listfile) from all things you don't want to have there. To do this, just extract (listfile) from that MPQ and place it whenever you like. Then run my Toolkit application and set extracted (listfile) as input file. For this purpouse, you will want to use cleanup filter, which is that big panel on the left. Select extensions you want to keep in listfile (most likely .M2 and Root-only .WMO). You can also select path prefixes to keep only models from certain directory, for example, you can keep only files from World folders. You can also modify filters by using those 2 buttons and text input under filters, so you can add filter to World\Expansion02\ directory, for example. For more info, follow a Manual. When all your settings are done, just click on Cleanup Listfile button and save cleaned listfile whenever you want. If you have made a MPQ which already contains only M2 files, its (listfile) will, obviously, contain also only M2s (and (listfile) and (attributes) most likely), so you can basically use that (listfile)'s content without even filtering it by my Toolkit.

Now just open that cleaned and filtered listfile, press ctrl+a (or select just some particular models you wanted to use), ctrl+c, open Import.txt, ctrl+v, ctrl+s, use To Text File function in Noggit to reload import file and you are done, you have your models in Noggit.

This all can seem a little bit complicated, but when you learn how to do this and won't need to look any manual up for that, you will actually be able to quickly get lists of even hundreds or thousands file paths and filter them by using my Toolbox to get files you wanted, the only problem is exporting model files via WMV, if you need to do that (so, if you need to select just a few certain models rather then just use whole folder for example).

One final tip. You can also create a (listfile) of all file paths in WoW and then just always get only models from some certain directories by using my Toolbox. Lets say you want all World\Expansion02\Coldarra\ models. If you already have prepared merged (listfile) of all WoW files, my Toolkit is actually very fast and easy way of getting all those models directly into Import.txt. Just open Toolkit, choose merged (listfile) as an input file, write World\Expansion02\Coldarra\ under filters, click on Add path prefix button, make that filter checked, click on Cleanup Listfile and... done.

And one now really final tip. Extensions filter may be actually used also for ends of file names (like keg.m2, instead of just .m2). Path prefix filter can, on the other hand, be also used for name prefixes, like World/Custom/am_. Sadly, its (for now) limited for use on only one directory. This will get all am_ files, but only in World/Custom/ folder. Both extension and prefix filters aren't case-sensitive.

English YT tutorial channel. Check it out if you preffer videos over walls of text.:
https://www.youtube.com/AmarothEng
I am now completely retired from modding. I am still reading PMs and reacting to them, however, I am not keeping up to date with what is going on in the community and my ability to help you is becoming very limited - I no longer remember some things, I don't have tools installed anymore, and I don't know what is up to date nowadays.]]> Original Post: https://www.wowmodding.net/topic/1516-im...to-noggit/


First of all, why the heck do I even bother with something what seems to be so basic? Well, apparently it is not, because there are a few tips and tricks which aren't very commonly known, at least beginners don't know them and there's no tutorial really describing them. I will also link my simple WIP tool which can be very usefull for you here. I will start with things you probably do already know, if that bothers you, just skip to the last heading.

First of all, how can we get models into our map in Noggit? A short list of possibilities:

• Ctrl+c and ctrl+v. No magic hidden here.
  
• Import from MV.
  
• Import from a text file (Import.txt).
  

Import from MV

MV is a model viewer. WoW Model Viewer is an application which enables you to browse WoW models. Great thing, but here comes a problem - current Noggit's import functions aren't compatible with quite a lot of WMV's versions. As far as I know, importing WMOs in general tends to work. In order to import models from WMV, simply change ImportPath in noggit.conf, so it points to log.txt file in userSettings folder in your WMV's folder. An example follows.:

ImportFile = D:\Modding\Projekty\Arathor\WMV\userSettings\log.txt

When you have this set, you can simply open a WMV, select a model, then go to Noggit and shift+c to import M2, alt+c to import WMO. There were slightly bugged versions of Noggit where both shortcuts actually imported M2, keep this on mind please. The newest version should have this fixed by now.

If your import functions don't work (mostly M2 tends to not), you can try a different version of WMV. Version which is definitely compatible with Noggit's import function for M2s can be downloaded on Modcraft.:

http://modcraft.superparanoid.de/viewtopic.php?f=48&t=4797

The problem is, that this version is really an ancient one, and tends to crash frequently, especially when it comes to retro-ported stuff.

Import from text file

Import.txt is a file located in Noggit's installation folder. It contains paths to models separeted by line breaks. You can delete models from here simply by opening a file and deleting them. To reload a file, just deselect any model you may have selected in Noggit and go to Assist menu, choose To Text File function, and here you go, Import file is reloaded. If you have any model selected while clicking on To Text File button, its path will be written at the end of the file. This can be very useful when you need to copy a model from different map, or when you need to copy multiple models. To acces list of models in your Import.txt, simply go to Assist menu and click on From Text File. Then you can just start clicking on model names and models will appear on your mouse cursor or in model you have currently selected, or on selected coordinates, if Auto select mode in Edit menu is turned off (does anyone even use this thing?).

So, why this tutorial? Where are those secret tips?

Yep, its a little bit strange to write them at the end of tutorial which was supposed to be dedicated to this, but I needed to explain stuff above. Import.txt is actually quite a powerful thing to use, as long as you can get list of models you want to import into Noggit, separated by line breaks, and filter them. Such lists do exist in WoW - they are called listfiles. In each MPQ, you can find (listfile) (as long as it wasn't made as listfile-free MPQ). (listfile) is a list of all file paths to all files in MPQ. And we will make a good use of this. First of all, download my Toolkit. Its a WIP application and poorly written, I've got to admit, but it works for what we are going to do with it absolutely fine. There's also a simple .bat included.:

https://www.dropbox.com/s/hh8i859hb9ebxve/AmarothsToolkit.rar?dl=0

Open your WMV. Go to File menu and select Export textures... option. In new panel which appears, make sure that Path preserved option is checked. Then just browse M2s. Everytime you find some you want to use, just click on Export all button in panel which have appeared. In the end, you will have model files in Export folder in WMV's directory, and they will be all in paths into which they belong.

Now, you have basically two options. You can either place cleanup.bat script into Export folder and run it. It will delete all .skin and .blp files in all directories in Export folder. If you want to change list of extensions which should be deleted, simply right-click that cleanup.bat, click on Edit and you surely will figure out how to change it on your own. Then create a new, empty MPQ and place all folders in Export directory into it. The second option is skipping whole cleanup.bat part and continuing to another paragraph of this tutorial.

When you have any sort of MPQ with (listfile) which contains files you don't want to use in Import.txt (like BLPs, SKINs or maybe even more stuff, it may be your server's patch you are giving to players or whatever else), you need to clean that (listfile) from all things you don't want to have there. To do this, just extract (listfile) from that MPQ and place it whenever you like. Then run my Toolkit application and set extracted (listfile) as input file. For this purpouse, you will want to use cleanup filter, which is that big panel on the left. Select extensions you want to keep in listfile (most likely .M2 and Root-only .WMO). You can also select path prefixes to keep only models from certain directory, for example, you can keep only files from World folders. You can also modify filters by using those 2 buttons and text input under filters, so you can add filter to World\Expansion02\ directory, for example. For more info, follow a Manual. When all your settings are done, just click on Cleanup Listfile button and save cleaned listfile whenever you want. If you have made a MPQ which already contains only M2 files, its (listfile) will, obviously, contain also only M2s (and (listfile) and (attributes) most likely), so you can basically use that (listfile)'s content without even filtering it by my Toolkit.

Now just open that cleaned and filtered listfile, press ctrl+a (or select just some particular models you wanted to use), ctrl+c, open Import.txt, ctrl+v, ctrl+s, use To Text File function in Noggit to reload import file and you are done, you have your models in Noggit.

This all can seem a little bit complicated, but when you learn how to do this and won't need to look any manual up for that, you will actually be able to quickly get lists of even hundreds or thousands file paths and filter them by using my Toolbox to get files you wanted, the only problem is exporting model files via WMV, if you need to do that (so, if you need to select just a few certain models rather then just use whole folder for example).

One final tip. You can also create a (listfile) of all file paths in WoW and then just always get only models from some certain directories by using my Toolbox. Lets say you want all World\Expansion02\Coldarra\ models. If you already have prepared merged (listfile) of all WoW files, my Toolkit is actually very fast and easy way of getting all those models directly into Import.txt. Just open Toolkit, choose merged (listfile) as an input file, write World\Expansion02\Coldarra\ under filters, click on Add path prefix button, make that filter checked, click on Cleanup Listfile and... done.

And one now really final tip. Extensions filter may be actually used also for ends of file names (like keg.m2, instead of just .m2). Path prefix filter can, on the other hand, be also used for name prefixes, like World/Custom/am_. Sadly, its (for now) limited for use on only one directory. This will get all am_ files, but only in World/Custom/ folder. Both extension and prefix filters aren't case-sensitive.

English YT tutorial channel. Check it out if you preffer videos over walls of text.:
https://www.youtube.com/AmarothEng
I am now completely retired from modding. I am still reading PMs and reacting to them, however, I am not keeping up to date with what is going on in the community and my ability to help you is becoming very limited - I no longer remember some things, I don't have tools installed anymore, and I don't know what is up to date nowadays.]]> https://elijahketchersid.com/forums/thread-21.html Tue, 28 Oct 2025 13:18:31 +0000 rektbyfaith]]> https://elijahketchersid.com/forums/thread-21.html Original Post: https://www.wowmodding.net/topic/1511-le...gn-basics/

Hello, Model-Changing Network. In this article I am going to speak about my thoughts on the way [b]level design[/b] should work in World of Warcraft, so it may come handy for those who want to create custom zones.
This is not going to be a how-to or step by step tutorial. That's more like an overview of basic steps, principles, tricks and many other things that I suspect Blizzard using in creation of their content. Opinions expressed here are entirely my own and may come not quite correct in reality, as I am not a professional level designer. Though, anyway that's what I think to be correct and from my own experience it works out pretty well.
Zone concept
The first thing that any zone requires for sure is the concept. You can't just create a random zone that has no purpose and idea behind it and expect it to look great. I am more than sure that random creations should not serve any purposes other than tests. And even tests actually have a little idea behind such as testing a new terrain style, testing tools or testing your own capabilities. 
Atmosphere and general story
I think that atmosphere and basic storyline are those two parts you should start designing your zone with. They should actually be developed simultaneously while you are thinking your concept over. The first thing you need to decide is what for you are creating a zone. Think a little of the events that you are going to add there. Don't try to come up with a detailed storyline and try to avoid making up characters that are going to participate in the questline of the zone. That's always too much for the first step. Just decide what race this zone will be dedicated to, what kind of major event is going to take place there (to say, is it gonna be a battlefield, a peaceful forest or a creepy dark canyon full of spiders). 
After this part, comes the atmoshpere. Imagine the places you want to build there. Think of the overall atmosphere things like texture color scheme, possible doodads, lighting and so on. Just get an imaginary picture of how the entire thing should look like.
When you are done coming up with atmosphere ideas you can start thinking of somme particular places of interest, questing spots and other little things that you may want to havve in your zone. It is actually required for the next step of concept designing which is related to drawing a quick sketch of your zone. Anyway, if you have any particular atmosphere ideas about these places you can either think of them now or later during the actual zone development.
Map sketch
As I said previously, this step presupposes making of the map sketch. It is [b]required [/b]for any zone if you want to make it look logical, natural and interesting to travel around when you are playing there. I have heard from a couple of guys that it is bad doing those "map plans" as in the end your zone simply turns out different from how you planned it to look like. Well, yes, they are kind of right as in the process of development you are trying to adjust your ideas and imaginary images from your mind to the capabilities of the game engine which is not always possible. That's quite normal and happens all the time, but you can change your plan any time, right? Most game developers do it, Blizzard devs do it and so we should.

Here is the image of that kind shown by Blizzard designers in the Arcraft series (I highly recommend you to read them as they contain quite a lot of design information and describe some parts of the zone creation process. Yet, they are far from being detailed enough to teach you doing something from scratch.)
As you can see on the picture, the map contains all the significant places such as towns, camps, dungeons, questing spots and so on. Different colors indicate different terrain height (usual cartography rules for doing that are quite well known: ranges from dark green to dark brown). The problem here is that this map again contains half of the information that is required for designing the zone from scratch. Blizzard is a big company and the work in designing a zone is divided by many people. As we are modders and sadly do not usually own enough of the human resources to separate the work, we most often have to do everything or our own or sharing the work with only a couple of people. Thus, you also need to think about how the player interacts with the zone, the way he goes through the the questing chains. This is usually the infromation you base the road and places of interest (POI) location on. You can draw arrows to see how the player will follow the story to avoid concentrating all the action in one part of the zone or focring player to cross the entire zone all over and over again (a little problem of classic WoW quest design, I have to admit). ]]> Original Post: https://www.wowmodding.net/topic/1511-le...gn-basics/

Hello, Model-Changing Network. In this article I am going to speak about my thoughts on the way [b]level design[/b] should work in World of Warcraft, so it may come handy for those who want to create custom zones.
This is not going to be a how-to or step by step tutorial. That's more like an overview of basic steps, principles, tricks and many other things that I suspect Blizzard using in creation of their content. Opinions expressed here are entirely my own and may come not quite correct in reality, as I am not a professional level designer. Though, anyway that's what I think to be correct and from my own experience it works out pretty well.
Zone concept
The first thing that any zone requires for sure is the concept. You can't just create a random zone that has no purpose and idea behind it and expect it to look great. I am more than sure that random creations should not serve any purposes other than tests. And even tests actually have a little idea behind such as testing a new terrain style, testing tools or testing your own capabilities. 
Atmosphere and general story
I think that atmosphere and basic storyline are those two parts you should start designing your zone with. They should actually be developed simultaneously while you are thinking your concept over. The first thing you need to decide is what for you are creating a zone. Think a little of the events that you are going to add there. Don't try to come up with a detailed storyline and try to avoid making up characters that are going to participate in the questline of the zone. That's always too much for the first step. Just decide what race this zone will be dedicated to, what kind of major event is going to take place there (to say, is it gonna be a battlefield, a peaceful forest or a creepy dark canyon full of spiders). 
After this part, comes the atmoshpere. Imagine the places you want to build there. Think of the overall atmosphere things like texture color scheme, possible doodads, lighting and so on. Just get an imaginary picture of how the entire thing should look like.
When you are done coming up with atmosphere ideas you can start thinking of somme particular places of interest, questing spots and other little things that you may want to havve in your zone. It is actually required for the next step of concept designing which is related to drawing a quick sketch of your zone. Anyway, if you have any particular atmosphere ideas about these places you can either think of them now or later during the actual zone development.
Map sketch
As I said previously, this step presupposes making of the map sketch. It is [b]required [/b]for any zone if you want to make it look logical, natural and interesting to travel around when you are playing there. I have heard from a couple of guys that it is bad doing those "map plans" as in the end your zone simply turns out different from how you planned it to look like. Well, yes, they are kind of right as in the process of development you are trying to adjust your ideas and imaginary images from your mind to the capabilities of the game engine which is not always possible. That's quite normal and happens all the time, but you can change your plan any time, right? Most game developers do it, Blizzard devs do it and so we should.

Here is the image of that kind shown by Blizzard designers in the Arcraft series (I highly recommend you to read them as they contain quite a lot of design information and describe some parts of the zone creation process. Yet, they are far from being detailed enough to teach you doing something from scratch.)
As you can see on the picture, the map contains all the significant places such as towns, camps, dungeons, questing spots and so on. Different colors indicate different terrain height (usual cartography rules for doing that are quite well known: ranges from dark green to dark brown). The problem here is that this map again contains half of the information that is required for designing the zone from scratch. Blizzard is a big company and the work in designing a zone is divided by many people. As we are modders and sadly do not usually own enough of the human resources to separate the work, we most often have to do everything or our own or sharing the work with only a couple of people. Thus, you also need to think about how the player interacts with the zone, the way he goes through the the questing chains. This is usually the infromation you base the road and places of interest (POI) location on. You can draw arrows to see how the player will follow the story to avoid concentrating all the action in one part of the zone or focring player to cross the entire zone all over and over again (a little problem of classic WoW quest design, I have to admit). ]]> https://elijahketchersid.com/forums/thread-20.html Tue, 28 Oct 2025 13:17:59 +0000 rektbyfaith]]> https://elijahketchersid.com/forums/thread-20.html Original Post: https://www.wowmodding.net/topic/1501-obj2adt-how-to/

So firstly you need to download the ObjToAdt tool from here. it's a java app so you also need to setup java on your PC. In the comment section of this tool you can find adt_template.rar so download it too and extract it somewhere.
When everything is ready run blender and open up adt_template.blend in it. You will see something like that:

So in the outliner panel you can see all of our objects and if you wanted to start sculpting your terrain then you need to follow those steps:
- Select object that named as Clear_Terrain_Template
- Switch to modifiers panel
- Set nomber of adts you want to have in a row (1)
- Set number of adts you want to have in a column (2)
- Hit apply on both modifiers
- Swith to Sculpt mode and start sculpting

When you are ready with your sculpting then you need to:
- Select ADT_TEMPLATE object (1)
- Make it visible (2)
- Go to modifiers panel again and in target select your sculpting. This time we don't need to apply this mod (3)

Now while holding ctrl drag ADT_TEMPLATE by X and Y to place it in needed position( better to do this in top view)

Then select all obects by pressing A key(two times actually, one for deselecting all and second to select all) and press H key to hide them. Then at the bottom you can see some script. Change 1 to 0 in it and press Run Script button. 256 obects will appear here. Select all of them (A key) and export to obj.Export settings:]]> Original Post: https://www.wowmodding.net/topic/1501-obj2adt-how-to/

So firstly you need to download the ObjToAdt tool from here. it's a java app so you also need to setup java on your PC. In the comment section of this tool you can find adt_template.rar so download it too and extract it somewhere.
When everything is ready run blender and open up adt_template.blend in it. You will see something like that:

So in the outliner panel you can see all of our objects and if you wanted to start sculpting your terrain then you need to follow those steps:
- Select object that named as Clear_Terrain_Template
- Switch to modifiers panel
- Set nomber of adts you want to have in a row (1)
- Set number of adts you want to have in a column (2)
- Hit apply on both modifiers
- Swith to Sculpt mode and start sculpting

When you are ready with your sculpting then you need to:
- Select ADT_TEMPLATE object (1)
- Make it visible (2)
- Go to modifiers panel again and in target select your sculpting. This time we don't need to apply this mod (3)

Now while holding ctrl drag ADT_TEMPLATE by X and Y to place it in needed position( better to do this in top view)

Then select all obects by pressing A key(two times actually, one for deselecting all and second to select all) and press H key to hide them. Then at the bottom you can see some script. Change 1 to 0 in it and press Run Script button. 256 obects will appear here. Select all of them (A key) and export to obj.Export settings:]]> https://elijahketchersid.com/forums/thread-19.html Tue, 28 Oct 2025 13:17:06 +0000 rektbyfaith]]> https://elijahketchersid.com/forums/thread-19.html Original Post: https://www.wowmodding.net/topic/1496-ho...mment-7944

Today i will explain how to port your Vanilla\BC\WotLK Maps to WoD.
What you will need:
Your map
MyDBCEditor
Pagdzin & Mjollná ADT converter
PhilipTNG's ADT LK to MoP/WoD Converter
Rangorn's WdtSupplies
A WoD Server
Step 1: Modify DBC files.
Go to your server's folder and copy the "Map.dbc" and "MapDifficulty.dbc" to your DBFilesClient in your WoD Folder.
Now right click the Azeoth entry, and select "Copy line to". Now write in the Map ID you want to use. I am gonna use the map id 3000.
Once copied, it should show you the new map id you have added. Now we need to modify it to your needs.
The first column says "Azeroth" This is the internal name aka what you want the map folder to be called. I am gonna call it "SuperCoolLand". The next name you will see is "Eastern Kingdoms" This is the ingame name, choose whatever you want here.
There is alot of different columns, but for now let's save it and open up MapDifficulty.dbc
Now this may look complicated, but it's actually pretty easy. Right click the ID column and click "Insert Line". Now write an unique id, im gonna pick 5000. 
You should now be at your new line. The second column is gonna show a "0". You will need to change that to your map id. So im gonna write 3000. 
Save the file and copy the your modified dbc files to the server's dbc folder. Now you should have your dbc files both in the client and the server.
Step 2: Converting the ADT's
There are two ways of converting the adt's. Pagdzin & Mjollná ADT converter or PhilipTNG's ADT LK to MoP/WoD Converter.
Pagdzin & Mjollná's is the fastest one. But it only works with blizzard adt's or older noggit modified adt's
PhilipTNG's works on all adts, but is quite slow at converting them.
If you are unsure which one to use, Philip's is usually the best one.
I'm gonna tell how to use both.
Step 2.1: Using Pagdzin & Mjollná ADT converter 
Download the tools and extract the folder to wherever you want. Open the "adtconverter.conf" and modify the "directory=" to where you want the converted adt's to be written.
Save the file and open up "ADT Converter.jar". You can now choose if you want "Retail" or "World building". I'm gonna select the second option.
Now click file, open and navigate to the directory with your WotLK adt's. Once you have found it, click "Open" and let the converter do it's thing.
Once it's done, you should be able to find your freshly made adt's in the folder to choosed above.
Make sure that for every adt that there is an:
_tex0.adt
_tex1.adt
_obj0.adt
_obj1.adt
If the tex1 and obj1 is missing, just copy the tex0 and obj0 and rename them to tex1 and obj1. 
Copy the adt's to your WoD folder's "World\Maps\Whatever your continent is called"
Step 2.2: Using PhilipTNG's ADT LK to MoP/WoD Converter.
Once you have downloaded the tools, extract the folder to the root of your C: drive (this is important!). The path should be like this:
C:\PTNG_ADT_Converter
Now, copy your ADT files to the "ToBeVerted" folder. Once they have been copied, run the "WC_ADT_Convert.bat" file.
This takes longer depending on how many adt's you have. 
While it's running, don't copy or paste anything, or you might break something.
Once it's done it's thing. You should now have some new adt's in the "Finished" folder. Make sure that for every adt that there is an:
_tex0.adt
_tex1.adt
_obj0.adt
_obj1.adt
If the tex1 and obj1 is missing, just copy the tex0 and obj0 and rename them to tex1 and obj1. 
Copy the adt's to your WoD folder's "World\Maps\Whatever your continent is called"
Step 3: Creating other needed stuff.
Now we need to use WdtSupplies to create some other needed files for WoD.
Extract WdtSupplies and move your wdt file to the same folder. Open a new command prompt at the same location (Shift+Right click and select "New command prompt here") and write the following:
java -jar WdtSupplies.jar NameOfWdt.wdt
The Program will now generate the following files:
*.wdl
*.tex
*_occ.wdt
*_lgt.wdt
It might take a few minutes, so be patient. 
Once done, copy the new files to your continent folder.
Now launch up your server, teleport to your contient and it should work!
FAQ:
"I Used Pagdzin & Mjollná ADT converter but there is no adt's in the output folder?"
Make sure that the directory is the same, as you wrote in adtconverter.conf. If that's correct, try use the other option (Retail). If it still doesn't work, try use the other converter.

"Terrain is green in the distance, but when i get closer it gets it right texture."
This is caused by the *.tex file, it's for low resolution texture. The only way to fix this, is to take an tex file from another map, that uses the same textures as your own.
"How do i port my WotLK maps to Cata or MoP?"
For Cata and MoP, you don't need to modify MapDifficulty.dbc and you don't need the _occ and _lgt file. Everything else is mostly the same.
 ]]> Original Post: https://www.wowmodding.net/topic/1496-ho...mment-7944

Today i will explain how to port your Vanilla\BC\WotLK Maps to WoD.
What you will need:
Your map
MyDBCEditor
Pagdzin & Mjollná ADT converter
PhilipTNG's ADT LK to MoP/WoD Converter
Rangorn's WdtSupplies
A WoD Server
Step 1: Modify DBC files.
Go to your server's folder and copy the "Map.dbc" and "MapDifficulty.dbc" to your DBFilesClient in your WoD Folder.
Now right click the Azeoth entry, and select "Copy line to". Now write in the Map ID you want to use. I am gonna use the map id 3000.
Once copied, it should show you the new map id you have added. Now we need to modify it to your needs.
The first column says "Azeroth" This is the internal name aka what you want the map folder to be called. I am gonna call it "SuperCoolLand". The next name you will see is "Eastern Kingdoms" This is the ingame name, choose whatever you want here.
There is alot of different columns, but for now let's save it and open up MapDifficulty.dbc
Now this may look complicated, but it's actually pretty easy. Right click the ID column and click "Insert Line". Now write an unique id, im gonna pick 5000. 
You should now be at your new line. The second column is gonna show a "0". You will need to change that to your map id. So im gonna write 3000. 
Save the file and copy the your modified dbc files to the server's dbc folder. Now you should have your dbc files both in the client and the server.
Step 2: Converting the ADT's
There are two ways of converting the adt's. Pagdzin & Mjollná ADT converter or PhilipTNG's ADT LK to MoP/WoD Converter.
Pagdzin & Mjollná's is the fastest one. But it only works with blizzard adt's or older noggit modified adt's
PhilipTNG's works on all adts, but is quite slow at converting them.
If you are unsure which one to use, Philip's is usually the best one.
I'm gonna tell how to use both.
Step 2.1: Using Pagdzin & Mjollná ADT converter 
Download the tools and extract the folder to wherever you want. Open the "adtconverter.conf" and modify the "directory=" to where you want the converted adt's to be written.
Save the file and open up "ADT Converter.jar". You can now choose if you want "Retail" or "World building". I'm gonna select the second option.
Now click file, open and navigate to the directory with your WotLK adt's. Once you have found it, click "Open" and let the converter do it's thing.
Once it's done, you should be able to find your freshly made adt's in the folder to choosed above.
Make sure that for every adt that there is an:
_tex0.adt
_tex1.adt
_obj0.adt
_obj1.adt
If the tex1 and obj1 is missing, just copy the tex0 and obj0 and rename them to tex1 and obj1. 
Copy the adt's to your WoD folder's "World\Maps\Whatever your continent is called"
Step 2.2: Using PhilipTNG's ADT LK to MoP/WoD Converter.
Once you have downloaded the tools, extract the folder to the root of your C: drive (this is important!). The path should be like this:
C:\PTNG_ADT_Converter
Now, copy your ADT files to the "ToBeVerted" folder. Once they have been copied, run the "WC_ADT_Convert.bat" file.
This takes longer depending on how many adt's you have. 
While it's running, don't copy or paste anything, or you might break something.
Once it's done it's thing. You should now have some new adt's in the "Finished" folder. Make sure that for every adt that there is an:
_tex0.adt
_tex1.adt
_obj0.adt
_obj1.adt
If the tex1 and obj1 is missing, just copy the tex0 and obj0 and rename them to tex1 and obj1. 
Copy the adt's to your WoD folder's "World\Maps\Whatever your continent is called"
Step 3: Creating other needed stuff.
Now we need to use WdtSupplies to create some other needed files for WoD.
Extract WdtSupplies and move your wdt file to the same folder. Open a new command prompt at the same location (Shift+Right click and select "New command prompt here") and write the following:
java -jar WdtSupplies.jar NameOfWdt.wdt
The Program will now generate the following files:
*.wdl
*.tex
*_occ.wdt
*_lgt.wdt
It might take a few minutes, so be patient. 
Once done, copy the new files to your continent folder.
Now launch up your server, teleport to your contient and it should work!
FAQ:
"I Used Pagdzin & Mjollná ADT converter but there is no adt's in the output folder?"
Make sure that the directory is the same, as you wrote in adtconverter.conf. If that's correct, try use the other option (Retail). If it still doesn't work, try use the other converter.

"Terrain is green in the distance, but when i get closer it gets it right texture."
This is caused by the *.tex file, it's for low resolution texture. The only way to fix this, is to take an tex file from another map, that uses the same textures as your own.
"How do i port my WotLK maps to Cata or MoP?"
For Cata and MoP, you don't need to modify MapDifficulty.dbc and you don't need the _occ and _lgt file. Everything else is mostly the same.
 ]]>