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

Duplicate, instancing, parenting and grouping

Open
  • Is something wrong?
#42 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 the Scene management section of .project-docs/parity.md and the coverage inventory in .project-docs/mcp.md, then read the pinned Maya reference in #5. The issue spans undoable scene operations, Outliner drag-reparent, MCP tools and a native visual check, so it needs design work before code. Done means the operations are undoable and tested, failed operations keep the baseline, and the docs are updated.

Written by the indexing model from the issue text.

Description

area/modeling type/feature

Problem

Hierarchy and instancing can be read from imported scenes but cannot be authored.

Current behavior

.project-docs/parity.md (Scene management): hierarchy, instancing and generic attributes pending.

Expected behavior

Duplicate, instance, parent/unparent and group as undoable typed operations with Outliner drag-reparent and MCP tools.

Acceptance criteria

  • Shared-instance edits report their effect on every instance.
  • 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 28m
Merged PRs (30d)
76

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.