Skip to content

feat(characters): one animation over many directions, joined on this side - #78

Merged
protonspy merged 2 commits into
mainfrom
feat/one-animation-many-directions
Sep 20, 2026
Merged

protonspy merged 2 commits into
mainfrom
feat/one-animation-many-directions

Conversation

@protonspy

Copy link
Copy Markdown
Owner

No description provided.

…side

PixelLab starts a new animation group for every call to
POST /v2/characters/animations: animation_group_id is extra_forbidden on the
way in, and repeating animation_name or template_animation_id makes a second
group rather than extending the first. So the directions of one motion cannot
be joined on the provider, and this joins them here.

- character animate refuses a direction the motion already holds, before
  anything is sent, naming what it holds and what it lacks; --again buys a
  second take. Animating a direction it lacks says where the frames join.
- character show folds the groups of one motion into one animation and says
  how many PixelLab holds behind it.
- The subject record gathers the animation runs of one motion into one
  animation over every direction they covered and every file they wrote, so
  inspect and the atlas built from it carry all of them.

Names and direction labels coming back from the provider now reach a refusal
and the terminal, so they go through the same control-character table the
record already applies to a manifest.

specs/characters-and-animation R2.39, R2.40, R4.5; specs/asset-workspace R7.5.
Verified with scc validate --checks --pr: 1691 passed, 46 skipped, coverage
95.34%, ruff check and format clean, artifacts clean.
@protonspy
protonspy merged commit 2822b0c into main Sep 20, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant