Update projects to a Blender model's current version
r3_blender_updateA re-uploaded Blender model is always its latest version; the user's projects keep the meshes they have until asked. This tool asks and answers that one question: choice update_projects without reportId shows which projects and entity templates use an older version (or an earlier import of the same file) and what changed; with the reportId and the projectIds / entityTemplateIds the user chose, it moves just those to the current version. Which ones move is the user's choice; "not now" means no call. Parts are matched by Blender OBJECT name: each takes its new mesh and placement; when only its shape changed it keeps the project's materials and the edits made to them in R3; when its materials changed in Blender it takes Blender's materials where the import's own material is unchanged, while a material made or changed in R3 is kept unless the user chooses Blender's (replaceMaterials, from the plan's materialChoices), and a material made in R3 is never deleted. Objects new in the model are added under the copy's root Empty, parts the model no longer has are kept (removeGone: true removes them). Published releases never change. The plan only reads; moving projects needs the blender:update right.
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": {
"blenderModelId": "<blenderModelId>",
"choice": "<choice>"
},
"name": "r3_blender_update"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| choice | Yes | Required: update_projects. There is no default. | |
| reportId | No | The report being answered, from the plan (this tool without reportId). Leave it out to plan. | |
| projectIds | No | With a reportId: the projects to update. | |
| removeGone | No | Also remove the parts the current version no longer has (default false: they are kept and listed). Plan with it and answer that report with it. | |
| blenderModelId | Yes | The Blender model, from r3_blender_list. | |
| replaceMaterials | No | With a reportId: material ids from the plan's materialChoices (materials made or changed in R3, kept by default) the user chose to replace with Blender's. Default none: R3's materials are kept. | |
| entityTemplateIds | No | With a reportId: the entity templates to update. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kept | Yes | ||
| live | No | ||
| 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. | |
| choice | Yes | ||
| reportId | No | ||
| freedRows | Yes | ||
| repointed | Yes | ||
| duplicates | No | ||
| environment | Yes | ||
| projectParts | No | ||
| currentFileId | Yes | ||
| versionNumber | No | ||
| blenderModelId | Yes | ||
| materialChoices | No | ||
| behindProjectIds | No |