Iterating on a Resource

The first generation is rarely the last word. myRP.build keeps the conversation going, so refining a resource is the normal path — not a restart.

Refine by continuing the conversation

To change a resource, describe the change in a follow-up — the app keeps the context of what it just built:

Make the carwash cost $100 instead of $50, and only work on
cars (not boats or helicopters).

You don't re-explain the whole feature; you adjust it. Keep iterating until it's right.

Regeneration overwrites — but it's backed up

When you regenerate a resource, myRP.build rewrites that resource's folder. Before it overwrites, it automatically snapshots the previous version, so a regeneration is reversible — you can undo to restore the resource exactly as it was before the last change.

Heads-up: hand-edits and regeneration

Because regeneration rewrites the folder:

• If you hand-edit the generated Lua and then regenerate that resource, your manual edits are replaced. Undo restores the pre-regeneration version, but the cleaner habit is to keep iterating through prompts rather than mixing manual edits with regenerations.
• If you do want to take a resource over manually, treat your last generation as the handoff point and stop regenerating it.

Tip: version your resources/[local]/ folder with git. It gives you a second safety net alongside the app's built-in backup, and a clean history of every resource.

Each send is a generation

Every message that kicks off a build counts as one generation against your plan — including refinements and attempts that error out. So it's worth being specific up front: a precise first prompt usually costs fewer rounds than a vague one you have to correct.

If a regeneration doesn't load, work through Troubleshooting.