Skarn

No one is trying to shut this down. If you can see, this thread stays while, as Amaroth said, it probably should not. Want to know why it does, though? It amazes me to see how some people decided to join the board just to answer this topic

It seems we can't survive a week here without a good drama on the board.

No, I mean some newer map.

That is as far as you know. I have seen so many cases of patch stealing in Russian RP community. Including your works btw. I think that was called Erutia or something like that.

Rangorn, good decision to make this thread. To be honest, I did not expect that to happen. Well, I see there is an issue here with ADT conversion to Legion. If you guys find the exact reason and how it should be fixed, I can help you to make the process faster by making a script for this purpose or anything else.

Classic RP server situation. Also, patch stealing is very common among WoW modding servers, there is nothing surprising in that. Just stop caring about them. Those who steal stuff never make things work well in the end.

@Rangorn I believe everything is much simplier here. Someone wants to brag about his achievements but keep the teased people away from the knowledge. Case 2: You are just offended with all the community not serving you Legion or whatever knowledge you want on a plate. So, you sit there with your precious bits of knowledge that probably were not exactly hard to find and brag trying to make the community feel irritated. If I am wrong and you really do not understand why people stay on 3.3.5a that makes the situation even more sad. The real reasons are simple: a) many of us have started projects back in 2012 or smth when 3.3.5a was fresh. We have tons of work both clientside and serverside bound to core and storyline. b) Alastor's reasons. c) Amaroth's reasons. b) People like you not sharing 3.3.5a knowledge. And honestly, there are actually many people that contribute to your beloved wotlk+ expansions including Barncastle, Luzifix, all WoWDev.wiki guys, many others and even , surprise, me doing work on a new editor. Do you start sensing what is the main problem there? Am I triggered? Hell no. Just have to get myself something to do in the bus.

There was a thread in Ownedcore with all those builds cracked if I recall correctly.

Still wrong mipmaps. Best example is a texture with a lot of alphachannel. For example, tree leaves. After conversion in PS it is visible like in cata+ expansions, after Blipster and other software it looks like crap or more specifically as a swarm of flies in distance.

Without sharing thst found information, do not expect that to change anyhow soon. WoW modding exists only because of people sharing information on wowdev.wiki, ownedcore, modcraft, mcnet and other websites.

Did not read the full thread, only the initial post. So, I am sorry if I am repeating already said things or not answering some questions. 1. There is only one outdated tutorial. It is the one explaining how to use Noggit. The others might lack some files in the devkit or some small issues. There are 100% complete and relevant tutorials besides that, so saying that no tutorial is up to date is simply wrong. 2. If anything is wrong or not present in _my_ tutorials, I am most likely aware of the issue as I am the one who wrote them. I just lack time to do everything at once but I want to get back to it in January - February. 3. Speaking about learning WoW modding. Those people who came to this scene before 2011-2012 had pretty much only one useful tutorial which is Eluo's Worldbuilding Basics. I can say it did not help me much. Besides that, we had a load of crappy tools that mostly worked through CMD. Noggit worked 10 times worse. Custom WMOs and M2s was only something we could dream about, tools for that purpose were either unusable and unfinished or did not exist at all in most cases. How do you think we learned everything? Practice, experiments, reading of WoWDev wiki and reading information provided by some experienced guys like Schlumpf. Now you have got everything to start. The thing is that now with all available information you can start WoW modding but if you don't dig deeper your experience will stop on the first obstacle you get (believe me WoW modding is made of them). So, take your time learning, ask questions, try things or, as much as I would not want to say it, leave.

Never use any other BLP software other than BLP plugin for Photoshop. For now it is the only software than handles BLP file format 100% correct with proper mipmaps support and all kinds of files opening.

It is very posssible that it is caused by texture dimensions issue.

Well, there is no black magic in making new WMOs. I do not recommend you using MirrorMachine as it lacks lots of features. The white stuff btw is collision mesh. It does not appear like that all over all the models. It is usually used for ladders and other places where you need smoother collision or invisible walls. For making a new WMO you basically make a whatever you want scene in Blender and set everything according to the rules of the WMO export. So, materials for every texture (can be down automatically with Material Utils -> Texface to Material), collision, group settings, portals if necessary, maybe some vertex shading. That's basically it.

The path has to be the same size as the old one or shorter but not longer. If it s shorter extra space is filled with 00 bytes (be careful it appears as dot on the right but dot is actually a different value).

The idea is that .MDX is a hardcoded equal extension as .m2. That's literally all. When a client sees a .mdx it loads the same path with .m2. This way of naming comes from the fact that WoW engine is an updated WC3 engine at some point, or it was on its early stages.

It is actually being worked on for Neo too.

If you downloaded boost from Steff's repo, I think it is the wrong version there. Also I'll ask Adspartan for the version.

It is now being worked on as a part of Neo.

Well, as I said, just stop feeding them. They will eventually calm down as soon as they stop getting pleasure from it.

Download the required DLL and place it to the folder?