wungasaurus

I really don't see an issue with just using mine. Just install an up to date compiler.

no, i don't use windows.

Use a compiler that supports c++11.

I am the original author of list_root. If you don't give me the error, I can't help you though.

https://wowdev.wiki/CASC#hashpath

Hashing the string, looking up the hash, like it did in MPQ as well.

https://wowdev.wiki/M2#Attachments

There is a tool for dumping them. Ask in #modcraft.

There should be an attachment point that sets the center for the camera. You could set that higher

Try the m2 header bounding boxes as well as the attachments. I think there was an attachment used for camera height.

If you're referring to the user camera when sitting on those mounts: That's not in the M2 cameras. Those are for portraits etc. It might be depending on the size of the bounding box in the M2 header, but idk.

There is no filedata_id <=> string system, thus you can't edit it. You have to edit https://wowdev.wiki/CASC#Root to add new files to casc. There are no tools for that.

The game determines that the terrain is no longer visible as you are outdoors. Doodads are bound to terrain.

1) MFBO 2) not NoggIt.

Hint: Communities are made up of people. You are a people in a community. You would be the one that could help others.

This makes no sense. Just update. Old files sure won't vanish once you know the filenames..

Blizzard has stopped shipping FileDataComplete. It was a completely normal .db2, so everything needed to open it is documented on the wiki.

FileDataComplete of 7.0.3.21737 is already included in the repository.

I have exactly 0 interest in maintaining that list file, I have never used it myself. With everyone bugging me about stuff being retroporters, which I immensely hate, I don't really have any interest in investing time for it at all, to be honest. I'll happily merge additions others give, but I won't crawl stuff myself.

https://raw.githubusercontent.com/bloerwald/LegionFiles/master/listfile.txt have you tried just clicking on the file? Have you tried _anything_?

Well, great. This helped nobody ever, and still does not say what the problem was. Of course you can "eliminate the problem" by just removing everything you changed. Big surprise.

without the crash log: no. nobody will.

Because there is obviously more in it that that one field?

Afaik those don't take all that into account.

Yes, although it will be a lot of fiddling or will have subtle issues. removing an object: remove from MODF/MDDF, fix all MCRF in MCNK by removing the removed index and decreeing all bigger values by one. Alternative hack: set position to way below ground. replacing an object: if path not present yet, add to MMDX/MWMO, add offset to MMID/MWID, replace id in MODF/MDDF entry. If model is bigger than before: add to MCRF of all spanned MCNK. If MODF, adjust extents size. creating a hole: add bit in MCNK's hole mask.