Razer Synapse 3 Macro Settings

Razer Synapse 3, you don’t want a delay before up or down… AHK puts a pause in-between each up/down action… So for Razer, you want the following:

0s - (keybind)
0s - (keybind)
0.1s - (Insert a blank ‘Type Text’ here and set it for that timing)

This will put a 100ms pause in-between like AHK does

IT WILL NOT TYPE ANY TEXT (as long as it is blank)

Also, Razer does seconds, not milliseconds (ms), so you have to divide whatever MS the macro uses by 1000:

ms / 1000 = s

Examples:
100ms / 1000 = 0.1s
70ms / 1000 = 0.07s
50ms / 1000 = 0.05s
10ms / 1000 = 0.01s

The same thing can’t be achieved with this setting?

image

Your setting would cause a delay in the initial start of the macro, which could be bad in certain circumstances.

You want the initial keypress to be immediate without delay, but once started, then subsequent keypresses can have that delay.

Ultimately I created this post to function as AHK does, which is what most people use. It’s up to you on how you want your delay/timing to work.

i have a razer orbweaver Chroma have it should this be the same concept

If I use this with GSE can I get banned or in trouble in any way?

Cuz I love GSE, but keep smashing my #2 key non-stop during combat is starting to hurt my finger!

There is always a risk of being banned for using software to spam keys. Having said that i have used software to spam keys as fast as 0ms in wow since the burning crusade and have never been banned for it. The real grey area is if your using the softer to toggle the key spam on and off. That is bad in the eyes of blizzard. I typically use repeat while key is pressed. Again though i don’t think anyone has been banned for that either.

hi can you pls check this ,is this so ok i bind it on my razer naga trinity mouse

what do i do if i have a razer syanpse 2 mouse?

if i remember right with synapse 2 you can insert delay after the keypress

Apologies for the late response. As long as you have nothing in the text box for the text option, then you are good.

Apologies for the late response. I do not have any devices that use Razer Synapse 2, so I am unsure. However, Razer has been adding older mice to the Razer Synapse 3 software, so which mouse do you have?

:smiling_imp:

This is my Synapse Setup LUL idk why u guys has text thing in it tbh my runs so good that method calls me every day asking me to join

-BladePro

cause the blank text after key down key up adds the delay causing the key press to be instant then delay. The people with tinfoil hats don’t like running there macros fast. They cant seem to grasp the concept that priority based macros run better faster.

2 Likes

Yes - this makes sense. Priority macros MUST run very fast

It’s the delay that actually dictates the ‘speed’ of the macro. In Corsair, you can just prescribe this manually.

This is actually a myth hiding poor macro design. Priority isn’t even priority it’s mathematically weighted probability that something is potentially more likely to occur. Your macro will fire whatever line it is up to as soon as you have a clear GCD. This is irrespective of whether it’s sequential or priority. What matters is how many lines are cycling in your GCD window as to what comes next. The faster the macro MS the more lines that cycle which once you get to 100ms that’s 15 lines per GCD. Even at that speed irrespective of priority or sequential you are essentially playing whack-a-mole with what line shall we use. The faster this is the harder it is for your macro to be predictable and as you add haste the more random and less consistent the outcome … but what would I know about how GSE works anyway.

There is also the 400ms spell queue window, so my understanding is that at GCD less 400ms it can queue up an ability to use, that gives the macro 400ms to find at least one thing that is not on cooldown, the last one before the 400ms is up gets used.

If running a macro at 100ms that would give 4 bites of the cherry to find a spell that can be cast before you are in the realm of not casting anything but still trying to find something that can be cast.

With that in mind, the only reason to run faster than 100ms is if your macro is designed in such a way that it is possible to hit 4 spells that could not be cast in a row (with at least one that could be cast if it got to it).

If I’ve got it wrong please let me know as it will help with macro design.

Spell Queue Window has had no relevance for a VERY VERY long time (read at least the last 12 years).

The macro line is only valid at the point in which it is attempted to be executed. If you are under the GCD and you press your macro - the GCD ability in that command stack is ignored. The macro just moves on and its the next valid line after the GCD Window is complete that is executed.

I thought I’d test out the assumption that SpellQueueWindow has no bearing and did a little experiment.

Logged on as one of my hunters, removed trinkets and all gear with any haste, checked my stats and it showed no haste. Issued the command /dump GetCVar(“SpellQueueWindow”) and it returned 400 (i.e. 400ms). Setup my razer hardware to fire a key 5 times a second (i.e. 200ms) and then created a macro with the following sequence to run on it:

/cast [@target] Concussive Shot
/cast [@target] Arcane Shot
/cast [@target] Arcane Shot
/cast [@target] Arcane Shot
/cast [@target] Arcane Shot
/cast [@target] Arcane Shot
/cast [@target] Barbed Shot
/cast [@target] Cobra Shot
/cast [@target] Multi-Shot
/tar player
/sit

The theory would be if spells are queued you would get Concussive Shot followed by Cobra Shot after 1.5s although the spell would be attempted at 1.4s (the intervening spells skipped due to either GCD effect or being replaced within the Spell Queue Window. If the spells are not queued then Concussive Shot would be followed by Multi-Shot after 1.6s.

The result was Concussive Shot followed by Cobra Shot, so far so good, the spell queue window is working as intended. So then I changed the macro to this:

/cast [@target] Concussive Shot
/cast [@target] Arcane Shot
/cast [@target] Arcane Shot
/cast [@target] Arcane Shot
/cast [@target] Arcane Shot
/cast [@target] Arcane Shot
/cast [@target] Barbed Shot
/cast [@target] Concussive Shot
/cast [@target] Multi-Shot
/tar player
/sit

Now the second concussive shot when attempted at 1.4s in will be on cooldown. So with a 400ms queue window I would be expecting the previous spell Barbed Shot queued at 1.2s which hasn’t been replaced with concussive shot due to concussive shot being on a 14s cooldown.

The result was Concussive Shot followed by Barbed Shot as expected.

I then changed the macro to this:

/cast [@target] Concussive Shot
/cast [@target] Arcane Shot
/cast [@target] Arcane Shot
/cast [@target] Arcane Shot
/cast [@target] Arcane Shot
/cast [@target] Arcane Shot
/cast [@target] Concussive Shot
/cast [@target] Concussive Shot
/cast [@target] Multi-Shot
/tar player
/sit

Now the final Arcane Shot is scheduled to fire at 1.0s so outside the queue window, concussive shot is on cooldown so they fail to queue at 1.2s and 1.4s, so I expect Multi-Shot to fire at 1.6s.

The result was Concussive Shot followed by Multi-Shot.

So in summary, the Spell Queue Window is working as expected.

This means with a macro firing every 100ms it should have 4 chances to find a spell that is not on cooldown to queue up and fire once the GCD of 1.5s is up (or less if you have haste). If your macro cannot find a spell to fire within that window you are then encountering a delay on top of the GCD until it can find one.

Priority macros are more likely to repeat spells that are on cooldown so are more likely to experience an issue without a very fast click rate (depends on how well the macro is written of course). Sequential are less likely but not exempt from the issue, it really depends on how many spells you might encounter in a row that are on cooldown during the 400ms window.

I ran the same test and dont get the results you are getting.

I get Concussive then Barbed shot first time.

I get Concussive then Barbed shot second time.

Then Concussive and then Multi Third. (Lines 7 and 8 were in individual spell cooldown)

/gse debug pointed out that I was in GCD still for lines 2-6. My GCD was 1.35

Thats at 200MS which you said you were using.