Marvel Rivals Cheat Changelog

Marvel Rivals Cheat Changelog

Below, you can find all the updates to our Marvel Rivals cheats.

June 12, 2026

The Marvel Rivals Speeder has been updated to version 46.

Support for Cyclops has been added.

Fixed an issue where the ultimate-fully-charged color persisted indefinitely.

June 9, 2026

The Marvel Rivals Speeder has been updated to version 45.

HP bars have been added to the ESP:

  • Line 55) Settings for the HP bar on the ESP. The syntax is as follows:
    [enable]|[x offset]|[color]|[thickness]
    such as
    1|5|65280|2
    to use default settings. "Enable" should be set to 1 to enable HP bars and 0 to disable. "X offset" is how far left (or right) of the entity you want the bar to appear. "Color" is the color in RGB decimal format. "Thickness" is how thick you want the bar to be.

You can now colorize players with full ultimate charge differently. This is done by appending the new color to the end of your line 52 settings. (Example in the guide.)

May 15, 2026

The Marvel Rivals Speeder has been updated to version 44.

Support added for Devil Dinosaur.

May 4, 2026

The Marvel Rivals Speeder has been updated to version 43.

Speeder can now read attack data & status effect data. As such, I've added new console and script commands to make use of it. With these new commands, you can track cooldown timers & check which players have been marked by certain attacks.

The following console commands have been added:

  • -displaystatus — Speeder will display any newly applied status effects for all players in memory in the console.
  • -displayaid — Speeder will display your attack IDs in the console.

The following script commands have been added:

  • "pse[status effect]" — If you are currently afflicted by "status effect," the rest of the keys line will process. The inverse is possible with !pse. To retrieve status effect IDs, use the -displaystatus console command. Example:
    • keys=pse123456|dbg % currently afflicted by status 123456
  • "aid[attack ID]" — If you are currently performing an attack with an ID of "attack ID," the rest of the keys line will process. The inverse is possible with !aid. Attack IDs can be discerned with the -displayaid console command. Among other things, this command can be used to set cooldown timers. Example:
    • keys=aid123456|eq % cooldown123456,0|st % cooldown123456,10000|dbg % set a 10000 millisecond timer for cooldown 123456
      keys2=ct % cooldown123456|dbg % cooldown 123456 ready!|store % cooldown123456,0
  • "tcps[*][distance],[status effect]" — Targets the closest player within "distance" who is afflicted with "status effect." To see status effect IDs, use the -displaystatus console command. I recommend doing this in the training area before an actual match. If you include an asterisk, such as tcps*, the aimbot will target allies instead of enemies. This command will 'not' lock you onto the target by default, so call it in a tight loop if you want lock-on behavior. If there are no valid targets, the rest of the keys line will not process. Example:
    • keys=tcps1000,1001803|dbg % targeted player marked by Black Panther

April 25, 2026

The Marvel Rivals Speeder has been updated to version 42.

Added an additional HP check to function as a death check for the new game mode.

April 17, 2026

The Marvel Rivals Speeder has been updated to version 41.

Added support for Black Cat.

March 5, 2026

The Marvel Rivals Speeder has been updated to version 36.

An issue where the ESP would not display once closed has been fixed.

March 4, 2026

The Marvel Rivals Speeder has been updated to version 35.

A new hero display menu has been added to the ESP. This is a list that allows you to more easily view data related to the players in the match, such as HP, ultimate charge percentage, distance, etc. It is controlled and enabled by lines 52-53 in config.txt.

  • Line 52) Settings for the hero display menu. This is a list of players currently active in the match with data such as HP, ultimate charge percentage, distance, etc. It's basically all the same data you can see on the ESP but listed in a static location rather than next to each player. The syntax is as follows:
    [enable]|[x]|[y]|[enemy color],[ally color]|[font size]
    such as
    1|1000|25|16711680,0|15
    to enable the menu, position it at 1000, 25, set enemy text to red, hide ally text, and set the font size to 15. See line 53 to control the data displayed.
  • Line 53) The text you would like to appear in the hero display menu (see line 52). The following wildcards may be used to display dynamic text: %hp% (player HP), %dist% (player distance), %ult% (ultimate percentage), %hero% (hero name). Any other text will appear as written. Example:
    %hero% (%ult%%) %hp%/100
    This would look like
    Spider-Man (100%) 100/100

