ryan
3f66cc3195
- Introduced a new action type `move_to` allowing children to direct a stickman to a destination using either Walk or Run styles. - Updated the ActionEditor UI to include Walk/Run buttons for selecting movement styles. - Ensured compatibility with existing `walk_to` actions by converting them to the new `move_to` format during loading. - Defined clear success criteria for the implementation, including distinct movement animations and behavior for both Walk and Run. - Established a comprehensive verification contract to ensure functionality across various terrains and scenarios.
1.9 KiB
1.9 KiB
Feature Backlog
This is the live list of future Stickman Studio feature ideas. Designer maintains it as ideas become clear in discussion with the user.
Suggested order
Priorities are recommendations for discussion, not a committed release schedule. Keep higher-priority items first and explain the reason for each ranking.
- Move To with selectable movement styles — Status: Verified · Suggested priority: High. Intent: Give a stickman one destination action with a per-action style choice, starting with Walk (default) and Run; leave room for future styles like Fly. Use a fixed pace for each style initially, matched to its animation. Rationale: Children can direct the same route at different paces without choosing duplicate action types. The first run cycle should read as a believable human gait on the existing stickman rig, with clear foot contact and push-off, a flight phase, alternating arm swing, and cadence matched to travel speed. Connections: Phase 16 design brief,
scripts/stage/action_registry.gd,scripts/editors/stage/action_editor.gd,scripts/stage/stage_scene_io.gd,scripts/characters/stickman/stickman_locomotion.gd,scripts/tools/create_animations.gd; existing scenes and rules currently storewalk_toand should continue as Move To · Walk.
Entry format
For each feature, record:
- Status: Idea, Exploring, Planned, Verified, or Parked
- Suggested priority: High, Medium, or Low
- Intent: The user goal or experience the feature should support
- Rationale: Why it may be valuable and how it fits the project
- Connections: Relevant project docs, code, and dependencies, when known
Historical context
The archived roadmap is historical material, not an active priority list. Revisit individual ideas from it only when they are relevant to a current discussion.