Are Marvel Rivals Mods Bannable? What the Rules Say

Are Marvel Rivals mods bannable? NetEase's published rules prohibit modifying the game client, and that covers cosmetic mods such as skins and graphic packs as well as mods that change what you can see or do. Nobody outside NetEase can predict how the game will treat a given mod, so this page makes no promise about your account. What it can set out is what that rule covers, which mods RIVALSFPS.GG flags and why, what other players see, and how to undo every change.

Cosmetic mods and advantage mods

The rule covers both kinds. What separates them is what other players lose, and that is also where the app draws its own line.

Asking whether Marvel Rivals mods are safe is really two questions, one about your account and one about your machine, and both are here: what a mod is in engine terms, where the line sits between changing what is drawn and changing what you can do, what this app will and will not claim, and the check that runs before your game starts. It is not official advice and it is not a promise about your account.

What a mod actually is in Marvel Rivals

Marvel Rivals runs on Unreal Engine 5, and the game ships its content as pak archives. A mod is another archive dropped into MarvelGame\Marvel\Content\Paks\~mods: a single .pak, or a set of .pak, .utoc and .ucas files with one name, with a suffix such as _9999999_P on the end. The _P marks it as a patch pak, which is what lets it replace the game's own files. A mod does not patch the game's code; it supplies a file the engine loads instead of the original.

Two very different things travel in that same container. Some mods replace art the engine was already going to draw: a costume, a map texture, a sound effect. The file is different and the work the game does is the same. Others change what the game shows you, by taking out something it puts on screen on purpose or by exposing something it was keeping from you. Both arrive as a pak in the same folder, from the same sites, described with the same word. That is why "are mods safe" has no single answer.

The line that matters: what is drawn, and what is changed

The useful line is not cosmetic versus non-cosmetic, because cosmetic is a word people stretch to cover whatever they already installed. It is whether the change alters the information available to you. A recolored Iron Man leaves every player looking at the same shapes, timings and tells. A mod that strips the camera shake the game uses during an ability, or that makes something visible the game meant to hide, hands you an outcome your opponent cannot get by playing better. RIVALSFPS.GG does not ship mods in that second group and will not help you find one.

The app's own features, skins, graphic packs, the packs you build yourself, your own hit, kill and announcer sounds, and color grading, change how the game looks on your own screen or sounds in your own headset. That is a statement about what the app does. It is not a statement about what NetEase permits, and the next section is about the difference.

What is not being claimed

NetEase's published rules prohibit modifying the game client. That is the whole category, and a graphic pack sits inside it the same way a skin does. There is no reading of those rules under which any of this is approved, nobody outside the studio can tell you what will be actioned and what will not, and a page that told you otherwise would be selling you something.

So this site makes no promise about your account and carries no reassuring phrases about bans. Every one of them would be a claim about a system we do not run and cannot see, and repeating it would not make it true. What the app does instead is tell you what it knows is risky. Mods the app knows can get accounts temporarily banned carry a Flagged badge with the reason and a support code, and a .pak that carries its own game config has to come off before the app launches the game. It offers to remove both, and it keeps every other change reversible, which is the part of this you control completely.

What the app puts in your game

Skin mods are client side. A skin changes the model and textures your own game loads, so other players still see the default costume. Any number can run at once, one per costume. When two mods replace the same costume, the Skin Manager groups them under a note that only one of them shows up in game, and a Use this one button on each turns the others off. An add-on, such as tattoos or a hair color made for another skin mod, does not count as a clash: it shows on top of the skin it belongs to, and if that skin loads first and covers it, Load first on the add-on fixes the order. The skin add-ons guide covers that part. Nothing about your install reaches another player's screen.

Graphic packs, including the ones you make with the Custom Pack button, download nothing. The app builds them on your PC out of the game files already on your disk, so there is no archive from a stranger in that chain at all. A build takes a little time, and while it runs the Launch button reads "Building Graphic Packs". One pack is active at a time, and deactivating puts the game's own textures back with nothing left behind. You can import a pack from elsewhere if you want to, and that one is a stranger's file like any other. The graphic pack guide goes through what each one changes.

Color Correction runs through ReShade, which is crosire's work, free and open source. The app never bundles or hosts it. It links the versioned installer at reshade.me, finds the downloaded file in your Downloads folder by itself, and runs crosire's own setup already aimed at the game. Pressing End in game switches the effect off mid-match, and turning the feature off renames ReShade's proxy DLL so ReShade never loads into the game at all. The Color Correction page has a live preview you can try with nothing installed.

Skins, graphic packs and sound mods load into the game as mod paks, so each needs the Signature Bypass. The app itself contains no code that reads or writes another program's memory. The Signature Bypass it installs is a plugin the game loads at startup so it will accept mod paks, and what the Signature Bypass is lists the three files it puts in Binaries\Win64. For the main things the app changes on your PC and in the game folder, see what RIVALSFPS.GG changes.

The check that runs before your game starts

The app carries a compiled-in list of mods it knows can get accounts temporarily banned, and its warning about them is titled "These mods can get your account temporarily banned". Every entry on the list today does the same thing: it removes the camera shake the game uses to obscure your view during abilities and impacts, which is a straight aim advantage over everyone playing the game as it ships. The app does not provide those mods and will not help you find one.

