Macro with mouse / keyboard (Razer naga / G15 ?).

[Lyndis]

Hi, i wanted an official answer for the following question :

There is no queue system for spells like actually official server, so if you want to launch a spell just after an other, or just when the cooldown is up, you must spam your bind like a tard (latency etc), even with addons like "snowfall".

So i wanted to know if using mouse / keyboard macro system who can spam repetively an action like a razer naga or G15+ was allowed, of course, with moderate " spam " (something like every 10-20 ms for an action, and during a sort timer like 1-2 sec max).

Seems not too many informations send to the server, since you can just press all the binds of your keyboard at the same time without dc or lag etc, but i don't want to be banned if the server could recognize this " regular spam " as a bot action or whatever.

[OGTUCKER117]

would also like a word on this as my keybord has 18 macro keys and i use a razer nage

[Vod]

Or git gud, and learn timing for spells.

[g0dl1k3]

Or git gud, and learn timing for spells.

I used macro keys on retail so I assume you can here
dont hate just because you have a $5 keyboard lmao

[Lyndis]

Ty for the tips vod, but it's not a macro to spam all the time the bind, but only to repetly press in a short time to launch the spell in the 10-20 ms after cd is up, without changing keyboard (and maybe fingers) every month.

[riq and snog]

I dont think vanilla pve rotations are hard but if u feel the need to scratch out those 30dps due to human error go for it:-) id be bored but whatever.

[Lyndis]

When you have 1 or 2 spells with 6 sec cd, loose 100 or 150 ms each time make a huge difference at the end of the fight.

That's called optimization, maybe not totaly requiered in vanilla, but maybe some peoples want to do the things the best they can :p (without loosing their fingers ^^)

[Scamp]

Actually, it's totally possible to create sequential spell casts with standard macros (Obviously, no more than 1 spell per 1 keypress.) In vanilla you can call CastSpellByName if the parent caller is an input event.

This basically means you can create a macro like /script DoRotation(); then create an addon containing the function DoRotation, that increments a variable and calls whatever spell should be at that point using CastSpellByName.

I've actually made a little addon for this myself but I haven't posted it. (I can if anyone wants though.) This is basically how it works:

Code: Select all

   -- Basic caster druid rotation. Casts moonfire if moonfire debuff is expired, otherwise it spams wrath, but switches to healing if health is less than 50%
   [_Rotation_BasicDruid] = {
      ['Healing Touch'] = {
         ['priority'] = 0.96,
         ['shouldRun'] = function()
            return _PlayerHealthFloat < 0.5
         end
      },
      ['Rejuvenation'] = {
         ['priority'] = 1,
         ['shouldRun'] = function() return _PlayerHealthFloat < 0.5 and _TimeSinceLast > 12 and not _Casting; end
      },
      ['Wrath'] = {
         ['priority'] = 0.1,
         ['shouldRun'] = function() return true; end
      },
      ['Moonfire'] = {
         ['priority'] = 0.9,
         ['shouldRun'] = function() return _TimeSinceLast > 9 and not _Casting and not _FirstCast; end -- debuf duration
      }
   }




        -- shifts out of bear form, heals, until health is more than 60% then shifts back
   [_Rotation_DruidBearHealShift] = {
      ['Bear Form'] = {
         ['priority'] = 0.1,
         ['hasGCD'] = false,
         ['shouldRun'] = function()
            return _PlayerShapeshiftForm == 1 or _vars['finishedHealing'];
         end,
         ['didRun'] = function()
            _vars['finishedHealing'] = false;
         end
      },
      ['Healing Touch'] = {
         ['priority'] = 0.2,
         ['shouldRun'] = function()
            return _PlayerShapeshiftForm == 0 and not _vars['finishedHealing'];
         end,
         ['finished'] = function()
            _vars['finishedHealing'] = _PlayerHealthFloat > 0.6;
         end
      }
   }


Cast sequences are definitely allowed, that's a big part of why macros exist in the first place. It's multiple actions with 1 input that's not, as far as I can tell from the TOS. (And that's blizzard's policy aswell)

Not intending to hijack the thread lol, just sayin'

[macgarthur]

When these types of keyboards started coming out players on retail started getting banned. Blizzard considered this botting because of the extent you could macro these peripherals which sometimes could be played without hardly ever looking at the screen.

With the way Nostalrius bans people for botting I wouldn't risk it.

[g0dl1k3]

When these types of keyboards started coming out players on retail started getting banned. Blizzard considered this botting because of the extent you could macro these peripherals which sometimes could be played without hardly ever looking at the screen.

With the way Nostalrius bans people for botting I wouldn't risk it.

i used these in retail
i dont see why you couldnt here