Compare two visible selections under the same conditions

Start with weapons you can actually select, keep the distance and settings consistent, and change only the weapon between comparisons. You can make a useful comparison even when the interface provides few numbers.

Choose through the current experience’s own options. The official game description advertises free items, but it does not supply a complete weapon catalog or damage table. Record the names and behavior shown in your session instead of importing a ranking from another RIVALS game.

Checked on 2026-09-27. Repeat a comparison after a relevant update rather than treating an old result as permanent.

Establish one baseline first

Select one available weapon and note its exact displayed name. Check which firing and other actions the interface actually offers. Do not infer a reload key, alternate attack or ammo rule from the weapon’s appearance.

Use ordinary permitted play with a clear view of the target. Keep your position and approximate distance as similar as practical. If another player interferes, the view becomes choppy or an unfamiliar panel effect is active, stop the comparison and simplify the conditions.

Make a few deliberate attempts before switching so you get a feel for the first weapon. Compare those attempts rather than ranking weapons by one unusually fast result. If your camera placement changes sharply between attempts, practice aim control first.

Write down observations you can explain

Fill in a short record for each selection as you test. Use the fields below for your own observations rather than treating them as a published stat list.

FieldWhat to record
SelectionExact name shown in the current menu
ConditionsDevice, approximate distance, settings and session time
ActionThe displayed control you used and the kind of attempt
Visible responseHit indication, health change or other readable feedback, if present
HandlingWhether your aim stayed controlled or needed repeated correction
LimitationInterference, unclear feedback or any changed condition

Leave a field unmeasured when the interface does not provide enough information. A partially filled table is more useful than a confident number calculated from a barely readable effect.

If you observe a health change, separate that from an exact damage claim. Another attack or active effect can change health during the same moment. You need a clear comparison before attributing the result to one weapon.

Change one variable and repeat

Switch to a second visible weapon while keeping the other conditions steady. Repeat the same kind of deliberate attempt. Then return to the first selection for another short check.

Returning to the baseline helps you notice changes in the session. If both weapons suddenly feel delayed, the second weapon is not automatically responsible. Review lag troubleshooting before drawing a conclusion.

Compare outcomes that matter to your use. For example, you can prefer a selection that is easier to aim with on your current device, even when an exact damage difference is unclear. Describe that as your handling preference rather than a universal strongest weapon.

Keep appearance separate from performance

A different skin or visible model does not tell you how a weapon behaves in combat. Test the selection and any cosmetic change separately. The skins guide explains how to check appearance without assuming a damage effect.

Likewise, a successful head-level shot is not enough to assign a multiplier. Use headshot comparisons to evaluate placement and feedback while keeping the weapon fixed.

End with a narrow decision: which visible selection feels easier to use for the conditions you tested, and what needs another check. That is a useful result without inventing a tier list.

FAQ

What is the strongest weapon in Rauls Rivals Modded?

Compare the selections currently available under consistent conditions, then choose based on the clear results you can reproduce. Those tests help you choose for your situation, rather than name a universal strongest weapon.

Can I use weapon stats from the original RIVALS?

Do not transfer them automatically. This is a separate experience, and the current selection, controls and behavior need their own check.

Does a weapon skin change damage?

Check it separately from appearance. Keep the weapon fixed while checking a cosmetic change, and use readable session feedback before assigning a performance effect.

What if a comparison is inconsistent?

Check distance, aim placement, other players, available settings and session responsiveness. Repeat under simpler conditions and record the limitation instead of averaging unrelated attempts into a false stat.