The risk in cheats is rarely the cheat itself and usually where you used it.
Short answer
They work in single-player only. Anything promising the same online is a scam or a ban waiting to happen.
If a site asks you to sign in to receive a code, it is not a code. A code that worked on an older patch may have been removed rather than changed. If a step reads as obvious, do it anyway — the obvious ones are the ones people skip and then wonder about.
Codes that no longer work
Console entry uses button sequences with tight timing, and mistiming reads as a broken code. A code that softlocks a mission is a known risk in more than one of these games. A method that works but cannot be explained tends to stop working without warning. Console commands and cheat codes are different systems with different consequences.
Anything that requires downloading a program is not a cheat code. A specific answer beats a comprehensive one when you are in the middle of something. A cheat menu built into the game cannot get you banned, whatever the forum says.
What you give up
Single-player cheats are a supported feature; the same behaviour online is a ban. The useful part of any answer is the part that tells you what to do differently. Achievement locking is usually per-save rather than per-account, but not always.
- Make a separate save before enabling anything.
- Ignore any list that asks you to install something first.
- Treat any number without a date attached as approximate.
- Check the code is for your exact platform.
Achievements and save files
Controller-entered codes need rhythm rather than speed. If this seems to describe a different version, it probably does, and that is the thing to check first. Codes are usually case-insensitive but rarely space-insensitive. Glitches get patched and codes tend not to, which makes codes the more durable option.
What follows assumes you are on a current install and have not modified it. Anything that alters save state can corrupt it, which is why a separate save is worth the ten seconds. Case and spacing matter more than the lists suggest.
Console commands versus codes
Nothing here assumes a particular playstyle beyond wanting the thing to work. Anything requiring an external program is a different category with different risks attached. Codes typically do not persist through a reload, which surprises people who use them for convenience.
Consensus and correctness overlap less than the upvote count suggests. Codes entered correctly and rejected usually mean the wrong platform variant. Enabling cheats disables achievements in most games, and the warning is easy to miss.
What each one actually does
There is no hidden trick here that the game is keeping from you. Some effects cannot be undone within a save, and the game does not always warn you first. Some effects stack in ways the developers did not intend and the game does not handle gracefully.
Where people go wrong
- Trusting a video thumbnail that promises a result the video never actually shows.
- Assuming an option exists here because it exists in a similar game.
- Assuming a page is current because it ranks first.
- Believing a figure that has no date attached to it.
RDR2 FAQ
Do I need anything else set up first?
No. Where a step assumes something, it says so at that point rather than up front.
Where should I check if this changes?
The in-game version of the information first, then the official patch notes. Community pages update after both.
Do the effects save?
Rarely. Most reset when you reload, which makes them convenience rather than permanent change.
Why is a code not working?
Either it belongs to an older version, or the entry method differs on your platform. Both are common.
When in doubt, do the cheap check first.