Delete components LIVE in the user's open R3 editor (plan, then confirm)
r3_editor_deleteDelete components from the project the user has OPEN in their R3 editor, exactly as the editor's delete dialog asks it — in TWO calls. First call WITHOUT confirm: it returns the plan and changes nothing — the selected components, what only they use (their geometry, material, colliders …), an Entity's members, the modes on offer and a planToken. Then call again with the same componentIds and confirm: {"mode": …, "planToken": …}: "one" deletes only the selection, "with_dependents" also what only it uses, "bundle" (one Entity) the entity with its members. The mode is the user's choice, unless they already said. If the project changes in between, the confirm is refused: plan again. Only when the user asked for it. The confirmed delete is kept at once in the project's live copy (every open R3 tab shows it; no editor is needed); R3 keeps what was deleted in the project's trash. The children of a deleted Empty or Mesh keep their place in the world, as the editor's delete does (their numbers become the scene's; the answer lists them). A project itself is never deleted here. Needs the editor:dispose capability.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"projectId": "<projectId>",
"componentIds": "<componentIds>"
},
"name": "r3_editor_delete"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| confirm | No | Leave out to get the plan; give it to delete what the plan named. | |
| projectId | Yes | The project (r3_project_list). | |
| componentIds | Yes | The ids of the components to delete (r3_editor_inspect / r3_project_load). |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| seq | No | ||
| live | Yes | ||
| mode | Yes | ||
| modes | Yes | ||
| saved | Yes | ||
| answer | Yes | This answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guidance. | |
| editor | Yes | ||
| members | Yes | ||
| disposed | Yes | ||
| selected | Yes | ||
| confirmed | Yes | ||
| planToken | Yes | ||
| projectId | Yes | ||
| dependents | Yes |