The Working Approach
Rhino 3D Scripts helps an agent choose among RhinoPython, RhinoCommon, legacy RhinoScript and command macros. The distinction matters: a toolbar macro can replay commands, while a script can inspect geometry, branch on conditions and process many objects. The source recommends Python for new scripts and retains VBScript guidance for existing files.
Its most useful detail lies in application behavior rather than shape recipes. It explains the difference between object GUIDs and geometry objects, reads tolerance from the active document, groups changes into an undo record and restores viewport redraw after failures. It also documents Rhino 8 Script Editor and older Python-runtime pitfalls, making the target version and launch method essential parts of the brief.
Expected Deliverables
- A Rhino Python, C# or legacy VBScript implementation appropriate to the task
- A command macro or toolbar alias for a simple repeatable sequence
- A geometry-operation script with cancellation, undo and redraw handling
From Brief to Review
- 01Choose the Runtime
Identify Rhino version and launch method. Use a macro only for a fixed command sequence; choose a script when variables, loops or conditions are needed.
- 02Respect the Document
Resolve selected object types, active-document tolerance and geometry identifiers before applying changes. Avoid hardcoded assumptions about units.
- 03Make Batch Changes Recoverable
Group mutations into an undo record, restore redraw in a finally path and allow cancellation during long loops. Inspect the resulting geometry in Rhino.