Native Extrude control with manipulator, region and all-face extrusion
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start with known-issues.md under "Core authoring limits" and the existing core Extrude API and MCP tool, then read .project-docs/mcp.md and its coverage inventory. The first blocker is the pinned Maya fixture from #5, which must define all-face extrusion before any behavior is implemented. Done means the native control, MCP schemas, Editor protocol tests and a reviewed window screenshot all agree with that reference, and unverified constants are marked provisional.
由索引模型根据 Issue 内容生成。
描述
Problem
Extrusion exists as a core API and MCP tool only; the native control is disabled.
Current behavior
known-issues.md ("Core authoring limits"): one quad, signed object-space displacement; all-face (including one-quad plane) extrusion is unsupported until a pinned fixture defines default behavior; region/world extrusion, divisions, offset/taper, UVs/normals and construction-history nodes pending.
Expected behavior
Native Extrude with a manipulator workflow and history, then region/world extrusion and options, matching the pinned reference.
Acceptance criteria
- Default behavior for all-face extrusion taken from a pinned Maya fixture.
- 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.
- 主要语言
- Rust
- 星标
- 4
- 派生
- 2
- 平均合并
- 2 小时 44 分钟
- 30 天内合并 PR
- 59
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
cristim/AztecCraft 的其他 Issue
-
area/ui-parity type/bug
难度 2/5 1-3 小时 新手友好度 72/100
cristim/AztecCraft#140 ·
维护者通常 1 天内回复
-
area/ui-parity good first issue type/docs
难度 2/5 1-3 小时 新手友好度 72/100
cristim/AztecCraft#85 · 1 条评论 ·
维护者通常 1 天内回复
-
good first issue type/docs
难度 1/5 1 小时以内 新手友好度 75/100
cristim/AztecCraft#79 · 1 条评论 ·
维护者通常 1 天内回复
-
area/selection area/viewport type/feature
难度 5/5 一周以上 新手友好度 20/100
cristim/AztecCraft#135 ·
维护者通常 1 天内回复
-
bug
难度 4/5 3-5 天 新手友好度 22/100
cristim/AztecCraft#128 ·
维护者通常 1 天内回复
查看 cristim/AztecCraft 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 63/100
AimesSoft/NipaPlay-Reload#1022 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
ZcashFoundation/frost-tools#612 ·
-
难度 2/5 1-3 小时 新手友好度 64/100
ScoopInstaller/Extras#19070 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100