February 25, 2026

The Marvel Rivals Speeder has been updated to version 33.

The ESP can now display the current ultimate charge percentage for all players. This is accomplished with the %ult% wildcard on line 44. Example is in the guide.

The following script command has been added:

  • "ult[percent]" — If your current ultimate charge percentage is greater than or equal to "percent," the rest of the keys line will process. The inverse is possible with !ult. "Percent" should be written as a decimal with 0.1 equal to 10%, 0.2 equal to 20%, and so on. Example:
    • keys=ult1.0|dbg % ultimate is ready!

The following setting has been added to config.txt:

  • Line 51) A divisor for the %dist% wildcard for the ESP. For example, if you input 100 on this line, and the ESP was previously displaying an entity's distance as 2000, that distance would be displayed as 20 instead.

February 19, 2026

The Marvel Rivals Speeder has been updated to version 31.

The %dist% wildcard can now be used to display distance on the ESP. Line 44 example:
%hero% (%hp%) [%dist%]

Fixed a bottleneck that could occur when running radar + ESP simultaneously.

Overall performance improvements.

February 17, 2026

The Marvel Rivals Speeder has been updated to version 30.

The "hp[*]" script command has been fixed.

February 13, 2026

The Marvel Rivals Speeder has been updated to version 29.

Added support for Elsa Bloodstone.

February 12, 2026

The Marvel Rivals Speeder has been updated to version 28.

The following setting has been added to config.txt:

  • Line 50) A list of colors for specific heroes for the ESP and radar. You might want to colorize healers a specific color, for example. The syntax is as follows (do not include the brackets):
    [Hero ID]:[Color]|[Hero ID 2]:[Color]|[Hero ID 3]:[Color]|etc.
    such as
    1044:16711680|1036:65280
    to colorize Blade red and Spider-Man green. Hero IDs can be found here.

January 31, 2026

The Marvel Rivals Speeder has been updated to version 27.

By default, the ESP will now display corner boxes instead of bounding boxes. This reduces screen clutter a bit. The length of the lines can be adjusted on line 14 of config.txt.

Mouse smoothing (line 21) can now be randomized, which helps humanize the aimbot by curving the aim trajectory.

  • Line 21) Mouse smoothing. This basically slows down the aimbot so it doesn't aim immediately at the correct location. 0 disables smoothing (not recommended). Anything above 1 will act as a divisor for cursor distance. For example, if the cursor needs to move 100 pixels, a mouse smoothing value of 2 will cause the mouse to travel 50 pixels initially, then 25, then 12, etc. You can also include a smoothing variance, which randomizes the smoothing used for each axis. This has the added benefit of 'curving' the aim trajectory and preventing the aimbot from aiming in a straight line. Append the variance you want to use with the "|" character, such as 5|1 to use a smoothing of 5 and a variance of 1. To obtain the randomized smoothness, Speeder subtracts and adds the variance from/to the smoothness, with a precision of two decimal places. Thus, 5|1 results in a possible smoothing between 4.00 and 6.00. The default smoothing is 5. The default smoothing variance is 1. If this line is blank, Speeder will default to 5|1.

The refresh rate of the aimbot (line 40) can now be randomized.

  • Line 40) Aimbot refresh rate. This is basically the number of milliseconds between each potential mouse movement. You may include two numbers, a minimum refresh rate and a maximum, such as 10|20. The first number is the minimum. In this example, Speeder would wait between 10 and 20 milliseconds between each potential mouse movement. This prevents mouse input from always showing up at the same intervals. The default refresh rate is 10|20.

