-
Posts
3 -
Joined
-
Last visited
Content Type
Profiles
Forums
Servers
Downloads
Gallery
Everything posted by Mr. DK
-
There are modified executables that can load files locally. Those work up to 7.2.5. Using these exe you can simply add the files to your folder in the correct stucture. But be aware that you need to calculate a FileID for all „new“ additions to the game or have to overwrite existing files and use their file ID. https://www.ownedcore.com/forums/world-of-warcraft/world-of-warcraft-bots-programs/501200-repost-sig-md5-protection-remover-8.html
-
Reading files and interface protection is 2 diffrent things. About the exe of somone else I cant say much.
-
Yes and that needs a sopcial executable that fixes this not entierly sure if somone did that for mop I did remove it for WoD 6.2.4 This is done whith hex editin the executable.
-
The error you are getting is due to an interface File called charCreation or something where the maximum amount of Races is set to a fixed number. This needs to be fixed in your client.
-
Problem is if I only do it on obj1 I get a streaming error if I try to load into the game. ---> see modcraft http://www.modcraft.io/index.php?topic=13869.0
-
Hey, tried your script today I converted both obj (o and 1) becasue otherwise i got a streaming error. Now when I enter the map I have no ground as you can see on the screenshot. Any idea what might cause this?
-
Hello, I managed to break the XML protection on the last WoD version. This allows in depth editing of the Interface. Edits: 1. Loading Files directly from you game folder (because we currently can't edit CASC) - Original files with this edit can be found on ownedcore 2. Patched to allow you connect to a private server (simply put in the Ip in WTF/Config) - Done with connection patcher from trinity core 3. Removed GlueXML protection from the Exe - Done by me How to Use: Simply place the exe in your game folder and your good to go Additional Info 1. This exe has no CDNS setup. So I recommend only using this on a full downloaded Client. 2. Only use for modding purposes not to play on other servers (They may have own edits) 3. If you encounter a error saying you lack some sort of startup strings. Add this to your WTF/Config.wtf: SET agentUID "wow_deDE" (instead of deDE use the locale of your client like enUS) Download: https://mega.nz/#!Kt0hlD4J!pvzAiU3zgrCOfkgCBxLsUPMtb3IgunuCMtlWG0nCjfw Edits in 010 So in case you want todo it by yourself here are the byte edits: x86: 02 00 00 00 84 5D 14 74 Edit to: 02 00 00 00 84 5D 14 70 29 FF D1 FF 59 84 C0 74 Edit to: 29 FF D1 FF 59 84 C0 75 E8 50 49 CE FF 50 E8 BD 24 C5 FF 83 7E 28 00 0F 95 C0 0F B6 C0 50 Edit to: E8 50 49 CE FF 50 E8 BD 24 C5 FF 6A 00 90 90 90 90 90 90 90 90 90 B1 D1 C2 FF 68 7B 51 05 01 6A 03 Edit to: B1 D1 C2 FF 68 7B 51 05 01 6A 02 BE 7B 51 05 01 56 6A 03 Edit to: BE 7B 51 05 01 56 6A 02 FB 00 8B 5D 08 68 75 51 05 01 6A 01 Edit to: FB 00 8B 5D 08 68 75 51 05 01 6A 00 x64: 02 00 00 00 40 F6 C5 01 0F 84 Edit to: 02 00 00 00 40 F6 C5 01 0F 80 74 3D 4C 8D 05 7E 53 8E Edit to: 75 3D 4C 8D 05 7E 53 8E
-
In Legion they removed DBC/db2 structure that handles file path's and replaced the whole system with a hasing process which makes legion close to impossible to mod at all. https://wowdev.wiki/CASC#Root Here you can see what exactly I mean. In order to make "new" content you need to generate this hashvalue. So good luck with that. If that makes you break all this your welcome but Its most unlikely atm.
-
So the m2s dont have any camera issues or collision issues? And yes give the logic to luzi he will upodate his converter.
-
Yes and nwo tets that witha n m2. Wmos had bounding boxes since ages. m2 have them since WoD
-
Okay basicly I reccomend using 6.2.4 You need a executable that allowes you to laod files from your folder. From that point on you can simpyl modify date nearly the same way you did for 3.3.5. Luzifix has also released a 3.3.5 to WoD converter which lets you port up maps.
-
Its still due to the missing bounding box entries. you probably dont have in the ADT.
-
then you will have a problem anyway if you want to find your own way to Legion modding.
-
Go use luzis code as a base basicly this + all legiosn spesific stuff should work purfectly
-
Ahm why mod legion anyways its unstable as fuck and blizz changes everything all the time. Get a copy of last WoD Build. Luzifix released a adt converter that works with high performance and even clears your adts. So you got even betetr performance in WoD. Everythign that is in legion can be done in WoD and WoD does not change aynmore. It is essential to have a new constant patch. Elesewiese we will probably redo all our tools 20 times before legion is over. And when legion is at its end you would probably end all legion work and work on whatever addon they put out then. So I highly reccomend you havign a look rather on WoD than legion. I have learnd so much in WoD allready but if everyone is workin on a diffrent patch we will never ever achive anything again.
-
Okay I have been working on this for a while. Before they reworked everything within Legion. You problem with m2 not showing happened to me aswell I also know how to fix it but never made it work. Basicly every m2 has a bounding box entry in WoD- ADT which was not there back in 3.3.5. You have to calculate that bounding box and make an entry in the ADT. If that entry is not precise you object will either not appear ( box to small) or have no collision (to big) There was a calculation somewhere in the dev wiki but I never made it to work. It was somwhere in the ADT page. ( https://wowdev.wiki/ADT/v18 ) Hope that helps. A propper ADT converter would be great. Also this should be somewhere in NEO code so maybe have a look there.
-
I dont know where u can find it but i am working on similar things in WoD there is a dbc that tells you how much mana you get per point of intelligence or level what ever its designed to. Your mana is probably working but since Dk's dont have mana in vanilla this value is set to 0. Energy however is always 100 so this could be the reason why its working. This is only a guess from what I know so far but give it a shot. Maybe its still hardcoded in your core dont know what you are using.