Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Native Extrude control with manipulator, region and all-face extrusion

Open
  • Is something wrong?
#44 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
12/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
api, desktop

Research direction

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.

Written by the indexing model from the issue text.

Description

area/modeling type/feature

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.md and 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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cristim/AztecCraft

All issues in cristim/AztecCraft

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.