The following aimbot setting has been added.

  • Line 49) Aimbot jitter. This is the max number of pixels you'd like Speeder to move the mouse along one of the axes when the other axis is equal to 0. Essentially, this prevents the mouse from moving in a straight line. No human can perfectly move the mouse left/right or up/down, so Speeder will randomly add or subtract a random number of pixels based on the number you enter on this line. For example, if you enter 2, whenever Speeder attempts to move the mouse along the x-axis, and the y-axis movement is 0, Speeder will randomly add or subtract up to 2 pixels from the y-axis. The default jitter is 1.

January 19, 2026

The Marvel Rivals Speeder has been updated to version 26.

Per request, you can now specify a 'deadzone' for the aimbot, within which, Speeder will not adjust your aim. This feature already exists for the y-axis (pitch), but it will now work for the x-axis (yaw) as well. The yaw deadzone can be adjusted on line 25 in config.txt:

  • Line 25) X-axis correction for the aimbot. This will move the crosshair left or right relative to the entity. You shouldn't need to adjust this. However, similar to line 24, you can add a degree of randomness by appending a second number with the "|" character, such as 0|10. This second number will tell Speeder not to adjust the aimbot if the crosshair falls between -10 and +10 game distance of the intended target. This allows you to manually aim within a small window, ensuring you still hit your target but are never aiming at the same exact spot.

ESP performance has been slightly improved.

January 16, 2026

The Marvel Rivals Speeder has been updated to version 25.

Added support for Deadpool.

November 14, 2025

The Marvel Rivals Speeder has been updated to version 23.

Added support for Gambit on the ESP.

October 15, 2025

The Marvel Rivals Speeder has been updated to version 22.

Fixed an issue where the aimbot could only be activated once with a controller.

October 13, 2025

The Marvel Rivals Speeder has been updated to version 21.

Controller support has been added for the aimbot. Set the controller button you want to use on line 48 in config.txt:

  • Line 48) The controller button you'd like to activate the aimbot. The possible buttons are A, B, X, Y, L1, L2, R1, R2. This will still aim with the mouse but will allow you to activate the aimbot with controller buttons.

Line 26 can now be controlled via the "at" script command:

  • "at[type]" — Sets the aimbot's aim type to "type," with 0 aiming only at enemies, 1 aiming at everything (allies & enemies), and 2 aiming only at allies. This is equivalent to changing the setting on line 26 in config.txt. Example:
    • keys=at2|dbg % now aiming only at allies

September 3, 2025

The Marvel Rivals Speeder has been updated to version 17.

Fixed a bug with the aimbot that was causing it to occasionally perform awkward movements. You should notice it is now significantly smoother.

Line 26 in config has been changed as follows:

  • Line 26) This line controls what Speeder will aim at with the aimbot. If 0 (default), Speeder will only aim at enemies. If 1, Speeder will aim at everything (allies & enemies). If 2, Speeder will only aim at allies.

The tcp* command for aiming at allies has been improved. It will now function exactly like the aimbot without any weird delays. The new guide text is:

  • "tcp[*]" — Targets enemy players with the same criteria as the aimbot. When the macro key is released, the aimbot will stop. If you include an asterisk, such as tcp*, the aimbot will target allies instead of enemies. This command ignores the line 26 setting and allows you to set different keys for targeting enemies and allies. See the example macros for a usage example.

September 1, 2025

The Marvel Rivals Speeder has been updated to version 16.

I've added an additional delay to the triggerbot to prevent unintended key spam. It can be adjusted on line 38 in config.txt:

  • Line 38) Virtual key code of the firing key for the triggerbot, as well as the release delay and press delay. Presumably, you want the triggerbot to press left click, so you can set this line to 1. The release delay is how many milliseconds Speeder should wait before releasing the firing key when a target is no longer present. This is a safety mechanism to make you appear more legit. The default release delay is 1000. The press delay is how many milliseconds Speeder should wait before pressing the firing key again (should it be released). This prevents unintended key spam, which may trigger the anticheat. The default press delay is 200. The full syntax of the line is as follows:
    [firing key]|[release delay]|[press delay]
    such as
    1|1000|200
    to shoot with left click, release left click after 1000 milliseconds, and press left click no faster than 200 milliseconds (should it be released). These are the default settings.

