Guides
Paralives Cheats Finder: Commands, Money, Needs, Skills
Quick Answer
Open the Paralives cheat console with Ctrl+F1, run HELP after patches, then search this finder for money, needs, skills, jobs, items, FPS, or rescue commands. Use a duplicate save for anything that changes money, age, inventory, skills, work, or debug state.
Cheats Finder
Search Paralives Cheat Commands
Filter commands by use and risk, then copy only the command you mean to test.
Open the console with Ctrl+F1, run HELP, copy one command, mark it tested, then reload before touching a story household.
Duplicate or start a throwaway household. Run HELP first so the current build confirms the console. Add a controlled amount of money, build one room, then save only if routing works.
Do not use a giant money command on a story household just to test one object.HELP -> PRINTMONEY 20000 -> FPS -> SAVEShow needs before changing them. Relieve one need only, then test the object or room that caused the problem. Fix blocked food, bed, bathroom, or seating paths before using broader need commands.
Do not reset all needs if the real problem is a broken build route.HELP -> SHOWNEEDS -> RELIEFNEED Hunger -> RELIEFNEED SleepConfirm the selected Para and current job state. Show skills before changing levels. Use the work-time skip only in a duplicate if schedule testing matters.
Do not clear occupations or force career state before the career panel is backed up.HELP -> PRINTALLOCCUPATIONS -> SHOWSKILLS -> SKIPTO5MINUTESBEFOREWORKZip the save before any command that changes family, inventory, object, or debug state. Confirm the selected character ID when the command targets one Para. Save only after the result is clean and reloadable.
Do not run danger commands on a main household without a rollback point.HELP -> ZIPSAVEFILE -> SHOWCURRENTCHARACTERGUID -> SAVEShow current actions first so you know what is failing. Try UNSTUCK before deleting interactions. After rescue, fix the furniture, door, stairs, or path that caused it.
Do not use broad cancellation to hide a layout problem that will happen again.HELP -> SHOWACTIONS -> UNSTUCK -> CANCELSELECTEDCHARACTERSINTERACTIONSRun the check in a furnished test lot, not only in the menu. Use FPS and BENCHMARKFPS before changing several settings. Try a 30 FPS cap only when frame pacing or battery life needs help.
Do not change resolution, VSync, Proton, and frame cap all in one test.HELP -> FPS -> BENCHMARKFPS -> CAPFPS 30Show the current command list in the console.
Best first command after a patch.Windows: Ctrl+F1. Mac: use the same console shortcut first, then check keyboard function-key behavior if it does not open.Use a lab save before trying this on a main household.Clear text from the command console.
Good housekeeping during longer test sessions.Use a lab save before trying this on a main household.Show alternative shortcuts for commands.
Use when a guide uses a shorter command name.Use a lab save before trying this on a main household.Show the selected Para's unique character ID.
Diagnostic command for character-specific testing.Use a lab save before trying this on a main household.Add a chosen amount of Paradimes.
Good for build-only test saves.Works best with a physical keyboard or a comfortable Steam Input typing route.Use a lab save before trying this on a main household.Set the household balance to a chosen amount.
Use on a duplicate save if you care about the economy loop.Works best with a physical keyboard or a comfortable Steam Input typing route.Use a lab save before trying this on a main household.Pay the selected Para's salary.
Can affect job pacing, so keep it in a lab save first.Use a lab save before trying this on a main household.Add a small money boost.
Lower-impact than large money commands.Use a lab save before trying this on a main household.Add a larger money boost.
Useful for catalog testing.Use a lab save before trying this on a main household.Add a very large money boost.
Better for build labs than story saves.Use a lab save before trying this on a main household.Add a random amount of Paradimes.
Fun for experiments, poor for controlled testing.Use a lab save before trying this on a main household.Clear billing statements from the mailbox.
Check household finances after using it.Use a lab save before trying this on a main household.Advance the clock by 24 hours.
Check work, bills, needs, and save reload after using it.Use a lab save before trying this on a main household.Advance the clock by one hour.
Good for a short timing test in a duplicate household.Use a lab save before trying this on a main household.Set the current time of day.
Use before a routine test, then confirm sleep, work, and school timing.Use a lab save before trying this on a main household.Move time close to the selected Para's next work shift.
Use with the career planner when checking a job route.Use a lab save before trying this on a main household.Open character editing for the selected household.
Save before large appearance changes.Use a lab save before trying this on a main household.Display the selected Para's age in the console.
Check before changing age or life stage.Use a lab save before trying this on a main household.Change a Para age to a specified value.
Use a backup before age-sensitive story saves.Use a lab save before trying this on a main household.Add one personality level to the selected Para.
Use after saving if the Para's story matters.Use a lab save before trying this on a main household.Reset personality level to the starting state.
Better for lab saves than long household stories.Use a lab save before trying this on a main household.Show active status effects for the selected Para.
Good when a Para behaves oddly.Use a lab save before trying this on a main household.Clear status effects from the selected Para.
Can hide the cause of a mood or routine issue.Use a lab save before trying this on a main household.Clear status effects from all Parafolks.
Use only after confirming the problem is not build-related.Use a lab save before trying this on a main household.Add one story card.
Story pacing can change, so use a duplicate first.Use a lab save before trying this on a main household.Make the selected Para pregnant, optionally with a multiple value.
Back up before pregnancy or family-state commands.Use a lab save before trying this on a main household.Trigger birth for the selected pregnant Para.
Do not test this on a household you cannot roll back.Use a lab save before trying this on a main household.Make two selected Parafolks have a baby together.
Requires careful selection and a backup.Use a lab save before trying this on a main household.Show current pregnancy details.
Diagnostic command before changing family state.Use a lab save before trying this on a main household.Move the selected Para to the next life stage.
Can permanently change household pacing.Use a lab save before trying this on a main household.Move the selected Para to the previous life stage.
Use only in a duplicate or throwaway save.Use a lab save before trying this on a main household.Trigger a growth spurt for an infant or teen Para.
Check age state before and after.Use a lab save before trying this on a main household.Revert a growth spurt for an infant or teen Para.
Use when testing age behavior, not a main story.Use a lab save before trying this on a main household.Kill the selected Para.
Never use on a main save unless you intend the result.Use a lab save before trying this on a main household.Revive selected Parafolks when the game state allows it.
Keep a backup; recovery commands can have limits.Use a lab save before trying this on a main household.Add selected NPC Parafolks to the current household.
Household edits can change routines and saves.Use a lab save before trying this on a main household.Create a Para from a model ID or display name.
Use a lab save until you know the expected model names.Use a lab save before trying this on a main household.Split the current household into a new household state.
Back up before any household split command.Use a lab save before trying this on a main household.Remove selected Parafolks from the household.
Use only when you are ready to roll back if needed.Use a lab save before trying this on a main household.Show the selected Para's relationship labels and values.
Good before testing social or romance changes.Use a lab save before trying this on a main household.Display need values for the selected Para.
Good diagnostic command.Set one need to a chosen value.
Need names usually tolerate case, but copy the ID cleanly.Use a lab save before trying this on a main household.Reduce one need by a chosen value, or by one if blank.
Good for stress-testing routines, bad for story saves.Use a lab save before trying this on a main household.Restore one specified need.
Safer than clearing many systems at once.Restore needs for the selected household.
Good for testing build routes without need pressure.Restore needs for every Para in the household.
Use for broad tests, not quiet story cleanup.Use a lab save before trying this on a main household.Change one need by a chosen value.
Use only when a single-need test matters.Use a lab save before trying this on a main household.Offer new wants from current emotions.
Complete or clear current wants first if the list is full.Use a lab save before trying this on a main household.Complete the selected Para's current wants.
Use when testing want rewards or pacing.Use a lab save before trying this on a main household.Add one level to a chosen skill.
Check the skill exists in the current build.Set a skill to a chosen level.
Use on a duplicate if career progress matters.Use a lab save before trying this on a main household.Add a vacation day to the selected Para's job state.
Use only when testing career time off, not a normal work route.Use a lab save before trying this on a main household.Clear all jobs from the selected Para.
Back up first; this can wipe a career plan.Use a lab save before trying this on a main household.Add a strike to the selected Para's occupations.
Use in a job lab save only.Use a lab save before trying this on a main household.Clear occupation strikes.
Check the career panel after using it.Use a lab save before trying this on a main household.Finish the current work day and pay out salary/progress.
Can change job pacing; avoid on untouched story saves.Use a lab save before trying this on a main household.List jobs held by the selected Para.
Good for checking career state.Use a lab save before trying this on a main household.List possible extras for occupation testing.
Diagnostic career command for lab saves.Use a lab save before trying this on a main household.Put out fires across the current loaded state.
Use after a fire test blocks normal play.Use a lab save before trying this on a main household.Put out fire on selected Parafolks.
Rescue command for fire tests.Use a lab save before trying this on a main household.Set a selected item on fire.
Use only in a throwaway lot.Use a lab save before trying this on a main household.Change the state of a selected item.
Back up first; object state changes can be hard to undo.Use a lab save before trying this on a main household.Set selected Parafolks on fire.
Never use on a main household unless you intend the outcome.Use a lab save before trying this on a main household.Delete newspaper issues from the current save state.
Back up before clearing world records.Use a lab save before trying this on a main household.Generate a newspaper issue for testing.
Check mailbox and household routine after using it.Use a lab save before trying this on a main household.Generate mail for testing.
Use in a duplicate household before a normal bill route.Use a lab save before trying this on a main household.Reset mailbox state.
Do not use on a main save unless you are ready to roll back.Use a lab save before trying this on a main household.Toggle town editing behavior when available in the current build.
Use only in a test town and save before trying it.Use a lab save before trying this on a main household.Repair items in the game.
Useful if broken objects block testing.Use a lab save before trying this on a main household.Unspoil items in the game.
Use for kitchen or storage testing.Use a lab save before trying this on a main household.Run a short FPS benchmark.
Good before changing graphics settings.Set a frame cap.
Helpful on laptops and Steam Deck.Useful on laptops and handheld setups after the build reaches a playable lot.Display current FPS.
Pair with furnished-lot tests.Useful on laptops and handheld setups after the build reaches a playable lot.Change or inspect resolution behavior.
Use carefully on handheld displays.Use a lab save before trying this on a main household.Set a specific resolution.
Use carefully on Deck or small displays.Avoid changing display commands on Steam Deck until a throwaway save already loads.Use a lab save before trying this on a main household.Display or set VSync behavior.
Check frame pacing after changing it.Use a lab save before trying this on a main household.Switch the game to fullscreen.
Useful after display testing.Use a lab save before trying this on a main household.Switch the game to windowed mode.
Can help with capture or troubleshooting.Use a lab save before trying this on a main household.Show current shadow render distance.
Helpful for performance checks on larger lots.Start a town performance benchmark storyboard.
Run before changing many graphics settings.Use a lab save before trying this on a main household.Save the current game.
Use after a clean test, not after an unknown bad state.Use a lab save before trying this on a main household.Zip the current save file to the desktop.
Useful before risky commands or Workshop batches.Check the desktop or active user folder after running it.Use a lab save before trying this on a main household.Exit the game immediately.
Avoid unless you are done with a throwaway test.Use a lab save before trying this on a main household.Move the selected Para out of a pathing problem.
Try this before tearing down a build.Use a lab save before trying this on a main household.Move all Parafolks out of pathing problems.
Useful after dense build tests.Use a lab save before trying this on a main household.Clear museum donations and make them available again.
Do not use on a collection save without a backup.Use a lab save before trying this on a main household.Run a command on a visible schedule.
Good for repeated FPS display; stop it when done.Use a lab save before trying this on a main household.Stop a scheduled command.
Use after SCHEDULE tests.Use a lab save before trying this on a main household.Teach the selected Para all skins in a chosen category.
Use only when testing unlock behavior in a duplicate save.Use a lab save before trying this on a main household.Clear selected-character state for a lab test.
High-impact cleanup command; back up first.Use a lab save before trying this on a main household.Cancel interactions for all Parafolks.
Good for unsticking a test, but it can interrupt household routines.Use a lab save before trying this on a main household.Cancel interactions for the household.
Use after checking whether the problem is pathing.Use a lab save before trying this on a main household.Cancel interactions for selected Parafolks.
Safer than broad cancellation, but still use a lab save first.Use a lab save before trying this on a main household.Delete queued interactions for selected Parafolks.
Use only when a duplicate save is already backed up.Use a lab save before trying this on a main household.Exit to the main menu.
Use after saving a clean lab test.Use a lab save before trying this on a main household.Run a small fun command.
Keep fun commands in lab saves until you know their effect.Use a lab save before trying this on a main household.Run a small fun command.
Keep fun commands in lab saves until you know their effect.Use a lab save before trying this on a main household.Run a small fun command.
Keep fun commands in lab saves until you know their effect.Use a lab save before trying this on a main household.Run a small fun command.
Keep fun commands in lab saves until you know their effect.Use a lab save before trying this on a main household.Randomize deformation values.
Use only in Paramaker or a duplicate save you can discard.Use a lab save before trying this on a main household.Run a small fun command.
Keep fun commands in lab saves until you know their effect.Use a lab save before trying this on a main household.No matching command. Try another category, clear the risk filter, or run HELP in the current build.
The Paralives cheats finder above is built for quick command lookup. Use it when you need to add test money, fix needs, show skills, check FPS, rescue a stuck Para, inspect items, or run a build lab without scrolling through a long article.
Open the command console with Ctrl+F1. Type a command, press Enter, and use HELP after patches to see what the current build recognizes. Do not treat any launch-week command list as permanent. Paralives is in Early Access, and console behavior can change faster than normal guide pages.
Main hub: Paralives Tools. Build testing: Build Tools Database. Save safety: Save Location.
Use a duplicate save for commands that change state. Diagnostic commands are safer than commands that rewrite money, age, inventory, careers, or debug objects.
Money-only route: Paralives Money Cheats has a shorter copy table for PRINTMONEY, SETMONEY, PIGGYBANK, MAKEITRAIN, bills, and build-lab cash checks.
Quick Answer
Use cheats in this order:
- Back up or duplicate the household.
- Open the console with Ctrl+F1.
- Run HELP to confirm current commands.
- Search this page by category.
- Copy one command.
- Test it once.
- Save, quit, and reload only if the result is clean.
If you are testing build mode, money commands are useful. If you are protecting a story save, stick to diagnostic commands unless you are comfortable rolling back.
Money Quick Table
| Money need | Command example | Best use |
|---|---|---|
| Add exact test money | PRINTMONEY 20000 | Build lab funding without fully rewriting household funds |
| Set household balance | SETMONEY 20000 | Controlled duplicate-save economy checks |
| Small boost | PIGGYBANK | Low-impact console test |
| Bigger build boost | MAKEITRAIN | Catalog and furnished-room testing |
| Huge cash test | JACKPOT | Throwaway household only |
| Random boost | LOTTERY | Fun test, not controlled routing |
| Bills cleanup | CLEARBILLS | Mailbox and billing tests after a lab command |
If your only question is money, use Paralives Money Cheats first. Use this full finder when you need needs, skills, rescue, items, FPS, UI, or debug commands too.
Safer Command Categories
| Category | Safer use | Save warning |
|---|---|---|
| Basics | HELP and ALIASES show command information | Low risk |
| Performance | FPS, BENCHMARKFPS, CAPFPS | Low risk, but settings can change comfort |
| Needs | SHOWNEEDS is safer than changing all needs | State changes can affect routine testing |
| Skills | SHOWSKILLS is safer than setting levels | Skill edits can change career or story pacing |
| Money | Good for build-only labs | Can ruin the early economy loop |
| Items | SHOWITEMINFOS and PRINTINVENTORY are diagnostic | CLEARINVENTORY is risky |
| Rescue | UNSTUCK and UNSTUCKALL can save a broken route | Still check the build that caused the problem |
| Debug | Useful for testing | Keep away from main saves |
The finder marks some commands as safe, test, or danger. That is not an official guarantee. It is a player habit label. “Safe” means the command is usually lower-risk or diagnostic. “Test” means it changes game state. “Danger” means you should use a throwaway save unless you are ready to recover.
Best Uses For Cheats
Cheats are most useful in Paralives when they answer a practical question:
| Goal | Good command type | Why |
|---|---|---|
| Build a test house | Money command | Lets you test walls, furniture, routing, and Workshop objects without grinding |
| Check a stuck Para | UNSTUCK or UNSTUCKALL | Helps confirm whether the lot layout is the problem |
| Plan a skill route | SHOWSKILLS first | Confirms current skill names before changing levels |
| Tune settings | FPS or BENCHMARKFPS | Tests performance on a real lot instead of the main menu |
| Repair a test world | REPAIRALLITEMS | Useful when broken objects block the next test |
| Find item IDs | SHOWITEMINFOS | Helps item testing without guessing |
The worst use is changing five things at once. If you add money, set needs, change skills, spawn items, and load Workshop content in one session, you will not know which piece caused the issue.
Need IDs And Safer Examples
Need commands are easy to mistype because they use internal need names. Use the chip list in the finder before typing, then test one need at a time:
| Need problem | Safer first command | What to check after |
|---|---|---|
| Para is too hungry to test a kitchen | SHOWNEEDS, then RELIEFNEED Hunger | The Para can cook and eat without route failures |
| Sleep is blocking a build test | RELIEFNEED Sleep | The bed still works after resize, rotation, or room changes |
| Hygiene is breaking a morning route | RELIEFNEED Hygiene | Bathroom objects are usable and not blocked |
| You want a full reset for a lab household | RELIEFALLNEEDS | Needs changed cleanly without hiding a build bug |
| You are about to try risky commands | ZIPSAVEFILE | A zipped save appears before the test continues |
Avoid using a need command to cover up a broken house. If Hunger, Sleep, or Hygiene drops because the Para cannot reach food, bed, or bathroom objects, fix the build first.
Main-Save Rules
Use this checklist before running any command on a household you care about:
- You know where your save backup is.
- You have run HELP in the current build.
- The command category matches the problem.
- You are not mixing cheat changes with new Workshop items.
- You can explain what changed if the save behaves oddly.
If you cannot do those five things, use a throwaway lab household. Paralives gives players a lot of freedom; cheats should help you test that freedom, not quietly damage the save you actually want to play.
Console Habits After Patches
After a patch, do not assume every command still behaves the same. Run a small check:
| Check | Why |
|---|---|
| HELP still opens the list | Confirms the console is responding |
| SHOWSKILLS works on the selected Para | Confirms target selection |
| FPS or BENCHMARKFPS returns expected feedback | Confirms diagnostic output |
| A small money command works in a lab save | Confirms state-changing commands still behave |
| Save and reload after the test | Confirms the result survives safely |
Use a lab save as your command notebook. Keep your story household clean unless you have a specific reason to change it.
Next Pages To Open
FAQ
How do you open cheats in Paralives?
Use Ctrl+F1 to open the command console, then type or paste a command and press Enter.
Do Paralives cheats need to be enabled first?
Start by opening the console and running HELP. If the current build needs a separate enable step, the live command list is the safest place to catch it.
Are Paralives cheat commands case sensitive?
Commands are usually forgiving, but copying the exact command is still the safest habit.
What is the safest Paralives cheat to test first?
HELP, ALIASES, SHOWSKILLS, SHOWNEEDS, FPS, and BENCHMARKFPS are safer diagnostic commands because they mostly show information.
Can cheats break a Paralives save?
Some commands can change money, age, inventory, needs, jobs, or debug state. Use a duplicate household before using them on a main save.