Are Marvel Rivals Mods Bannable? An Honest Answer

Are Marvel Rivals mods bannable? Nobody outside NetEase can answer that with authority, and anyone promising you a firm yes or no is guessing. Two things are true at the same time: the published rules prohibit modifying the game client, cosmetics included, and the mods that actually get people thrown out of matches are the ones that change what you can see or do. This page keeps both in view instead of picking the comfortable one.

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. Most ship as a trio of .pak, .utoc and .ucas files with a chunk suffix like _9999999_P on the name. That suffix is a load-order number. The engine mounts what it finds and the highest chunk wins, which is the whole mechanism: a mod does not patch the game, it supplies a file the engine loads instead of the original.

Two very different things travel in that same container. Most 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. A much smaller group changes 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 recoloured Iron Man leaves every player looking at the same shapes, timings and tells. A mod that strips the effects the game uses to limit your view during an ability, or that makes something visible the game meant to hide, hands you an outcome your opponent cannot get by playing better. That second category is what any enforcement is looking for, and it is the category this site refuses to help with.

Everything RIVALSFPS.GG ships sits on the first side of that line. Skins, graphic packs, the packs you build yourself, hitsounds and colour grading all change what your own screen shows you and nothing else. That is a statement about what the app does. It is not a statement about what NetEase permits, and the section after this one 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 it does not carry the reassuring phrases that usually sit in this spot on a page like this one. Every one of them is 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 refuse to hide the risk from you. It states what was tested and stops at the edge of the test. It names the one category it knows gets players kicked and offers to take it off your disk. And it keeps every change one click from being undone, 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 the other eleven people in the match see the costume that player equipped. Any number can run at once, one per costume slot, and the Skin Manager tells you when two mods want the same slot and offers to resolve it. Nothing about your install reaches another player's screen.

Graphic packs and the packs you build in the Custom Pack builder download nothing. The app compiles 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, and no file size to wait on. 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.

Colour 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. Tested in game on our own rig, the effect does not trip Marvel Rivals' modification warning, and that test result is the whole of what the app asserts about it: one green line on the tab reading "No in-game warning." Pressing End in game switches the effect off instantly, and turning the feature off renames ReShade's proxy DLL so ReShade never loads into the game at all. The colour correction page has a live preview you can try with nothing installed.

The check that runs before your game starts

The app carries a compiled-in list of mods known to kick players out of the game with a warning message. Every entry on it 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.

A mod that matches gets a red Flagged badge on its row in the Mod Manager. The badge is a button: it opens what the mod is, one line on why it is listed, a support code you can quote to us, and a Remove it action. 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 thing, and it is a different kind of finding: a .pak in your game folder that carries its own game config. That one is not an account risk, and it is named on screen rather than hidden behind a code, because it is your file and you are being asked to authorise deleting it. It matters for a smaller reason. Marvel Rivals shows its in-game modification warning the whole time one is installed, and it can override settings the app applied. Config paks are retired, and what replaced them is its own page.

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 has its own writeup in why your Marvel Rivals mods are 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 tick 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.
• 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. 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 chips. 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 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

Game updates are where most modded installs break, 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.

If a mod stays broken after a patch, 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 the way back one click away. The app is free, Windows only, installs per user in seconds, and works on Steam, Epic Games and Loading Bay. Installing the Signature Bypass is the one step that writes into the game's Binaries\Win64 folder, so Windows raises a permission prompt for it.

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