Detection is deliberately doubled up. A mod matches on the trio basename, which is how these actually ship, or on the SHA-256 of its .pak behind an exact file-size gate, so renaming a file does not walk it past the check. The list is compiled into the binary rather than read from disk or fetched from the network, so it cannot be edited away on a machine, and a new app build is the only thing that changes it. That is one of the reasons the app checks for its own updates at launch, every thirty minutes, and when you focus the window.

Mods the app knows can get accounts temporarily banned carry a Flagged badge with the reason and a support code. On the mod's row in the Mod Manager the badge is a button: it opens what the mod is, one line on why it is listed, the support code you can quote to us, and a Remove it button. The same scan runs when you press Launch, so a flagged mod is caught before the game starts rather than after a match goes wrong. That launch warning lists your own file names and the code rather than naming the mod from the list, because publishing the list would advertise the exact thing it exists to steer people off.

The same scan reports one other kind of file. If a .pak in your mods folder carries its own game config, the app shows it with a Config badge and the reason "Contains its own game config", and asks you to remove it before it launches the game (Remove config pak and launch). The app's own warning says Marvel Rivals shows its in-game modification warning while such a pak is installed, and that it can override the settings RIVALSFPS.GG applied. The app is stricter here than with a flagged mod: the warning when the app opens has no option to keep it, and the launch gate has no Launch anyway while one is installed. A config pak is named on screen rather than hidden behind a code, because it is your file and you are being asked to authorize deleting it. RIVALSFPS.GG retired config paks in version 3.4.2 with the note "Using configs may result in bans." Installing config paks was removed completely in 4.0.0, and Marvel Rivals configs covers what replaced them.

The risks that are real regardless of policy

Two risks survive whatever the policy turns out to be: where the file came from, and whether it is quietly doing nothing.

Provenance is the first. A mod is a file from a stranger, and an archive page can claim anything. The app reduces that rather than pretending it away. It never runs mod content: an imported .zip, .7z or .rar is extracted to a temp folder and copied in as files, and the conflict scan reads the pak index or the .utoc directory only, without decompressing any payload to work out what a mod contains. What no tool can do is vouch for what a stranger put inside a texture, so download from sources you can stand behind.

The second is a mod that quietly does nothing because another mod overrode it. Two enabled mods that contain the same game asset fight over it, the engine loads one and ignores the rest, and the app names both the mods and the assets they share without resolving it for you. That is a conflict rather than a safety problem, and it is covered with the other causes in Marvel Rivals mods not working.

Keeping your install reversible

Reversibility is the part you control completely. The rule the app holds to is that nothing leaves your disk without you saying so, and that managing a mod it did not install means showing it and letting you act on it, not taking ownership of it.

• The switch unloads, it does not delete. Turning a mod off renames its files where they sit, appending .off, so X.pak becomes X.pak.off and the engine stops mounting it. Turning it back on strips the marker. Nothing changes folder, so nothing gets lost on the way back.
• Disable All Mods returns the game to stock. In the Mod Manager's Tools menu, it turns every mod, skin and pak off in one press and leaves the Signature Bypass installed. It goes one way on purpose: which mods were on is a set of choices you made one at a time, and no single button can work out which of them you actually wanted back.
• Turning things back on is a checkbox and a button. Select the rows you want in the list and the toolbar swaps to Enable, Disable and Delete for that selection, which is also how you bring mods back in small batches after a patch.
• Disable Bypass is its own action. It removes the signature bypass and nothing else. Your paks and mods stay on disk and simply stop loading, because the game ignores every mod pak without it.
• Deactivate restores the default look. On the Graphic Packs tab, deactivating a pack puts the game's own textures back with nothing left behind.
• Revert All Changes undoes the app's side. On the Diagnostics tab in Settings, it takes out the graphic packs, the signature bypass, the Windows Optimizations and stretched resolution, and leaves your own mods alone.
• Delete is the only one-way door. It asks first, names what it is about to remove, and says outright that turning a mod off unloads it without deleting anything.

One setting is worth checking once. The App tab in Settings has a Mod Manager section with a "Check for mod conflicts" option, on by default, which is what drives the conflict banner and the red Conflict badges. It reads the mod file lists only, so the reason to turn it off is a very large mod folder and a faster list, not safety. The Marvel Rivals mod manager guide covers the rest of the tab, and the features page lists what else the app touches.

What to do before and after a patch

A game update can break a modded install, and the failure looks alarming even when nothing is wrong with your account. A patch can move, rename or recook the assets a mod was built against, so a mod that was fine last week can crash the game on launch or load into nothing.

One kind of patch breakage the app can repair when you ask it to. The September 3, 2026 game update changed how mods have to be packaged, and mods packaged the old way stopped loading. The Mod Manager marks those rows Outdated, and Update my mods in the Tools menu, or Fix on the row, repackages them in place and backs up each .pak it replaces first.

If a mod stays broken after that, the answer is the mod author's update, not a workaround. Nothing about waiting is risky, and a mod sitting switched off costs you only the disk space.

The part that is genuinely your call

A skin swap and an advantage mod are both "a mod" in casual conversation, and treating them as one thing is how people talk themselves into the second while thinking about the first. Keep the two apart, install from sources you can stand behind, and keep a way back. The app is free, Windows only, installs for your Windows user, and works on Steam, Epic Games and Loading Bay. Installing the Signature Bypass writes into the game's Binaries\Win64 folder, which normally sits under Program Files, so Windows usually asks for permission (a UAC prompt) for that step.

What it will not do is tell you that you cannot be banned. That is not ours to promise, and a page that promised it would be worth less than this one.

Download RIVALSFPS.GG

Common questions