Blank WMO

[Scytheria23]

Hi folks,

I wonder if anyone can help me by making (or explaining how to make) a blank WMO?  Essentially, one I can rename and use in a patch to easily remove unwanted WMOs from maps.  The idea is to replace an existing WMO file with one that has no mesh data.  I know noggit could remove them entirely, but I am editing some MOP maps which do not work in noggit.

I've tried creating a blank myself, but I'm lacking info on what to delete from a WMO file to leave just a header.  Everything I've tried just results in crashes.  I've used the same technique to remove unwanted M2s, which was easy, so I guess the same approach can work here.

Thanks in advance for your help/suggestions.
Scy

[abdalrahman9]

What i would do is just create a custom wmo with no vertices and just replace them that way. Using of course Mirror Machine.

[kojak488]

What i would do is just create a custom wmo with no vertices and just replace them that way. Using of course Mirror Machine.

Errors out when trying to convert a blank WMO, at least when I tried that in the past.

[schlumpf]

Deleting everything should be quite fine. Have you tried looking in the wiki to see what the blocks mean? wowdev.wiki

[abdalrahman9]

What i would do is just create a custom wmo with no vertices and just replace them that way. Using of course Mirror Machine.

Errors out when trying to convert a blank WMO, at least when I tried that in the past.

Well to tell you the truth, i never tried so i wasn't too sure. You could be right though

Deleting everything should be quite fine. Have you tried looking in the wiki to see what the blocks mean? wowdev.wiki

Maybe if Scytheria tries it, he can tell us if it works or not.

[Scytheria23]

I'm struggling to understand the WMO file structure to be honest.  I would prefer to use Noggit to remove the unwanted WMOs and M2s (a much cleaner method), but I'm also having trouble with some strange entry heights (on entering a modified map in-game, the camera defaults to a position high above the map and the character falls into infinity).  I know this is fixable (having read about similar issues being solved), but sadly, the ADT file structure is even less fathomable to me and unfortunately those who have marked their issues as solved have not specified how they solved them.

Does anyone know of a better guide to the ADT file structure?  I can see the 256 chunks clearly enough when I open one with a hex editor, but I've no idea what the rest means.

I'll keep plugging away and let you know of any progress.

Oh, and 'he' is a 'she'. :shock:
Scy

[schlumpf]

both file structures are quite easy to follow if you see how chunked files work: always look at 4 bytes of chunk identifier, then a 4 byte size and size bytes data. eg {'MVER', 4, {17}}.

The ADT issue you reference is an error in MFBO chunks. To fix it, iterate chunks (look at 4 byte magic and check if correct one, look at 4 byte size and skip size bytes until your find the correct magic) until the first (and only) MFBO chunk. There, interpret the data given as described in http://wowdev.wiki/index.php?tit ... MFBO_chunk. To fix it without thinking about reality, let maximum be all the maximum value of a short (32767) and minimum -32767. To make the iterating easier, just look at the very end of the file, MFBO is one of the last ones, if not the last.
The 256 "chunks" of an ADT refer to the 256 MCNK chunks which have sub chunks. There, it will be [{'MCNK', size, {0x80 bytes of header, [more chunks of ]}}…].

I usually link my by now 8 years old guide about this topic: http://www.ownedcore.com/forums/world-o ... iting.html -- it probably is horrible by modern standards.

I will at some point install a filter that replaces all 'he' or 'she' by 'xhe' to avoid confusion.

[Scytheria23]

Many thanks for this information, Schlumpf.  I feel the issue is on the brink of resolution.

The offending MFBO information is, indeed, at the very end of the file and looks like this:

OBFM
$<bh:00><bh:00><bh:00>
<bh:f4><bh:01><bh:f4><bh:01><bh:f4><bh:01>
<bh:f4><bh:01><bh:f4><bh:01><bh:f4><bh:01>
<bh:f4><bh:01><bh:f4><bh:01><bh:f4><bh:01>
<bh:a6><bh:ff><bh:a6><bh:ff><bh:a6><bh:ff>
<bh:a6><bh:ff><bh:a6><bh:ff><bh:a6><bh:ff>
<bh:a6><bh:ff><bh:a6><bh:ff><bh:a6><bh:ff>

So, ok, I can now clearly see the three sets of numbers pertaining to the coordinates of the bounding planes.  I will try changing these to the max/min values you suggested. Unfortunately, I am about to head from Shanghai to the UK and won't be able to do this for another three weeks...

Once again, your patience and helpfulness is very much appreciated.
Scy

[schlumpf]

That MFBO should not be three sets of numbers but rather 2 time 3x3 values. The block you pasted does not exactly look like something a hex editor would output. What editor do you use?

Have fun in the UK.

[Alastor]

Open your ADTs in 010 Editor and load ADT template then remove WMOs

... Done

[schlumpf]

Open your ADTs in 010 Editor and load ADT template then remove WMOs

... Done

This will result in the chunk size being wrong and if that is fixed, in MCRF still referencing the WMOs resulting in not exactly defined behavior. Wheey.