A complete .rbxlx Roblox place with generated terrain and native objects. Open it in Studio and run the provided command to render the terrain in Edit mode.

Can I edit the terrain in Studio?

Yes. It is normal Roblox terrain, so you can sculpt, paint, and smooth it after import.

What does the subscription include?

$49 per month includes 400 credits. Every map size costs 20 credits: enough for 20 maps. Credits refill each billing month; unused credits do not roll over. Failed generations are refunded. Cancel anytime.

What if it is not right for me?

Email us for a refund of your most recent payment. No explanation required.

Ten worlds, one hundred edits — Terrainio editor evaluation

A substantially broader prototype; the full campaign is not finished. All ten historical starting briefs now produce saved geometry. Eight journeys reached their tenth edit. In the documented reference chains, 81 of 87 attempted edits were accepted. API credits ran out with 13 edits still unattempted and one quota-rejected request awaiting a retry. Accepted revisions are not a promise of visual or semantic success.

This report evaluates the separate local Map Studio. The public generator still delivers one complete Roblox place per request. Read the earlier three-journey review for the first editing baseline.

What we tested

Ten initial briefs were selected from a private historical request snapshot. We then wrote ten successive edits for each brief and froze all 110 inputs before campaign calls. Repeated historical prompts helped identify real revision patterns; repeated requests and backend failures are not evidence of user satisfaction.

Each journey has its own saved map. Every edit uses the preceding accepted revision. A rejected edit keeps that revision intact; later requests can consequently fail because a feature was never added. Replays preserve the frozen wording. Some reuse an exact accepted prefix or a previously paid model plan, with separate provenance and no duplicate cost charge.

Initial maps compiled: 10 / 10
Frozen edits attempted: 87 / 100
Edits accepted in reference chains: 81 / 87
Exact exports audited: 10
Measured API usage, all phases: $12.20
Accounted incl. unknown reservations: $14.30

This was an iterative engineering campaign across multiple pinned code versions, not a controlled before/after benchmark. The complete record contains 224 requests excluding inherited checkpoints and 256 actual provider calls, including corrections, failures and replays. Five calls retain conservative unresolved reservations. Successful edits across phases took a median 15.2 seconds (range 6.0–55.7); difficult creation attempts took several minutes. The reference chains below are explicitly selected evidence, not a random-sample reliability estimate. A later anime replay regressed to three rejected edits, demonstrating remaining model variability.

Where the prototype started

The earlier Map Studio already had shared preview/export geometry, atomic revisions, undo and reload recovery. New worlds still began with a harbor or player-plot recipe. That limited the range of briefs it could fulfill, while water, paths and references to earlier objects exposed weaknesses over successive edits.

What changed

Fresh creation now compiles a complete spatial plan instead of requiring a harbor or player-plot keyword. Composition guidance comes from the latest scene-quality work.
Continuous paths, explicit deck/stair geometry, filled lakes and carved waterways replace painted substitutes. Native stud geometry supports the classic block style.
Object identity, component edits, query-relevant summaries and compact route context support references across many edits. Exact failures now include nearby targets and measured foundation dimensions.
Water edits preserve elevated living floors and clear submerged vegetation. Grounded building placement and collision checks reject broken geometry before committing.
The preview focuses selected objects, shows elapsed request time, keeps twenty history entries and remains readable over dark scenes. Atomic saves, undo and recovery are retained.
Fresh plans now reject accidentally tall clearings in otherwise low terrain. The wetland initially contained implausible plateaus; its repaired creation retains lowland relief.
Sculpting now derives its bounds from the actual brushes, so disjoint edits are not silently clipped by a redundant box. This allowed the saved desert plan to compile without another paid creation call.
A final offline correction keeps native bed geometry below sea level. Replaying the saved biome plans restores lake/crater floors and preserves the unsafe-edit rejection; complete real-model retesting of that correction is still pending.
An offline follow-up repairs paths buried or left floating by later terrain edits. Native walking pieces and attached studs follow the changed surface while preserving their identities; unsafe slopes and flooding require an explicit route or bridge correction.

The ten journeys

Descriptions below paraphrase the historical starting briefs. The follow-up prompts are our own test scenarios. “Applied” means the API accepted a saved revision; the assessment separately describes visual and semantic quality.

Classic studded wooden-house valley

10 of 10 attempted edits applied; 10 planned. Recognizable studded buildings, targeted roof/light edits and a separate guest cabin. The world is oversized for a small hangout, paths retain coarse studs, and the tiny pond is nearly hidden by its bridge.

Review, 0–4: intent 3 · composition 2 · spatial consistency 2 · preservation 3 · local recovery/export 4. These are editorial judgments, not user ratings or native Studio certification.