Hello together,
since Gatherbuddy is out i can count myself to a member who use it nearly every day for 12 hours.
But i had a time where i got a lot of WoW Errors 132.
Just a few days ago i found a way how to avoid these annoying errors.
Its so simple .. you just have to run WoW on one core instead of 2 or 4 or whatever.
I dont know why it works but its confirmed by me (Gatherbuddy now runs 9 days without a wow error. Before wow crashed everytime i use an bot which inject)
But after using the task manager these 9 days to choose at which core wow should run i found a better solution which i wanna show you:
1. Go to your WoW root folder and open the "wtf" folder
2. Now open "config.wtf" with the notepad and add this new line:
3. Close and save it.
4. Have fun without crashes.
Little Note: After testing alot i can say this helps increasing the stability of every wow which have something injected.
This is written by: Imperial Blaze, Thelovefool
since Gatherbuddy is out i can count myself to a member who use it nearly every day for 12 hours.
But i had a time where i got a lot of WoW Errors 132.
Just a few days ago i found a way how to avoid these annoying errors.
Its so simple .. you just have to run WoW on one core instead of 2 or 4 or whatever.
I dont know why it works but its confirmed by me (Gatherbuddy now runs 9 days without a wow error. Before wow crashed everytime i use an bot which inject)
But after using the task manager these 9 days to choose at which core wow should run i found a better solution which i wanna show you:
1. Go to your WoW root folder and open the "wtf" folder
2. Now open "config.wtf" with the notepad and add this new line:
Code:
SET processAffinityMask "1"
4. Have fun without crashes.
Little Note: After testing alot i can say this helps increasing the stability of every wow which have something injected.
This is written by: Imperial Blaze, Thelovefool