Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
The principle here is you are modifying dryrain's mod so that this silverin guard mod will actually work, which means you are creating your own mod that should not be regularly updated (as doing so will break it.) You want your new dryrain (MINUS those table entries) mod operational, not the original dryrain.
It's my first time doing this so I'm not familiar with editing mods for Warhammer 2.
Yes, step 7 is you saving it with a different name. The point is that any connected mod still on workshop gets updated-refreshed. So all your changes above would get deleted. So yes, definitely save your new mod with a different name.
Then yes, refresh your mods and you will see the pack file (assuming you "Save as" a different name.) You SELECT/CHECK that mod, you DE-SELECT (or delete) the dryrain official mod as it will conflict.
Take a look on the screenshot
https://ibb.co/mJ3Q3YQ