Closed laytya closed 1 year ago
Looking at the example config (https://github.com/namreeb/wowreeb/blob/master/example_config.xml#L34) it seems like there's an issue with the way wowreeb loads DLLs: It requires an exported method to call in the DLL. VanillaFixes doesn't work this way, instead relying on DLL_PROCESS_ATTACH
and DLL_PROCESS_DETACH
to modify game code.
I could make a workaround in VanillaFixes by adding an empty placeholder function for wowreeb to call but there's another issue, it only supports loading one DLL per instance. This means VanillaFixes and nampower wouldn't work together if you use wowreeb.
I opened an issue here: https://github.com/namreeb/wowreeb/issues/20. I won't be home until next week but if the issue isn't resolved by then I'll fix it myself and open a pull request for wowreeb.
I m personally dont use nampower, so u can make fix for VanillaFixes to test it work
OK, I haven't tested this but it should work: https://github.com/hannesmann/vanillafixes/blob/wowreeb-workaround/bin/VfPatcher.dll?raw=true
Load with <DLL Path="VfPatcher.dll" Method="Load" />
.
Its starts now. Thanx
Issue has been fixed in wowreeb 3.5.
Could not make it work. example?