VoiceOver (Classic)

VoiceOver (Classic)

923k Downloads

Issues with an Addon and wow-voiceover

Zergei opened this issue ยท 6 comments

commented

so to keep it simple and clear:

i use this addon call "ClassicAPI"

it allows to use Classic addons who are backported by the same creator of ClassicAPI to be used in 3.3.5. but when i tried to use wow-voiceover your addon itself didnt work so i reported this issue to "ClassicAPI" creator and gave me a "patch" solution (link below)

https://gitlab.com/Tsoukie/classicapi/-/issues/2

the solution consisted in replacing a file inside wow-voieceover. the fix worked your addon works but gave me this message when i created a new character in wow

WoWScrnShot_112823_032641

i check inside addons for the folders the addon gives in the image and the mentioned folders doesnt exist, I ignore that message but now everytime i speak with goblins the games crashes buts with specific goblins

image

commented

I'm wondering if there is an issue with the 3.3.5 port we made or if it is currently too difficult for people to find.

nah men people use your voice over anywere i have seen a lot of people using it. people are hoping TBC and WOTLK content gets released soon

commented

I'm wondering if there is an issue with the 3.3.5 port we made or if it is currently too difficult for people to find.

nah men people use your voice over anywere i have seen a lot of people using it. people are hoping TBC and WOTLK content gets released soon

Thanks for the response. It seems like this may just be a case of user error then.

I'm posting updates for tbc and wrath progress in the discord if you would like to follow. I'm almost ready for a big community push.

commented

Is there something I'm missing that doesn't allow you to use the official 3.3.5 port? https://github.com/mrthinger/wow-voiceover/releases

commented

well i discover the real culprit of the errors it was this mod https://github.com/s0h2x/wow_patch-interface for some reason it messes up with voice over which is weird but already solved it

commented

I'm wondering if there is an issue with the 3.3.5 port we made or if it is currently too difficult for people to find.

commented

closing this for now as it doesnt seem to be an issue on our end.