On this page 9 sections
Ask five Marvel Rivals players what a macro is and you will get five different answers. One means a mouse button that spams jump. One means a Razer profile that fires a combo. One means a full script that watches Luna Snow’s cooldowns and heals the tank the moment he drops low. They are not the same thing, and they do not carry the same ban risk.
This post sorts them out. What each type actually does, what NetEase’s rules say in plain terms, which uses are common and how risky each one is, and how the Elocarry scripting works if you want the real thing rather than a blind key spammer.
The three things people mean by “macro” in Marvel Rivals
The word gets used for three very different tools.
A keyboard or mouse macro. This is the simplest one. You record a sequence of key presses with fixed timings and bind it to a button. Press the button and the sequence plays. Most gaming mice and keyboards ship with software that does this, and some store the macro on the device itself. The macro has no idea what is on screen. It just presses keys.
A third-party input tool. Things like a rapid-fire tool, a bunny hop program or an AutoHotkey script that loops jump while you hold a key. Still blind, still fixed timing, but now it runs as a separate process on your PC rather than inside your mouse software. That matters, because a process is something the anti-cheat can see.
A real script. This is the one that reads game state. It knows which hero you are on, what your cooldowns are, if you are stunned, what the enemy is doing and how far away they are. It fires an ability only when a condition is true. That is not a macro in any meaningful sense. It is a cheat, and it lives in the same category as an aimbot or ESP as far as NetEase is concerned.
When someone asks “are macros bannable in Marvel Rivals”, the honest answer depends entirely on which of these three they mean.
What NetEase’s rules say about Marvel Rivals scripts and macros
You do not need to read the terms word for word. The shape of them is simple.
Anything that modifies the game, reads its memory or automates gameplay is prohibited. That covers aimbots, wallhacks, triggerbots and any script that reacts to game state. It also covers input tools that give an unfair advantage, which is deliberately vague and is where macros fall.
A hardware macro that presses a single key on a timer is a grey area. NetEase has not drawn a public line at “one button, one action”. Plenty of people bind a jump repeat to a mouse button and never hear a word about it. Plenty of people also assume that means it is allowed, which is not the same thing as the rule saying so.
Enforcement comes from two places. The first is Neac Protect, NetEase’s own kernel-level anti-cheat on PC. It looks at what is running alongside the game and how the game’s memory is being touched. The second is reports and replays. Every match has a replay, and a reported player gets their footage reviewed. A macro the anti-cheat cannot see is still a macro a reviewer can see if it makes you move like a robot. We cover the whole system, including how ban waves land, in our guide to how the Marvel Rivals anti-cheat and bans work.
Popular macro uses and how risky each one is
Here is the honest picture for the four uses that come up most.
| Macro or script type | What it does | Risk level | Why |
|---|---|---|---|
| Hardware jump macro | Spams jump with a fixed press and release timing while a key is held | Low to medium | Not software, so the anti-cheat sees nothing. Fixed timing looks mechanical in a replay if you overuse it |
| Bunny hop script | Jumps only above a minimum speed, with press duration, release gap and double-tap activation | Low to medium | Same movement as above, but conditional and less uniform. Still visible to a human reviewer |
| Combo or animation cancel macro | Plays a sequence of ability and attack inputs with set delays | Medium | Combos are legitimate, but a macro’d one is identical every time. Reviewers notice the same frame-perfect string on repeat |
| Rapid fire on one-shot-per-click heroes | Turns a held button into repeated clicks | Medium to high | The fire rate cap is server-side, so the gain is small, and a perfectly even click rate is an obvious tell |
| Auto-heal | Tracks the teammate who needs the heal and sends it (healer mode, a menu tab rather than a script) | Medium | Needs a state-reading cheat. Undetected only while the build is. Looks natural if the threshold and delay are sensible |
| Ult cancel script | Fires a chosen ability the moment a listed enemy hero starts an ultimate | Medium to high | Needs a state-reading cheat. Reacting inside human reaction time every single time is the thing replays catch |
| Aim automation of any kind | Moves the crosshair for you | High | Explicitly cheating. Detected as software or spotted as movement. No grey area |
Bunny hop
Marvel Rivals does not give you free speed for chaining jumps the way old Source games did, but staying airborne and keeping momentum makes you harder to hit and helps some heroes reposition. The tool most people use is a hardware macro that spams space. It works. It also produces a jump every exact number of milliseconds, which is the kind of thing a replay reviewer pauses on. A bunny hop with press duration, release gap and double-tap activation exists so the timing varies and the hop only fires when you are actually moving, rather than spamming jump while you stand at a health pack.
Animation cancels and combos
Spider-Man, Black Panther, Magik and Psylocke all have combo strings where cancelling one animation into another is the difference between a kill and a wasted cooldown. A macro can press the string for you. The problem is that it presses the same string, at the same speed, with the same gaps, every single time, and a blind macro cannot tell that your target dashed away halfway through. A script that checks whether the ability is off cooldown and the target is still in range before it fires the next input is both more useful and less robotic.
Rapid fire on semi-automatic heroes
Hela and Winter Soldier fire one shot per click. A rapid fire macro turns a held button into repeated clicks. The gain is smaller than people expect because the game caps fire rate on its side, and the cost is a perfectly even click rate that does not look like a human finger. It gets reported because it is easy to hear in a replay.
Auto-heal
A macro cannot do this at all. It has no idea who is hurt. Healing the right ally needs something that reads the game: which teammate is in the worst state, where they are, whether the heal is off cooldown. This is the use case people ask about most, and it is also the one that depends most on how it is tuned. A support who heals the second anyone dips below half health, every time, with zero delay, is playing better than any human Strategist and someone will notice. On Elocarry this is not a script at all but a menu tab: healer mode with heal aim assist, auto-fire and target priority picks the teammate, holds the track and sends the heal, and it assists rather than replaces you.
What a real script can do that a macro cannot
A macro presses keys. That is the whole feature list. It cannot see, it cannot wait, it cannot decide.
A script that reads game state can:
- Read your own cooldowns. Fire ability 2 only if it is ready, otherwise skip it and keep the combo moving.
- Read your own status tags. Know that you are stunned, slowed or mid-ultimate and hold inputs until the tag clears.
- Read the enemy’s tags. Know that the Iron Man across the map has just started his ultimate, or that the Hulk in front of you is in his charge.
- Fire only when a condition is true. Heal the ally under a threshold. Shield the tank only when he is taking damage. Cancel the ultimate only when it is within range.
- Target a specific hero. React to Jeff’s ultimate and nobody else’s. Prioritise the Strategist for a flick and ignore the Vanguard.
- Chain a Team-Up ability. Team-Ups switch on when specific heroes share a team, and some of them grant an extra ability with its own input. A script can bind that into the same logic as everything else. Our post on how Team-Ups work in Marvel Rivals explains which pairings give what.
None of this is possible with a Razer profile. All of it is possible with per-hero logic that reads the game, which is what the Marvel Rivals scripts on Elocarry’s custom API are.
How the Elocarry scripting actually works
No spin here. This is what the Scripts tab contains and what it does not.
Per-hero scripts on a custom API. Each script targets a hero. The API exposes what the cheat can read (your tags, your cooldowns, enemy tags, distances) and what it can press. It is Elocarry’s own API, not a general purpose injector, and it works only inside the Elocarry build.
Global input bindings. The script does not need to know what key you have jump on. You bind attacks, reload, melee, jump, abilities 1 to 3, ultimate and Team-Up abilities once, globally, and every script uses those bindings. Change your keybinds in game and you change them in one place.
Script manager and script builder. The manager imports a script from your clipboard and lets you save, enable and bind it. The builder is for people who want to assemble conditions and actions themselves without writing the whole thing by hand.
Debug overlays. This is the part that makes writing a condition possible. One overlay shows your own tags and cooldowns as they change. Another shows the enemy’s tags. You can stand in the practice range, watch what tag appears when Iron Man ults or when Luna Snow freezes someone, and use that tag name in your script. Without the overlay you would be guessing.
Barry writes it for you. Barry is the Elocarry AI. You tell it the hero and the behaviour you want in plain English, in the Discord or from your dashboard, and it returns a script ready to paste and run. Then you tweak it, save it and bind it to a key. The support article on getting a Marvel Rivals script from Barry is the step-by-step, and it is short because the process is short.
Scripting is available on Marvel Rivals and DayZ only. It is part of the Marvel Rivals cheat alongside the aimbot, ESP and triggerbot rather than a separate purchase.
Scripts people ask Barry for
These are the requests that come up over and over. No numbers, because your threshold and your timing should be yours.
A Luna Snow that never wastes the freeze. “On Luna Snow, only fire Absolute Zero when an enemy Duelist is tagged inside melee range and it is off cooldown.” Barry writes the condition on the enemy tag, the range check and the cooldown check. You pick the range. For the healing itself, point Barry at healer mode instead: it is a menu tab, not a script.
Cancel a specific enemy ultimate. “On Doctor Strange, fire my shield the moment Iron Man or Hela starts an ultimate within range.” This one already exists as a menu feature, the cancel ult option that fires a chosen ability at a chosen enemy’s ultimate with a cooldown and max distance, but a script lets you add your own logic on top, like only firing if your shield is not already up.
A Spider-Man combo on one key. “Web-swing in, Get Over Here, uppercut, primary, and if the target is still in range, Amazing Combo.” Barry writes the sequence with cooldown checks between each step, so if you get stunned halfway the script stops rather than pressing buttons at nothing.
If you can describe it, Barry can usually build it. If Barry cannot, the script builder and debug overlays give you what you need to build it yourself.
The risk picture: what a replay can see and what it cannot
Two separate systems can get you banned. Keep them separate in your head.
The anti-cheat sees software. Neac Protect looks at processes, drivers and memory access. A macro stored on your mouse is invisible to it. Macro software running on your desktop is not. A script that reads game memory is exactly what it is built to find, which is why the build it runs inside has to stay undetected, and why Elocarry’s detection status is public and sales pause when anything looks off.
The replay sees behaviour. Every match is recorded. When you get reported, a human or a review system watches your footage. It cannot see your mouse firmware. It can see that you jumped every exact interval for ninety seconds, that your Hela clicked at a perfectly even rate, or that you cancelled every single Iron Man ultimate within a fraction of a second of it starting.
That last one is the tell. A script that plays too perfectly is more dangerous than a script that is slightly bad. Real players miss ult cancels. Real Strategists heal the wrong person sometimes. Real Spider-Men whiff combos. If your script never does any of that, the replay is the evidence, and it does not matter what the anti-cheat saw. Our guide to how to spot a cheater in Marvel Rivals lists the exact things reviewers look for, and it is worth reading from the other side of the table.
This is why the delays, thresholds and random variation in a script are not optional extras. They are the difference between a script that gets you through a season and a script that gets your account flagged in a week.
Nothing is guaranteed
Elocarry’s position on this is the same as it is for every game. No cheat is ever guaranteed undetected. An internal build that is clean today is clean today. The status page is live, sales stop when something looks wrong, and none of that changes the fact that NetEase can push an anti-cheat update at any time.
Scripts add a second layer to that. Even on a fully undetected build, a script that behaves like a machine gets you reported by the enemy team’s replays, and cheating bans in Marvel Rivals are account bans. Free public macro tools make it worse: they are detected quickly, they are often bundled with something you did not ask for, and they were never tuned to look like a person.
So: a hardware macro that spams one key is a grey area that mostly goes unnoticed until it does not. A real script that reads the game is a cheat, full stop, and is worth running only inside an undetected build with humanised timing. Know which one you are using, and set it up as if someone is going to watch the replay, because eventually someone will.
Frequently asked questions
Are macros bannable in Marvel Rivals?
They can be. NetEase does not list every macro by name, but its rules cover any third-party tool that automates play or gives an unfair edge. A hardware macro that presses one key on a timer sits in a grey area and is rarely detected on its own. A macro that reads the game or moves your aim is treated as cheating outright.
What is the difference between a macro and a script in Marvel Rivals?
A macro replays fixed inputs with no idea what is happening on screen. A script reads game state such as cooldowns, health and status tags, then decides what to press and when. The macro is blind. The script is not. That difference is what makes scripts far more useful and far more visible to anti-cheat if they are built badly.
Can NetEase detect a mouse macro?
It can see the software side. Razer Synapse, Logitech G Hub and similar apps run as processes on your PC, and the anti-cheat can read what is running. A macro stored on the mouse itself does not show as software, but the input pattern it produces still shows up in a replay if it is inhumanly consistent.
Is bunny hop a macro or a script?
Most bunny hop tools are macros. They spam jump with a fixed press and release timing. A script version can add a minimum speed check and small timing variation so the jumps look like a player and not a metronome. Either way the movement itself is visible to anyone who watches your replay.
What can a Marvel Rivals script actually do?
A proper script can watch your own cooldowns and status tags, watch the enemy's tags, and fire an ability only when a condition is true. That covers things like healing an ally who drops below a set health, cancelling a specific enemy ultimate, or running a hero combo from a single key press.
How do I get a script written for me?
On Elocarry you describe what you want in plain English to Barry, the Elocarry AI, either in the Discord or from your dashboard. Barry returns a script you paste into the script manager, then you tweak it, save it and bind it to a key. No code needed on your side.
Does using a script guarantee I will not be banned?
No. Nothing does. An internal build that is undetected today is not a promise about tomorrow, and a script that plays too perfectly gets reported from the replay regardless of what the anti-cheat sees. Humanised timing and restraint are what keep an account alive over months.
Do scripts and macros work on console?
Scripts do not. Console players cannot run cheats or scripting tools, and Elocarry does not offer anything for PlayStation or Xbox. Hardware macro devices exist for console pads, but they are blind input replayers and nothing more.
Want the edge in Marvel Rivals?
Undetected Marvel Rivals cheats with aimbot, ESP and 24/7 support.