Layer Editor (display and render layers)
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. Start with .project-docs/mcp.md and its coverage inventory, plus the pinned Maya reference in #5, to see which layer state and MCP operations are expected. Done means display layers (visibility, reference, color) and render layers sit below the Channel Box, with disabled controls showing a reason, MCP schemas and protocol tests updated, and a reviewed native screenshot. The Maya doc links are still pending from the parity inventory.
Written by the indexing model from the issue text.
Description
Problem
No layers.
Current behavior
Not implemented.
Expected behavior
Display layers (visibility, reference, color) first, then render layers, below the Channel Box. The per-element Autodesk Maya 2026 doc links are being collected in the UI parity inventory (slice A, in progress); add them here when it lands.
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 51m
- Merged PRs (30d)
- 84
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/viewport effort/s impact/internal priority/p3 severity/low triaged type/chore urgency/eventually
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cristim/AztecCraft#186 ·
Maintainers usually reply within 1 day
-
area/infra effort/s impact/internal priority/p3 severity/low triaged type/chore urgency/eventually
Difficulty 1/5 Under an hour Newbie friendliness 94/100
cristim/AztecCraft#181 · 1 comment ·
Maintainers usually reply within 1 day
-
area/modeling effort/s impact/many priority/p3 severity/low triaged type/bug urgency/this-quarter
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
cristim/AztecCraft#176 ·
Maintainers usually reply within 1 day
-
area/modeling effort/m impact/many priority/p3 severity/low triaged type/bug urgency/this-quarter
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
cristim/AztecCraft#175 ·
Maintainers usually reply within 1 day
-
area/ui-parity effort/s impact/many priority/p3 severity/low triaged type/bug urgency/this-quarter
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
cristim/AztecCraft#172 · 1 comment ·
Maintainers usually reply within 1 day
All issues in cristim/AztecCraft
Similar issues
-
area:desktop priority:p2 type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
fritzprix/libr-agent#2165 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:ecosystem bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Chelis-Lang/chelis#3942 ·
Maintainers usually reply within 1 day