As noted, it is set to 200 by default.

The following script commands have been added:

  • "cthp*[health]" — Same as "cthp" but checks teammate's health instead of enemy's. You can use this command to automatically judge whether you should heal a teammate or not.
  • "it*" — Same as "it" but checks for teammates instead of enemies (i.e., it checks whether you are targeting a teammate).

August 25, 2025

The Marvel Rivals Speeder has been updated to version 15.

The ESP will now display offscreen entities along the top of the screen (i.e., entities above you), as well as the other three sides.

The "tcp" script command can now be used to target allies for healing/support:

  • "tcp*[distance],[max angle difference]" — The closest ally player within "distance" and no farther than "max angle difference" from the camera's yaw and pitch will be targeted. "Max angle difference" should be a radian value between 0 and 1.57, with 0 being directly in front of you, 0.78 being anywhere in front of you (within 90 degrees of you on either side), and 1.57 being anywhere around you. Example:
    • keys=tcp*1000,0.78|dbg % targeting closest ally in front of me within 1000 distance

The "cnp*" script command can now contain an additional argument for "max angle difference" so you can check specifically for enemies in front of you:

  • "cnp[*][number of players],[distance],[max angle difference]" — If there are "number of players" within "distance" and no farther than "max angle difference" from the camera's current yaw and pitch, the rest of the keys line will process. If an asterisk is included, such as cnp*, only enemy players will be checked. "Max angle difference" should be a radian value between 0 and 1.57, with 0 being directly in front of you, 0.78 being anywhere in front of you (within 90 degrees of you on either side), and 1.57 being anywhere around you. This can be useful for determining whether you want to use melee attacks. Example:
    • keys=cnp*1,300,0.78|dbg % there is at least one enemy player in front of me within 300 distance

July 27, 2025

The Marvel Rivals Speeder has been updated to version 13.

Speeder will unlock from a target once it is no longer visible.

July 27, 2025

The Marvel Rivals Speeder has been updated to version 12.

Speeder can now read/write from/to the game's memory via physical memory addresses. This is undetectable and bypasses any memory protections the game might have. If you are having issues, you can disable this via line 46 in config.txt:

  • Line 46) If 1, Speeder will NOT use physical addresses when reading/writing from/to the game's memory. Using physical addresses is 100% undetectable by the anticheat and should not be disabled unless you are having problems.

Fixed Phoenix not displaying correctly on the ESP.

Mostly fixed visibility check. Some heroes still have issues (e.g., Scarlet Witch).

Speeder can now adjust your aiming FoV depending on your distance to the target. This is done via line 22 in config.txt:

  • Line 22) Max screen distance from the center of the game window for targets to be considered viable for the aimbot. This is often referred to as the aimbot "field of view." If you have the ESP enabled, you will see a circle in the center of the window. This is the aimbot field of view. I suggest starting with 10000 and adjusting as needed. Additional settings are also available. You can set a minimum and maximum field of view, along with a minimum distance and maximum distance, within which Speeder will gradually increase the field of view to account for closer targets. The syntax is as follows:
    [Minimum field of view]|[Maximum field of view]|[Minimum distance]|[Maximum distance]
    For example,
    10000|20000|0|1000
    With these settings, the field of view will increase from 10000 to 20000 the closer the target is. Because I have set minimum distance to 0 and maximum distance to 1000, this adjustment will only occur when the target is between 0 and 1000 distance.

July 17, 2025

The Marvel Rivals Speeder has been updated to version 11.

