If you're trying to use a current 6.2 client, you need to extract CreatureExtraInfo.db2, and convert it to dbc, then put it in the Output folder in the proper dbc sub-folder.  Neo needs to have db2 support going forward, so there's that. I might take a stab at it, despite the fact that I'm not a coder - there's c++-based converters for db2 to csv, and csv to dbc, so it can't be that hard, can it? (sarcasm)

Thanks, I got there in the end; turns out it was in DUNGEONSTEXTURESTESTS and TEMP.

Interesting, all those textures are suffixed with 'WAILING'. The textures from Wailing Caverns are dated 1 November 2003, while the textures in the above paths are dated 13 June 2003. Perhaps that awesome sprawling above-ground bit that we thought for so long was dragon isles-related is nothing more than the original Wailing Caverns entrance!

* I'm basing the file dates off of the 0.5.3 files, not current data *

When I was able to compile it without issues, the version I believe was at 8.2x.

Quote from: "Hobbilis"

I'd like to point out that relaxok is doing a great job with his MMOSDK project and i certainly hope it becomes a new Noggit. Because from what i see/read noggit is functional but lacks a lot of stuff.

I have been to the thread and seen/read everything I could think of to find that actually. Wanted to test it so bad I actually spent about 2-3 hours scouring the internet for a download of it lol.

But from what I understand that isn't just a Wow builder but an entire MMO builder (correct me if I am wrong) and I am not to sure he would release that to the public as freeware.

I hope he does lol, but, we will see =D

MMOSDK is an entirely new engine, with relaxok's own coding from start to finish. It converts the WoW data to his file formats, which are still somewhat evolving between releases of the beta/alpha tools. I don't believe he's interested in offering any sort of export tools from his engine back down to WoW's engine, as his engine is capable of much more since it's a hobby and not a corporate-funded project. Ideally, his engine will become the best platform to build an MMO off of in the future.

At this point, he has verified that most of WoD's files are supported properly within his conversion tools - which is an amazing feat by one person (granted, the Wowdev wiki is a wealth of information, and he does contribute back to it as he figures things out).

Perhaps if he decides to write a modding API in the future, the ability to export the contents of a world you design in his engine would be able to be ported back to another engine, but at the current time, that's not the point of the MMOSDK project.

oops, you're right. Guess the Blizz Lawyers got to him or the moderators... Most likely the mods deleted the posts due to a C&D or something of that nature.

edit: actually, it's more likely due to the fact that the user deleted his account. I guess reddit deletes all traces of an account when the user is deleted/closed.

Thanks for answering my questions. They were mostly a bunch of random thoughts I had, floating in my mind. The only reason why I brought up saving the map data as individual chunks outside of the ADT is because of work I did 10 years ago helping to decode the Halo map format - in the end, we found that the map files were actually more or less databases of 'tags', very much like the chunked structure that ADT's have. When it came to editing the maps, we started with by-hand offset hacks, which worked ok initially, but eventually if we wanted to do more extensive edits, we needed to extract each 'tag' from the map files. The end result was a database of usable chunks of data that we could swap between different maps.

Things got a bit better, though, when Gearbox decided to release editing tools for the PC version, which allowed people to use a neutered version of the original Halo editing toolset. Gorilla was the main editing environment - it basically acted as a tag manager, and metadata editor. I suspect that WoWEdit is very much the same, except that it allows terrain editing within itself, whereas Bungie/Gearbox's tools required an external 3d editor to create and texture the terrain. I got about 30% into creating a map in 3dsmax, before my hard drive failed and I gave up on the project. Ah, those were the days... no backups to speak of :/

At least with Noggit, we have a fully functional editor that, when given proper new maps, seems to work correctly without the overhead of a database or tags. All the work you and everyone else here has put into the tool, including research and reverse engineering of the various file formats is beyond what was done with Halo. Well beyond any other game reversal projects that I've ever seen.

I modified Offsetfix to not do any fixing of the M2 or doodad info for WoTLK maps. I did this to try and fix the resulting non-noggit-compatible maps that Mjollna's GillijimProject creates. As such, my first experiment was a success, aside from the water disappearing (which I'm sure is due to how the offsetfix app processes liquid data - additional hacking will be needed to determine how to get the water back).

As such, I've got Alpha WoW maps working within Noggit!