Match the editing control to the change you want
Before removing anything, decide whether you want to change one piece or clear a larger build. Inspect the current editing controls, keep a saved version you recognize, and try the selected tool on a disposable sample before using it on an important section.
Look for the trash-can icon and the separate red X labeled Delete your blocks. Check each control’s behavior on its own. TNT has its own stock and interactions. Try it on a disposable sample before using it for an editing task.
Name the intended scope first
For a faulty corner, identify the piece or join you want to revise. For a fresh layout, decide which current creation you intend to clear. Make that choice before selecting a tool.
Read the current tool prompts or descriptions for the operation you are considering. Check its behavior on a small sample instead of assigning a removal action from an icon alone.
| Visible control or feature | What to check | Appropriate question |
|---|---|---|
| Trash-can icon | Current targeting and removal behavior | Can this handle the individual sample I selected? |
| Delete your blocks | The scope of the broader clearing action | Is this the amount of the current build I intend to remove? |
| TNT | Its description and behavior on a disposable test | Is this a separate experiment rather than ordinary editing? |
| SAVE card | The version shown after saving | Have I stored the creation I want to keep? |
For a small edit, choose a control whose targeting you have tested. Check the broader clearing control’s scope even if it is the easiest button to spot.
Preserve the version you want to keep
Open SAVE, choose the intended usable card, and store the version you want to retain. Inspect the preview or recent-save state afterward.
If you are still learning the load controls, practice with a small disposable build first. Check the saved preview, then practice loading that version. Seeing the card and knowing how to restore it are separate checks. The save guide and load guide cover those tasks separately.
Do not plan an important edit around an assumed undo shortcut. Use the visible current controls and a version you can identify instead.
Test an individual change on a simple sample
Place a small arrangement in a clear area and choose one piece to investigate. Select the intended editing control, inspect what it targets, and use the current interface instructions for the operation.
Compare the arrangement afterward. Check which parts remain and whether the result matches the change you intended. If it does, return to the actual project and inspect the target again before applying the same operation.
After changing a track section, view its neighboring endpoints and test the ride. An edit can solve the original layout problem while leaving another connection to inspect. The track troubleshooting guide helps you locate that next point.
Keep clearing and rebuilding as separate passes
If you intend to start a new layout, first verify the clearing scope and the saved version you are keeping. Then inspect the workspace after the operation before beginning the replacement route.
For a partial redesign, make one understood change and test it before removing more. Keep a screenshot of the section you are revising so that the next comparison stays specific.
Use the TNT guide for acquisition and separate testing questions. Test unfamiliar interactions separately from ordinary editing so you can see what each one changes.
FAQ
Should I use Delete your blocks for one faulty rail?
First check its current clearing scope. Choose a tested control with the scope you need for that individual change.
What should I check about the trash-can icon?
Check targeting and removal behavior on a small disposable sample. Read the current tool instructions before applying it to your main project.
Is TNT interchangeable with ordinary deletion?
Treat it as a separate feature. Read its current description and test it separately rather than assuming the same editing behavior.
What should I do after removing a track section?
Inspect the neighboring endpoints and test the revised route. Compare the first unexpected point before making another change.