Repository navigation
feat(pipeline): add the story.scene and story.asset products - #81
Merged
Merged
Conversation
story.scene (storyscenes/default.json) holds what the ADV screen loads before an episode's first line: the ADV scene, the camera manager, the character and background fields, the global volume, the ADV player and master id settings and the built-in graphics settings. scene.json names them by object id with the animator clip bindings and the shader name table; the renderers' shaders and post-processing textures are reached through the graphics settings. story.asset (storyassets/<key with / as ~>.json) holds the objects of one catalog key a story loads, such as a stage, frame, effect or still, with the bindings and shader table of what it reaches; an asset several stories load is one product. The lookup of a built-in settings root moves to content.prefabs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
adv.build is the episode logic (shards, commands, resource closure) for its inputs; adv.extract reads them from a catalog, and content.storyepisode from a product's object table and master rows: the episode's command list, its shard TextAssets and the default transition of the ADV player settings. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Summary
story.scene(storyscenes/default.json): what the ADV screen loads before an episode's first line — the ADV scene, the camera manager, the character and background fields, the global volume, the ADV player and master id settings and the built-in graphics settings.scene.jsonnames them by object id, with the animator clip bindings and the shader name table.story.asset(storyassets/<key with / as ~>.json): the objects of one catalog key a story loads (stage, frame, effect, still, chat window, transition, ...) with the bindings and shader table of what it reaches. An asset several stories load is one product.adv.buildis the episode logic for its inputs;content.storyepisodereads those inputs from a product's object table and master rows (command list, shard TextAssets, default transition).content.prefabs.builtin_rootlooks up a built-in settings root (moved fromlivescene).Test plan
pytest tests/pipeline/test_story.py tests/content/test_storyscene.py tests/content/test_storyasset.py tests/content/test_storyepisode.pystory.sceneexported from a real catalog: all seven keys reached, graphics settings and shaders resolvedCo-Authored-By: Claude Opus 5.5 noreply@anthropic.com