Main menus and menu sets
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 18/100
Research direction
The payload names no source files or entry points, only .project-docs/mcp.md and its coverage inventory, plus the pinned Maya reference in #5. Start by reading the existing native menu code and the MCP docs to see which actions already have menus. Done means all five menu sets are present with unimplemented items disabled and a reason shown, the MCP tests pass, and a screenshot is reviewed. This is multi-part design work, so confirm scope with the maintainer first.
Written by the indexing model from the issue text.
Description
Problem
Menus are provisional and incomplete.
Current behavior
Native menus exist for implemented actions only. Maya's five menu sets are Modeling, Rigging, Animation, FX and Rendering: https://help.autodesk.com/cloudhelp/2026/ENU/Maya-Basics/files/GUID-3DB1C040-051F-4C2A-83F8-D806455FCEFF.htm .
Expected behavior
All five menu sets with every item present and visibly unsupported where not implemented.
Acceptance criteria
- Unimplemented controls stay visibly disabled with a reason; no dummy tools or controls.
- MCP coverage in the same change: implemented operations and relevant state exposed with synchronized tool schemas, real Editor protocol tests (scene token, draft, modal, close and busy guards) and updates to
.project-docs/mcp.mdand its coverage inventory. - Native visual check of the real window (screenshot reviewed), not only headless tests.
- Tests cover malformed, empty, boundary and failure cases; failed operations preserve the baseline.
- No parity claim without comparison against the pinned Maya reference (#5); unverified constants are documented as provisional.
- Dominant language
- Rust
- Stars
- 4
- Forks
- 2
- Avg merge
- 2h 44m
- Merged PRs (30d)
- 59
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from cristim/AztecCraft
-
area/ui-parity type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cristim/AztecCraft#140 ·
Maintainers usually reply within 1 day
-
area/ui-parity good first issue type/docs
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cristim/AztecCraft#85 · 1 comment ·
Maintainers usually reply within 1 day
-
good first issue type/docs
Difficulty 1/5 Under an hour Newbie friendliness 75/100
cristim/AztecCraft#79 · 1 comment ·
Maintainers usually reply within 1 day
-
area/selection area/viewport type/feature
Difficulty 5/5 Over a week Newbie friendliness 20/100
cristim/AztecCraft#135 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 22/100
cristim/AztecCraft#128 ·
Maintainers usually reply within 1 day
All issues in cristim/AztecCraft
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
pop-os/cosmic-comp#2956 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:release criticality:p3 documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
registrystack/registry-stack#2085 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
libp2p/rust-libp2p#6694 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
EmbarkStudios/cargo-deny#910 ·