Skarn

LSD-induced dreams

You can use my Blender addon to work with WMOs.

If there are any custom filenames, you will have to rebuild the structure by anazying the files. On old clients it is possible to do 100% for the files that are actually used and referenced by the game DBs, ADTs or models. Also this whole MPQ listfile removal process is not encryption.

It can be converted to WMO. You can use my Blender addon. There is a tutorial for it on this website too.

Hello. As some of you may know, for quite a while I've been working on the first actual editor for M2 / WMO models for WoW. The project began about a year ago as a fork of happyhack's Blender addon for WMOs. Over time by my own efforts and with the help of some people, I was able to create a full featured (despite a couple of things, that yet have to be implemented) WMO editor. Now I am working on the M2 part of the project. Since there are a lot more tools that I want to develop, I am looking for somebody who can help me with development to finish it faster. The project is written in Python 3.5. Requirements: - Python coding experience - Ability to stick to project's architecture - Ability to stick to given code style (I use regular python standard PEP8 with a few minor additions to naming conventions) Project goals: - Full-featured editing of WMO / M2. - Rudimentary editing of ADT. - Support for multiple WoW versions. - Editor for client DBs related to M2 / WMO (AreaTable, NPC stuff, etc). The majority of the boring stuff, such as file parsing is arleady implemented. Import for M2 is implemented, except for particles. Last but not least, donations that the project is going to receive in the future are going to be shared proportionally, even though the work is mostly volunteer. The project's aim is not money income, but the creation of the first proper editing toolkit for WoW files, as well as the Swiss Army Knife tool for machinima artists. If you are interested, feel free to contact me here, on my Discord (Skarn#2018) or elsewhere.

I think you can turn that off in settings.

I am sorry, that's bullshit. Noggit does not use .NET, fortunately. What's exactly the issue?

You should use the new Noggit. I think that issue is fixed there.

This topic is being researched at the moment by some people. I am pretty confident the solution will be available later.

Just extract them and convert to wotlk with Adspartan's tool. Should be as easy as that.

what did you make it with? I don't recall my addon producing crashing models.

There are no ways you can prevent leechers from stealing your content. It has always been happening and probably will always happen. Despite that I work with many awesome people from the WoW RP community, I have to admit that most of these content stealing dramas somehow happen within the WoW RP community. Not saying anything, just a fun fact. If you want to make the life harder for them, protect your patches in the best way possible (even though everything is reversable, but people who steal other people's content cannot really create anything themselves and therefore most likely won't be able to do it). You can also leave a sort of signature inside the files, so the fact that you've made the file can be easily proved, which could down the reputation of these people. I personally do not think anyone should do the things that you suggested to this server. Attack on a server is first of all an attack on the players who spend time and have fun there, and secondly on admins. The players did not steal your content. What can be done instead is gathering evidence that these people steal content, posting it on the boards where they get players from, asking the admins of these boards to stop supporting them, and so on.

That won't give you much. There are no tools utilizing the features of new clients at the moment. There is no point in moving to anything higher than 3.3.5 without it since compared to original content your custom edits will look like shit without texture scaling and other new features.

I'd rather have actual competitors steal my content rather than noobs because that makes your stuff look valuable. And no sane competitor who takes things seriously is going to spoil their reputation by acting this way.

It is just always disappointing for a designer to see your work being stolen and reused in some shitty distasteful environment. If I have a chance to make things harder for such people, I am going to do it, if it does not take insane amount of time. Those patches to .exe/files are not time consuming at all. The more time you spend on creating the concept of the artwork, actually doing it (considering we have rather shitty tools in the community on all fronts for now), the more valueable it becomes to you. Tools are an entirely different thing. The whole purpose why this website exists is to help people mod WoW and tools have exactly the same goal. But using someone else's tools is not the same as using someone else's artwork without permisson.

They usually steal stuff like custom item models which appear on their shitty 255 level servers and your own project looses the feeling of uniqueness since people might have seen the same stuff everywhere else.

There is no tutorial. It kills the point of doing this.

It is worth it. Noobs who often want to steal pathces usually do not know how to reverse this stuff. People who know something are unlikely to steal your content because they do not care or can create something on their own.

It is done by writing your own software that can manipulate those file's bytes. Swapping magics in the exe can be done with 010 editor or similar software. Patching files can also be done through scripts in there. There is no easier solution.

Patch the chunk magics of all DBC files and other small size files and change the string the client is looking for and include all of them in your custom patches to override previous versions. As a result, your WoW.exe won't work without your patch, as well as normal WoW.exe would work with yours. However, it is quite easy for some people to revert this change. In order to make it a bit harder and require some additional software, you might consider changing the names of the tables in WoW.exe, so that your DBC are named in a different way. Anyway there is no ultimate protection. Everything can be reversed back.

The pictures from the game show the effect of MCLV, not MCLY. MCLY effect can be seen, for example, in Icecrown and it looks different. It almost does not change the color of the tileset, but only adds the fake reflection effect.

Yes, I know. And that is exactly what is happening on the first screenshot here. MCLV on the rocks emits red light which makes it looks like the rock tileset is reflecting lava. But essentially it does not matter since MCLV is not supported by WotLK.