updated, see changelog![]()
Anthraxbot & SPQR Creator / Administrator
Im testing and its working very nice, there's some bugs on MySPQR.Internals.ActionBar.CanCast its returning true when it shouldnt for free
cooldown spells, ie kill shot and its definetly not checking if the player is casting.
Good news is that last version improves dps for about 30-50k dps.
One request, can you make MySPQR.Internals.ActionBar.CastSpellById(spellId); return TRUE if the spell was casted?
Thank you
PS: Updated rotations for Hunter and Shaman, https://ramakandra-emporium.googleco...PQR-Rotations/
Last edited by bruj0; 04-13-2014 at 05:30 PM.
A retribution paladin rotation:
https://github.com/nrgd/nrgdret/blob/master/nrgdRET.cs
PHP Code:
//////////////////////////////////////////////////////////////////////////////////////////////////////////////////
// nrgdret rotation //
// v[alpha0.1] //
//////////////////////////////////////////////////////////////////////////////////////////////////////////////////
// Notes: //
// //
// - This is ALPHA! Don't expect to work flawlessly and to achive an amazing dps! I've just released it to get //
// some feedback to help me improve it, please keep that in mind when posting bugs! //
// //
// - Inquisition is tracked by using timers... this is far for perfect and right now the OnStop() method //
// is not being called by SPQR which means that the timer won't stop when you stop the rotation. I would //
// recomend to restart SPQR if you have stopped the rotation. Hopefully an aura remaining time method //
// will be provided in a new version or the OnStop() method will be fixed to allow using timers meanwhile. //
// //
// - You can switch between single/aoe rotations by pressing 'z' key. Once again this is not perfect because //
// we can't hook to keypresses but instead have to use pooling, so you keypress can be missed. I've added //
// a beep for single and 3 beeps for aoe, so you can know the keypress has been detected and which one is //
// the active one. Maybe in a new SPQR version the program allows us to detect keypresses by handling events! //
// //
// - Rotation is based on icy-veins: //
// [http://www.icy-veins.com/retribution-paladin-wow-pve-dps-rotation-cooldowns-abilities] //
//////////////////////////////////////////////////////////////////////////////////////////////////////////////////
// Upcoming:
// - Change rotation when not in melee range, cast only ranged spells.
// - Detect Divine Purpose procs.
// - Detect 4 pieces tier procs.
// - Pause rotation button.
Register an account on the wiki, you will be able to edit all pages of the WIKI using the top right button Editor create a new page using the Mediawiki system following this : http://www.mediawiki.org/wiki/Help:Starting_a_new_page
Also, uploaded the update
Actually, this is not possible to detect the last Spell used, I need to reverse the CombatLog, and this is a piece of shit![]()
Last edited by Nonowmana; 04-13-2014 at 06:21 PM.
Anthraxbot & SPQR Creator / Administrator
the auto interrupt for warlock doesn't work for me, how can i get it work ? thx
Warlock Interrupt : Optical Blast - Spell - World of Warcraft
It's a pet abilitie
I tried to give my point of view some time ago, but I think it wasn't clear enough so I'll try again to express my opinion.
People like manylol only want SPQR to use the interrupt functionalities in PVP, and gain advantage over other players. Although SPQR simulates keypresses, it has a higher reaction time than a player could possibly have, and it's even better if you want to interrupt only a defined list of spells, so anyone using SPQR will interrupt faster than other players, and players getting interrupted several times just when starting casting are going to report those using SPQR, which is going to bring Blizzard's attention to SPQR and it will be game over for SPQR. They will either find a way to detect it and banwave everyone using it [PQR] or they are gonna contact you Nonowmana "suggesting" to stop SPQR development [ProbablyEngine]. This doesn't mean that they won't take action at some point if SPQR stays PVE-only, but using SPQR in PVE doesn't affect other players, using it in PVP does, and they won't allow it for sure.
Interrupting is not really that hard, it's easily done with a single keybind, so my suggestion would be to remove interrupt functionality from SPQR, and leave it as an automated rotation only program.
I loved PQR, and I hope we can enjoy SPQR for a long time!
or just delete the id of your interrupt in the config file from your class