The ESP can now display all entities in memory, including those behind you. If an entity is offscreen to the right, you will see their name on the right edge of the screen. If an entity is behind you, you will see their name at the bottom of the screen in the center. You can adjust the position of the text via the "total entities" settings in the normal ESP settings:

  • Total number of entities to display, edge offset X, and edge offset Y. The edge offsets are optional and refer to how far from the edge you want the ESP text to display when entities are offscreen. For example, if you set "edge offset X" to 150, if an entity is offscreen to the right, the text for that entity will be displayed at [screen width] - [edge offset X]. The default edge offset is 150 if you do not set it. If you do not want offscreen entities to be displayed at all, set "edge offset X" to 0.

Note the final sentence if you wish to disable the new feature.

July 6, 2025

The Marvel Rivals Speeder has been updated to version 10.

This is a small update to improve the security of the triggerbot. I have increased the default release delay from 200ms to 1000ms and added a setting for it on line 38:

  • Line 38) Virtual key code of the firing key for the triggerbot, as well as the release delay. Presumably, you want the triggerbot to press left click, so you can set this line to 1. The release delay is how many milliseconds Speeder should wait before releasing the firing key when a target is no longer present. The default release delay is 1000. If you want to change this, you can append a new delay with the "|" character, such as
    1|900
    to set the release delay to 900 milliseconds.

July 5, 2025

The Marvel Rivals Speeder has been updated to version 9.

Smoothing has been disabled when using the "cy" and "cp" script commands. This means the crosshair will move exactly to where you specify. You can create your own smoothing by calling the command multiple times with sleep commands, such as
keys=cy0.785|s100|cy0.785|s100|cy0.785|s100|cy0.785|s100
to swing the camera around 180 degrees.

By default, if a target moves outside the aiming FoV circle, Speeder will cease targeting it. This prevents suspicious scenarios where an enemy might zoom past you, and Speeder would continue targeting it. You can disable this security feature if you want on line 45 in config.txt.

You can now set a range of Y-axis offsets for Speeder to use when aiming:

  • Line 24) Y-axis correction for the aimbot. Positive numbers will move the crosshair upward. Negative numbers will move the crosshair downward. Presumably, you want the aimbot to aim at the head, so you will want a positive number here. 75 seems to work well for me. See line 36 to adjust the Y axis when aiming at different heroes. You may also include a second number here to add a degree of randomness to the Y-axis. This second number will create a range of pitches, within which the aimbot will not attempt to reorient the crosshair. For example, if I set the Y-axis correction to 75, and set the second number to 10, Speeder will assume the target is between 75 and 85 along the y-axis. Speeder will calculate the minimum pitch for +75 and then for +85, and if the current pitch falls between those two pitches, the crosshair will not be adjusted. This allows some degree of manual aiming while still significantly increasing your headshot accuracy. The second number can be appended with the "|" character, such as
    75|10

The Y-axis offset range is pretty nice. It looks very legit.

June 4, 2025

The Marvel Rivals Speeder has been updated to version 6.

Line 44 in config.txt can now be used to control the display of ESP text:

  • Line 44) Text you would like displayed on the ESP for each player. %hp% may be used to display the player's current HP percent. %hero% may be used to display the name of the player's hero. Any other text will appear as written. Example:
    • %hero% (%hp%)

Fixed death detection for the ESP. The box should disappear immediately.

Updated address for distinguishing between teammates and enemies. Let me know if this is still a problem. I tested a few games.

May 31, 2025

The Marvel Rivals Speeder has been updated to version 5.

The following script command has been added to allow you to target enemies or teammates based on HP:

  • "thp[*][health],[game distance],[screen distance]" — Targets the lowest HP player whose health is equal to or below "health." "Health" should be a percent with 50 equal to 50%. If an asterisk is not supplied, this command will target enemy players only. If an asterisk is supplied (thp*), this command will target allied players only. "Game distance" is optional, and if supplied, Speeder will only target players closer than that distance to your character. "Screen distance" is optional, and if supplied, Speeder will only target players closer than that distance to the center of the screen. "Screen distance" directly correlates to line 22 in config.txt, so you can use that to visualize the value you should use. Example:
    • [113]
      keys=thp50,1000
      repeat=1
    • Hold down F2 to target the lowest HP enemy player below 50% within 1000 game distance.

