The risk in cheats is rarely the cheat itself and usually where you used it.

Short answer

Use the codes built into the game, in single-player only, after making a separate save.

Anything that alters save state can corrupt it, which is why a separate save is worth the ten seconds. A code that softlocks a mission is a known risk in more than one of these games. If a step reads as obvious, do it anyway — the obvious ones are the ones people skip and then wonder about.

Console commands versus codes

Glitches get patched and codes tend not to, which makes codes the more durable option. If a site asks you to sign in to receive a code, it is not a code. What follows assumes you are on a current install and have not modified it. Anything that requires downloading a program is not a cheat code.

Achievement locking is usually per-save rather than per-account, but not always. There is no hidden trick here that the game is keeping from you. Console commands and cheat codes are different systems with different consequences.

Codes that no longer work

Some effects stack in ways the developers did not intend and the game does not handle gracefully. Consensus and correctness overlap less than the upvote count suggests. Codes are usually case-insensitive but rarely space-insensitive.

  • Never enter anything into an online mode.
  • Use built-in console commands over external programs where both exist.
  • Region and platform change more than people expect, so confirm both.
  • Make a separate save before enabling anything.

What each one actually does

Some effects cannot be undone within a save, and the game does not always warn you first. The short version is near the top on purpose; the reasoning is there if you want to know why. 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.

It helps to understand why a step exists, because then you can adapt it when your situation is slightly different. Anything requiring an external program is a different category with different risks attached. Case and spacing matter more than the lists suggest.

Anything promising online effects

The community wisdom on this is roughly half right, and the half that is wrong costs the most time. Console entry uses button sequences with tight timing, and mistiming reads as a broken code. Codes typically do not persist through a reload, which surprises people who use them for convenience.

Patch notes move numbers around constantly; the shape of the answer holds even when a specific value shifts. A code that worked on an older patch may have been removed rather than changed. A cheat menu built into the game cannot get you banned, whatever the forum says.

Achievements and save files

Time spent confirming which version you are on is never wasted. Controller-entered codes need rhythm rather than speed. Single-player cheats are a supported feature; the same behaviour online is a ban.

Where people go wrong

  • Reading a summary of the patch notes instead of the patch notes.
  • Deciding a step is redundant before finding out what it prevents.
  • Taking the highest number in a comparison without checking what it was measured on.
  • Following console instructions on PC, or the reverse, and blaming the method.

Roblox FAQ

Is this still accurate after the latest Roblox update?

The method is; individual numbers may not be. If a value on your screen differs, trust the screen and keep the sequence.

Why is a code not working?

Either it belongs to an older version, or the entry method differs on your platform. Both are common.

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.

What if none of this works for me?

Then something in your setup differs from the assumption — version, region or platform. Check those three before anything else.

That is the whole of it — if something here stops matching Roblox, the game changed, not the method.