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

Polygon modeling toolset

Open
  • Is something wrong?
#46 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
8/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
rust
Domain
computer-graphics

Research direction

This is an umbrella issue, so it has no code change to start on. Read .project-docs/parity.md (the Polygon modeling section) and the pinned reference in issue #5 to see the agreed scope. The first real step is splitting the checklist (bevel, bridge, edge loops, weld, delete/cut, normals, subdivision, mirror/combine, Quad Draw) into child issues with sourced workflows. Done means those child issues exist and the feature gates are written for each.

Written by the indexing model from the issue text.

Description

area/modeling epic type/feature

Problem

Beyond cube/plane creation and single-quad extrusion no polygon tools exist.

Current behavior

.project-docs/parity.md (Polygon modeling): topology, bevel, loops, weld, normals, subdivision pending.

Expected behavior

Staged tools. Quad Draw reference: https://help.autodesk.com/cloudhelp/2026/ENU/Maya-Modeling/files/GUID-35D650EE-C840-4E4B-8E5C-DC5FFE4DA53A.htm .

Checklist:

  • Bevel
  • Bridge
  • Insert edge loop / edge loops
  • Merge / weld / collapse
  • Delete and cut/split
  • Normals (soften/harden, conform)
  • Smooth / subdivision
  • Mirror, combine, separate
  • Quad Draw

Acceptance criteria

  • Each checklist item is split into its own issue before work starts, with a sourced workflow list.
  • Every child follows the feature gates: visibly unsupported until done, MCP coverage with schemas, Editor protocol tests and docs, native visual check.
  • No percentage or parity claim until the pinned reference (#5) and the audited inventory exist.
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.