The previous "thp" command has been changed to "cthp."

The "cy" and "cp" commands have been fixed and will now work as intended.

The aimbot's target prioritization has been changed from screen distance to distance from your character. All targets within the aimbot's FoV circle (i.e., all viable aimbot targets) will be compared, and the target closest to your character will be chosen. If you prefer the old method, you can change line 43 in config.txt to 1.

May 29, 2025

The Marvel Rivals Speeder has been updated to version 4.

Target switching delay has been added to config.txt:

  • Line 39) How many milliseconds Speeder should wait before switching targets with the aimbot. Default is 500.

You can now more directly control the "refresh rate" of the aimbot:

  • Line 40) How many milliseconds Speeder should wait to update the aimbot positioning. Default is 10.

A flickshot key has been added:

  • Line 41) Virtual key code of the key to activate flickshot. This is essentially a combination of the aimbot & triggerbot. While this key is pressed, Speeder will aim and fire your weapon. The key pressed to fire your weapon is the key assigned to line 38.

The traditional aimbot FoV circle has been added. It can be controlled via line 42:

  • Line 42) These settings affect the aiming FoV circle in the center of the screen. The syntax is as follows:
    [Color]|[Circle thickness]
    such as
    16711680|1
    for a red circle with a thickness of 1.

Line 19 (aimbot keys) has been fixed and works with multiple keys.

The following script commands have been added to allow you to adjust the camera via macros:

  • "cy[yaw]" — Camera's yaw (left/right direction) will be adjusted by "yaw." This should be a radian value between 0 and 6.28 (360 degrees). For example, if you want to swing the camera around by 180 degrees, you would use cy3.14.
  • "cp[pitch]" — Camera's pitch (up/down direction) will be adjusted by "pitch." This should be a radian value between -1.3 (-75 degrees) and 1.3 (75 degrees). For example, if you want the camera to look directly ahead, level with the ground, you would use cp0.

You can now color the ESP text differently depending on whether the entity is targetable or not. See the updated guide text here.

More stuff to come.

May 26, 2025

The Marvel Rivals Speeder has been updated to version 2.

A triggerbot has been added to the Marvel Rivals Speeder, along with relevant settings in config.txt:

  • Line 34) Triggerbot virtual key code (hold). While this key is held, the triggerbot will be active.
  • Line 35) Triggerbot virtual key code (toggle). This key will toggle the triggerbot on/off.
  • Line 37) Y offset for the center of the screen. The reticle is not exactly in the center of the screen, which can mess up the triggerbot's ability to judge height correctly. If you notice the triggerbot activating too far above the target or too far below, adjust this line as needed. I've found -15 works well.
  • Line 38) Virtual key code of the firing key for the triggerbot. When the triggerbot activates, it will press this key. Do not use left click. It does not work well when your character is moving. I am working on fixing this. In the meantime, assign a secondary key to your main attack, and use that key instead. Personally, I have used the "J" key, which has a virtual key code of 74.

I've also fixed the visibility check for the aimbot (and triggerbot).

Note that the triggerbot activates within the ESP's bounding box, so you can use that to adjust it.

The triggerbot requires Speeder version 2+.

May 25, 2025

I've created a new Speeder for the game Marvel Rivals.

It has all the traditional features of FPS cheats: Aimbot, ESP, & radar. There are some unique features as well, such as script commands to trigger abilities based off HP, hero IDs, and things like that. It's also possible to create commands to auto-heal teammates. Feel free to let me know if there are commands you'd like to see added.

Check out videos of the Speeder in action here: https://speedercheats.vip/marvel-rivals-speeder-videos/.

Check out features here: https://speedercheats.vip/marvel-rivals-cheats-hacks-bots/#features.

Scroll to Top