Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expand on your Interface-fixed Reznik and your personal preference for addons #10

Open
Therieth opened this issue Nov 15, 2024 · 6 comments

Comments

@Therieth
Copy link

Thanks Marotheit for the guide, id like you to expand on the topic of the Reznik patch but without the interface changes that you mentioned you yourself use, i've tried to tweak the patch slightly so I can use Elvui/Glues/LoginTweaks since I have that preference, alongside certain map addons too but its all too messy inside the file and i keep getting errors here and there. So if you could expand on the topic of "cleaning it up", alongside what patches from the individual ones can work in sync with Reznik's (if you happen to know) that'd be very nice.

@Marotheit
Copy link
Owner

Hey there!

If I understand correctly, you are looking to remove the custom interface changes the Reznik patch provides. To accomplish this, simply open the Reznik patch file using MPQ Editor and remove the entire Interface folder from the patch. This should remove any changes the Reznik patch provides and leave you with the completely standard, default World of Warcraft interface. At this point, you should be able to make any modifications you wish to.

If I am misunderstanding what you are trying to accomplish, please let me know and I will try to help further!

@Therieth
Copy link
Author

Hey there again Marotheit, you were not misunderstanding, thank you.
Your response got me perplexed since that's the first thing I tried and ran into a lot of issues but im assuming, since I did the exact same thing on Windows now, that it was related to Linux or my own settings on it.
What I was asking more so was for your own personal setup or changes to the MPQ, since due to certain areas such as "GMIsland", "Hyjal" and "OldOutland", giving issues in certain addons like Cartographer, Carbonite, QuestHelper and so on.
I thought that perhaps you'd have fixed some of that and to just know what else you did to it other than deleting the Interface folder itself, and also what other MPQs you may have working alongside Reznik, since many others are already there or improved, for example, I myself have reznik's but another mpq replacing the trees and artifact druid forms.
Just curiosity on your own personal setup, and if you by chance know how to remove those 3 zones and their related dbc files i'd appreciate you writing on it if its not too much trouble, thanks again.

@Marotheit
Copy link
Owner

Hi there! All changes I've listed below were made with the intention of modernizing Wrath of the Lich King as much as possible without making any changes to the game itself. When in doubt, if it modified any aspect of the game besides updating models, textures, particles, or music, it was removed.

There is almost certainly more to remove, as I probably edit my own patch once a month or so as I discover something I missed, but this will catch you up to speed with the changes I have implemented currently.

These are the folders I removed from Reznik's patch:

0100WoWBeta
0110WoWBeta
0120WoWBeta
053WoWAlpha
055WoWAlpha
0603592Beta
0703694Beta
0803734Beta
091WoWBeta
Afterfall
Interface
LeahWMO
Reznik
shaders
Textures\Minimap
Unreleasedwowinstancesversions10
UnreleasedWoWInstancesVersions9
Vesmir
World\ayahneminecraft
World\Maps
World\wmo
WOTLK_HD_PATCH\tutorial_guide
XTEXTURES
Y2k_project
  • Interface removes Reznik's custom interface.
  • Textures\Minimap removes upscaled minimap textures, which I personally did not want to use.
  • World\Maps and World\wmo removes custom changes to some buildings/zones, such as the hot air balloon(?) in Elwynn Forest while using the flight path from Stormwind to Ironforge. I believe these are the files in question that are causing errors when using map AddOns.
  • WOTLK_HD_PATCH\tutorial_guide removes Reznik's guide to editing this patch.
  • XTEXTURES removes custom changes to water/lava/slime, as I use another patch for that.
  • All other folders include textures and models for (what I can only assume are) other private servers.

These are the folders I removed from Reznik's patch:

DBFilesClient\ChatProfanity.dbc
DBFilesClient\ChrRaces.dbc
DBFilesClient\DungeonMap.dbc
DBFilesClient\DungeonMapChunk.dbc
DBFilesClient\LiquidType.dbc
DBFilesClient\LoadingScreens.dbc
DBFilesClient\Map.dbc
DBFilesClient\NamesProfanity.dbc
DBFilesClient\NamesReserved.dbc
DBFilesClient\SoundAmbience.dbc
DBFilesClient\TalentTab.dbc
DBFilesClient\UnitBlood.dbc
DBFilesClient\UnitBloodLevels.dbc
DBFilesClient\WorldMapArea.dbc
DBFilesClient\WorldMapTransforms.dbc
Environments\Ocean\OceanSkin.blp
World\Goober\g_fishingbobber.blp
World\Goober\g_fishingbobber.m2
World\Goober\g_fishingbobber00.skin
World\Goober\g_fishingbobber_4893611.blp
World\Goober\g_fishingbobber_4893613.blp
World\Goober\g_fishingbobber_4893616.blp
World\Goober\g_fishingbobber_4893619.blp
World\Goober\g_fishingbobber_4893623.blp
World\Goober\g_fishingbobber_4893625.blp
  • Files removed from the DBFilesClient folder would modify the game logic for some assets, such as which loading screens to display for each zone, ambient sounds for each zone, etc. The untouched files inside this folder leave the updated models, particle effects, music, etc. intact.
  • OceanSkin.blp removes a texture change made to ocean water, as I use another patch for that.
  • World\Goober\g_fishingbobber* removes the custom model for the fishing bobber, as Reznik decided to make the bobber twice as large, presumably to make it easier to click, which I personally did not want to use.

The patches I implement on my own installation:

patch-4.MPQ - Reznik's patch with the changes listed above.
patch-7.MPQ - LoginTweaks
patch-L.MPQ - vvladoon's Shadowlands Menu
patch-M.MPQ - Trimitor's Dungeon Maps
patch-Q.MPQ - vvladoon's Loading Screens
patch-W.MPQ - Project Epoch's Water Patch

@Therieth
Copy link
Author

Thank you Marotheit,

With that amount of details you provided, I was able to remove most of the stuff I didn't want and then learn to take it further, now everything just works and I've made a backup for whenever I stop playing and/or comeback in the future so I can plug and play within a few minutes, appreciate it a lot.

@Sithishade
Copy link

Sithishade commented Dec 21, 2024

@Marotheit I'm also curious about your preferred usage of Reznik's patch--according to its NexusMods page, it also includes a modified executable. Should we use his .exe, use his and patch it as you've described, or just manually patch our own executables using the methods you've listed?

Quick edit: assuming we need to do manual patching, I assume it's best to apply the WoWPatcher LAA fix first, and then to apply RCEPatcher afterward?

Leaving this on this issue rather than creating a new one as its relevant to the linked question in the guide itself.

@Marotheit
Copy link
Owner

Should we use his .exe, use his and patch it as you've described, or just manually patch our own executables using the methods you've listed?

I would recommend patching your own unmodified executable for two reasons:

  1. Safety: When you patch the executable yourself, you know where the patches are coming from. RCEPatcher is open source and could be crawled and compiled directly if one desires to do so. WoWPatcher, although not open source, offers more options while maintaining the ability to allow for interface edits, which is the reason Reznik includes an executable at all.
  2. Extensibility: With WoWPatcher, you also gain the ability to apply Large Address Aware, allow castbars to be shown on default nameplates, disable the creation of the Cache folder (which can sometimes cause problems while playing the game), and allow for interface edits. These options, when combined with RCEPatcher, is the best version of the executable I could create at the time of writing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants