Dragon's Dogma 2
0 of 0

File information

Last updated

Original upload

Created by

Imaginalex Ridog8

Uploaded by

Imaginalex

Virus scan

Safe to use

Tags for this mod

About this mod

Berserker Wolf Helmet with Glowing eyes (only if you activate BLOOM in game that is)

Requirements
Permissions and credits
Berserker Wolf Helmet with Glowing eyes (only if you activate BLOOM in game that is) - Beastren ones will be added later.

Thanks to Ridog8 for the help.

 (The Glow only works if you activate BLOOM in the game graphics options, that is)

As allways, just extract the /natives/ folder at the root of Dragon's Dogma 2.

Glow will naturally fade after a while to leave reddish eyes in the openings. To restart the glowing effect, you have to remove then equip the helmet again.



------------------------------------------ REMINDER :

A WARNING ABOUT HOW FLUFFYMOD MANAGER WORK AND ITS BEHAVIOUR WITH /NATIVES FOLDER ! 
(and why i don't use it for mesh mod files because it's not very clean by default settings)

BY DEFAULT   FLUFFY MOD MANAGER WILL NOT REMOVE OLDER MESH MOD FILES INSTALLED PREVIOUSLY - (Especially mesh/textures/materials mod files by default)l OF THE SAME ARMOR ID - wich end up with conflicts of mixed files of the same armor parts in their respective folder when you remove / and activate other mods of the same armor IDS. 

-> I realized this only recently because i barely ever use fluffy mod manager, but when i tried several of my mods in a row, i realized that it has the options to remove / uninstall files only if you force them into the advanced menu, and even THEN if you close up the game, if you close fluffy mod manager, it will not remove the files when CLOSED abruptly neither.

By default fluffy mod manager would randomly try (or not to) overwrite files, but most of the time, it will do a half job if it has no administrator rights when launched too. Most of the times, if you don't have a clean / hygienic behavior with the mod manager, you end up with a mess anyway from a domino effect of lazy / leaving things by default behaviour. (and mesh mods are still experimental as of now, especially full armors)

BEST PRACTICE IS TO REMOVE OLDER FILES OF THE SAME ARMOR ID MANUALLY BEFORE INSTALLING A NEW MESH MOD FILE OF THE SAME ID.


It works best if you usually just extract the files manually into :

Dragon's Dogma2 root folder.

The /natives folder from the compressed archive should be extracted to find itself in the folder, this way :

Dragon's Dogma2/natives/

WARNING for FLUFFY MOD MANAGER USERS :

The mod usually DONT uninstall itself PREVIOUS mod files in natives, leaving all the FORMER armor parts in it, it would ONLY remove former armor parts if you go into ADVANCED options to force UNINSTALL files when you deactivate the button, at most times without knowing this, it will KEEP former files and make conflicts as it will try to overwrite (or not even try) previous files and make a mix of old and new files if it doesn't find the same names.

And even when activating the options to uninstall files by switching on and off the mod in the mod list, You will also end up with weird behaviour with files if :

-fluffy mod manager is not launched in administrator mode.
-Even if launched in administrator mode : You didn't remember that the specific hard disk where you downloaded / installed the game needs admin rights to modify files !!!

Manual clean up of previous files is necessary if you see that /natives/.... to equipment folder to helm / pants / tops parts with 015 ids still contain files after deactivating the mod in fluffy mod manager.

People usually don't keep in mind that if they install mods through fluffy mod manager, it keeps their older files in the natives inside dragon's dogma 2 Steam / root folder even after they shut down the game , especially that the option to remove files is linked to you actually FORCE opt IN the removal of files when you uninstall a mod through the panel ( by switching it on and off), it does not uninstall them only if you activate the option to uninstall files or sometimes have to run it in ADMINISTRATOR mode.

It is best practice to avoid conflicts or shenanigans between files of a same mod to REMOVE the previous files manually from natives/  .. equipment /  ... tops (for armors) / pants (for leggings) /  helm (for helmet) under the 015  folder

Leggings are :  /pants/015/
Helmets are :   /helm/015/
Chestpiece :     /tops/015/

So if you previously used some of this armor's mod previous versions it will not allways copy paste over the natives folder if the files have identical names, be extra aware of that when you upload a new mod that changes the meshes of any 015 id armor part.