[nichinichisou0609]

The scene of a live becomes one product, shared by every live: what exists on the live screen before the first note, and the start timeline and LightWeight background of each band.

Scene keys

• A scene bundle's container names a scene without an object; its scene hashes name the scene's serialized file. census.scenes reads them: a scene is the objects of that file outside a hierarchy (the root GameObjects and the scene's settings).
• link.addresses (version 4) lists them as the objects of the scene's key and gives them stable addresses under the scene's path, so a product can start from a key such as EmbScene/Live.

Product

live.scene (default, manifest scenes/default.json) starts from:

• the scene EmbScene/Live;
• the lane line and judge effect prefabs;
• the combo and judgement sprite assets;
• the sprites of every lane skin;
• the start timeline and LightWeight background of every band;
• the built-in GraphicsSettings, QualitySettings and PlayerSettings.

scene.json (format 1) holds:

Field	Contents
scene, renderSettings	the scene's root GameObjects and its RenderSettings
graphics	the built-in settings, by id
laneSkins, prefabs, spriteAssets	the lane skins' sprites and the UI prefabs and assets, by id; prefabs includes the bar line view the scene's bar line container instantiates
bands	per band: the timeline prefab, the background sprite, and {AnimationTrack id: {name, prefab, animator}}, the Animator each track plays on
settings	the option defaults and ranges the render path reads, the quality settings, the lane skins by option value and the judgement sprite names
bindings	every Animator's clip bindings, including the timeline tracks' clips on the Animators they play on
shaders	the shaders a lookup by name finds

The scene's roots reference components of each other with $refs. The object table lists each such component as contained in the root GameObject that holds it.

Shaders

A material names its shader by id, so a product may hold different shaders of one name, for example a bundle's copy beside the copy in the APK's built-in files. The name table of shader_table gives what a lookup by name (Shader.Find) finds:

• copies of one shader: the first id;
• different shaders of one name: the one GraphicsSettings always includes;
• otherwise no entry.

Every shader keeps its files either way. live.scene requires the shaders the live screen finds by name.

Content helpers

content.prefabs gains two helpers, and the note highway uses key_object:

• key_object: the object of a key of a class.
• component_ref: a component a field names, in the same hierarchy or through a $ref into another hierarchy.