fix(pets): keep BitBlob size consistent across actions - #3196
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
BitBlob visibly changes size when a session moves between idle, working, waiting, review and lifecycle actions. Working frames were oversized, while jump frames had roughly half the idle silhouette area.
Re-register the existing v2 artwork with consistent silhouette area and lower-body anchors, reduce the jump to a 16-pixel hop, and retain all original poses, frame counts and look directions. Play only the sprite animation for the built-in BitBlob so additional CSS mood transforms do not compound its authored motion. Other pets retain their existing presentation.
Validation:
pnpm run check:webpassed; motion inventory reviewed.Only shared frontend rendering and bundled artwork change. Remote workspace, remote control, peer-device and detached-dispatch paths were not exercised; no transport or persisted format changes.