Banner Replay: two Zenless Zone Zero banners, played back from their own data

Wherever something is still missing, it stays missing, because nothing here is drawn, generated or keyframed by hand to fill the gaps.

PhoenixGachaDemoInfoBgRow_Phoenix, Spine animation idleOfficial EP: “1% Battery Girl”
RemielleGachaDemoInfoBgRow_Remielle, Spine animation loop2Official EP: “Two to Tango”

What this is

These are the animated backgrounds of two Zenless Zone Zero Signal Search banners, for the agents Phoenix and Remielle, which I rebuilt from the game's own layout and animation data so they can be played back outside the game.

Both banners are Unity prefabs, GachaDemoInfoBgRow_Phoenix and GachaDemoInfoBgRow_Remielle, and they're stored in the same asset block, StreamingAssets/Blocks/1534144329.blk. I read them from the installed game files and nothing else, so nothing was ever injected into the game, and its memory was never read or changed either.

Why this is a video

The replay actually runs live in a browser, so I could have embedded it just as it is. I've published it as a recording instead, though, and there are three reasons for that.

  • The game's files stay with me, because playing the banners live would mean putting the actual Spine skeletons, atlases and textures on this site, where every visitor can download them. Plus, they are the game's own files, and I really don't want them leaking from here and spreading. That said, what you see is a recording of what I've recovered, rather than the Spine resources themselves.
  • Every frame is exact, since the recording isn't a screen capture. Instead, the page's clock is replaced and advanced by exactly 1/60 of a second at a time, with each step saved as one frame, so the result doesn't depend on how fast the machine is, and it can be produced again frame for frame.
  • It plays everywhere, because a 60 FPS H.264 file doesn't need WebGL, a Spine runtime or any of the source files. You can also use the frame buttons under each recording to step through it one 1/60 s frame at a time.

960

frames per banner, 16 s at 60 FPS

4.3.23

Spine version of both skeletons

121 / 161

components read in full, Phoenix / Remielle

5.33 s

skeleton loop, the same in both banners

0

network requests in the offline player

0

keyframes added by hand

Layout, read from the prefab

Every layer is placed from its own RectTransform, meaning its anchors, pivot, position, size, scale and rotation, and the layers keep the prefab's original sibling order on the banners' 2580 × 1080 design canvas. On top of that, I apply the PC data of the game's MonoUILayoutAdaptor (the game's own enum gives PC the value 1), which moves the character root by (−50, 0) for Phoenix and (18, −517) for Remielle.

Each skeleton's origin is simply its node's original pivot, and there's no automatic centring or manual scaling involved, so Phoenix's skeleton data scale stays at 1.0 and Remielle's at 0.6600000262, both exactly as stored. I've also left the character nameplate layer out.

Motion, from the game's own curves

The characters are their original Spine 4.3 skeletons, played by the official Spine Web runtime, using idle for Phoenix and loop2 for Remielle, which are each about 5.3333 s long.

Phoenix's background moves on the game's tween components, where two hearts rotate and the logo scales on 4-second ping-pong tweens, while a small emoji rotates on a 3-second one, all using the amplitude, period and easing stored on each component. Remielle's background, on the other hand, follows the game's own animation clip, ActivityDemoRemielleLoop, which is a 4-second loop of position, scale and opacity curves. I sample that clip the same way Unity evaluates it, so its weighted Hermite tangents are turned into a cubic Bézier and then solved for time by bisection.

Where each layer starts, which layers are switched on and how transparent they are all come from the last frame of each banner's entrance clip (ShowFadeIn), so the recordings begin in the same state the banner settles into once it has appeared.

The rigs on their own

If you hide every image layer of the banner, only the skeletons are left, and that's what the rig recordings on the home page play, on this site's own background rather than the game's. These are the numbers read from the skeleton data at load time:

PhoenixRemielle
SkeletonUISpine_PhoenixUISpine_Remielle
Bones383411
Slots247350
Attachments247325
Constraints3222
Animationidle, 5.3333 sloop2, 5.3333 s
Data scale1.00.66

Both banners cut their character off at the bottom of the 2580 × 1080 frame, and the rig recordings keep that cut, so each one shows only what the banner shows and fades the cut out.

Pointing at parts

On the home page you can point at either rig and see which slot draws the pixel under the cursor. Since the page doesn't have the skeleton itself to ask, the answer comes from a second recording of the exact same frames instead. That recording uses a copy of each atlas with every visible pixel turned white and the rest cleared, sampled without filtering, and it draws every slot in one flat colour that encodes its index, with the low byte in red and the high byte in green. Any slot that's hidden, or less than half visible on that frame, simply draws nothing.

Over one full loop of 320 frames, the coloured silhouette covers the same pixels as the real one, scoring 99.6% for Phoenix and 99.9% for Remielle as intersection over union.

Nothing gets grouped or renamed along the way. Each frame is reduced to a quarter-scale grid that keeps the slot at the centre of every 4 × 4 block, and then every second frame is kept, run-length coded and gzipped, which comes to 837 KB for Phoenix and 1.39 MB for Remielle. In the browser, the grid for whichever frame is on screen gives the slot under the cursor, which is shown with its name and its bone exactly as stored in the skeleton data, while marching squares trace its outline.

Recording at exactly 60 FPS

The player runs in headless Chrome with its time sources replaced, so requestAnimationFrame, performance.now and Date.now all read one clock that only moves when it's told to. Each step moves that clock 1/60 s, runs the frame callbacks once and saves a screenshot, and this happens 960 times per banner. The frames are then encoded to H.264 at 60 FPS.

I chose sixteen seconds because that's where the loops line up. For Remielle it's three skeleton loops and four background loops, so the recording repeats without a seam. For Phoenix it's three skeleton loops and two cycles of the heart and logo tweens, and the only exception is the emoji, which runs on a 6-second cycle and so doesn't meet itself at the loop point.

Checked offline

Both banners pass an offline check, which means the player makes no network requests, throws no script errors and has no broken images, since everything it shows comes from the exported data and the files beside it.

What isn't rebuilt yet

The recordings are really a preview of the recovered data, rather than a copy of what the game itself draws. The parts below are still open, and I've left those gaps visible instead of filling them in:

  • The game's UI shaders. The materials (VX_Bg, VX_Lace, VX_Logo, VX_WindowColor01/02 and others) have been extracted, but their dissolve, tint and additive blending aren't implemented yet, so those layers are shown as plain images, which can look whiter or brighter than they do in the game. That affects 14 layers in Phoenix's banner and 19 in Remielle's, which still use one of these materials.
  • Some textures and effects. There are still 2 textures missing from Phoenix's banner and 10 from Remielle's, plus Remielle's flow-path and particle effects (UIFlowPath, UIParticle) aren't played yet.
  • The final placement on screen. The banners are shown on their design canvas, and I haven't checked yet how the game's Signal Search page scales, crops and offsets them on a real screen.
  • Physics state. Since the skeletons run in the Spine runtime rather than in the game, their physics aren't guaranteed to match the running game frame for frame.

Notice

© All rights reserved by miHoYo.

Other properties and any right, title, and interest thereof and therein (intellectual property rights included) not derived from Zenless Zone Zero belong to their respective owners.

This is a non-commercial fan study. The characters, art and animation are miHoYo's, while the analysis, tools and recordings are mine, and none of the game's files are on this site.

C

Calyndrae

Designer and developer

Next case studyPioneering