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

Scale tool (R), object and world space

Open
  • Is something wrong?
#36 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
18/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
api, desktop

Research direction

Start from the disabled Scale button in the editor UI and the Rotate tool it depends on, since the issue requires the same dependencies. Read .project-docs/mcp.md and its coverage inventory, because the MCP tool schemas, Editor protocol tests and docs must change in the same change. Done means the object-space channel edit works with the required refusals, failed operations keep the baseline, and the visual check and parity note against #5 are recorded.

Written by the indexing model from the issue text.

Description

area/selection area/viewport type/feature

Problem

Scale is a disabled button.

Current behavior

Not implemented. Approved plan scope is an object-space single-object channel edit.

Expected behavior

Axis boxes and center box, factor finite and > 0, f==1 bit-exact, world space only when node rotation is axis-aligned within a stated tolerance, refusal of nonzero scale pivot and zero or negative factors. Docs: https://help.autodesk.com/cloudhelp/2026/ENU/Maya-Basics/files/GUID-487B6A23-E135-45E2-94F1-B0D59D6B6F33.htm (Scale Tool), https://help.autodesk.com/cloudhelp/2026/ENU/Maya-Basics/files/GUID-09D0E733-74DF-44E2-937A-C857001E45B2.htm (scale objects).

Acceptance criteria

  • Same dependencies as Rotate.
  • 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
4h 4m
Merged PRs (30d)
116

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.