Deathgrowl
New Member
- Joined
- Oct 10, 2013
- Messages
- 39
- Reaction score
- 0
Everytime I do "enable VSYNC in your WoW" it throws me out of WoW, any ideas?
Yeah something is really jacked up. And I am not sure where the fault lies. I suspect the Honorbuddy program and not the Fury Unleashed routine.
Things used to just work but now I have to keep re-installing everything to get it working and even then I am not sure what's going on.
There needs to be very clear instructions in a larger font so end users can get support with these issues.
I've had to re-install at least 7 or 8 times to get it working and it's getting the best of me.
Please, no. Some english is just not supportable. I'd rather have him type russian so I can get it properly translated ...English only in this section please!
Please, no. Some english is just not supportable. I'd rather have him type russian so I can get it properly translated ...
English only in this section please!
Noom I notice that thurlling a caste takes place two invocations it Зуботычина and Destructive Scream. How maybe how to touch up that castes did hammer together on one invocation?
Community Alert -
For those that unaware, Blizzard has started to target raiders, i.e. those of us using dps routines with honorbuddy. I personally received a 72 hour ban and all I was doing was raiding, no farming, no leveling routines, nothing.
I would strongly suggest that all of you go and visit the ban section as there seems to be a massive 72 hour suspension currently taking place. 72 hour suspensions seem to fit the same mold, raiders only using routines.
In short, none of you are safe.
He has a valid point about interrupts. Disrupting shout and pummel will more often than not be used simultaneously rather than successively. Is there a solution for this? Maybe some enable/disable features for either of these interrupts? Perhaps a cooldown check and priority?
I'll do some testing for you. Check Skype.
Community Alert -
For those that unaware, Blizzard has started to target raiders, i.e. those of us using dps routines with honorbuddy. I personally received a 72 hour ban and all I was doing was raiding, no farming, no leveling routines, nothing.
I would strongly suggest that all of you go and visit the ban section as there seems to be a massive 72 hour suspension currently taking place. 72 hour suspensions seem to fit the same mold, raiders only using routines.
In short, none of you are safe.
It might be very possible that Blizzard is watching Interrupts. Alxaw made something to prevent a checking method which, in my eyes, should work. It will be added to the new release. It does make the routine less flexible, as each spell which is interruptable has to be defined. Only ToT and SoO are defined at this point. It will also RANDOMIZE the interrupt times.
A randomized interrupt timer sounds a VERY good idea as xxx ms into an interrupt timer or xxx ms from the end of an interruptible
spell can easily be detected imho, is there a way to add a random interrupt (say a random number between 1000ms into the spell
and the end of the spell timer) to be added to the current release asap as a stop-gap until the new system/version is ready.
No. The bot only interrupts when the spell is flagged with CanInterruptCurrentSpellCast. So using a interrupt spell when the spell is NOT interruptable only proves it is not a bot.Personally I interrupt myself reasons to interrupt yourself are, Interrupt Rotations= Bot doesn't care, attempting to interrupt uninterruptable abilities for example Vicious Assault from Paragons fight isn't interruptible but I see some people in my raid group that "tried" I'm sure it was a routine with auto-interrupts for example I know that Weishebers DK routine will attempt to interrupt any cast and will pop amz on any cast if you enable either of those settings. As far as Blizzard knowing/targeting raiders that's a silly statement just because you are a raider doesn't make you not a botter. In fact I am a firm believer that most raiders run bots I have been on servers with some top guilds Blood Legion even has a secondary guild that all their bots/bot accounts are in. Not to mention every botter runs wow in 32 bit just my thoughts haven't been active here lately sorry busy with work/life stuff. Maybe I'll see some of you guys @ Blizzcon next week.
Bot on now my wayward son.
Yes in the next release.Я просто не знаю как еще писать кто говорит что пишите по английски а кто говорит по русски. Вообщем пишу еще раз,проблема со сбиванием каста рутина использует сразу же два заклинания Зуботычина и Разрушительный Крик. Возможно ли как то исправить чтобы сбивание каста было по одному заклинанию а не сразу два?
It's a little bit more difficult then that. The routine/bot is too fast to see the Spell IS interrupted, hence it retry's with another interrupt.He has a valid point about interrupts. Disrupting shout and pummel will more often than not be used simultaneously rather than successively. Is there a solution for this? Maybe some enable/disable features for either of these interrupts? Perhaps a cooldown check and priority?
I'll do some testing for you. Check Skype.
Both are good, Fury and Arms.Все таки Фури получается лучше чем Армс?
Alxaw suspects it's the way how raiders interrupt spells. I'd suggest turning that off for the moment and wait until I've implemented a more smart interrupt system.Community Alert -
For those that unaware, Blizzard has started to target raiders, i.e. those of us using dps routines with honorbuddy. I personally received a 72 hour ban and all I was doing was raiding, no farming, no leveling routines, nothing.
I would strongly suggest that all of you go and visit the ban section as there seems to be a massive 72 hour suspension currently taking place. 72 hour suspensions seem to fit the same mold, raiders only using routines.
In short, none of you are safe.
Nah, just don't use interrupts for a while.A randomized interrupt timer sounds a VERY good idea as xxx ms into an interrupt timer or xxx ms from the end of an interruptible
spell can easily be detected imho, is there a way to add a random interrupt (say a random number between 1000ms into the spell
and the end of the spell timer) to be added to the current release asap as a stop-gap until the new system/version is ready.