Not every developer question needs a polished twenty-minute tutorial. Sometimes the useful artifact is a short engineering stand-up that shows the working feature, the important data transformations, and the part that took real effort to sort out.
Why I made this
The game needed a custom score display whose digits matched the visual style rather than using ordinary text. That meant keeping the artwork easy to revise while also turning a changing integer into the correct sequence of sprite objects at runtime.
The implementation also needed predictable behavior for zero, negative values, the integer limit, and unused digit positions. Those are small details, but leaving them unexplained makes a seemingly simple UI example difficult to reproduce.
What I did
I start with the finished interactive score screen, then trace the visuals back to a Photoshop file stored in the Unity project. The Sprite Editor slices the digit sheet into individual assets, and saving an art change in Photoshop updates the result in Unity.
I test the display with a normal score, zero, a negative value, and the maximum integer. That makes the expected boundaries visible before moving into the code.
The ScoreObject holds the digit positions and the sprite array. The update function converts the integer to a string, then to a character array, loops through those characters, selects the corresponding sprite, and enables only the positions the score needs.
I explicitly label the format as a fast stand-up rather than a from-scratch lesson and invite questions for anything I move through too quickly. That keeps the scope honest while still sharing the reusable core.
Chapters
Select a chapter to jump the video directly to that part of the workflow.
A note on the archive
This recording uses Unity's 2017-era Resources, Sprite Editor, object hierarchy, and C# patterns. Current UI systems and asset-loading practices may provide better implementation options; use current Unity guidance for production work.
The chapter timings come from auto-generated captions that occasionally mishear technical terms. The labels above have been cleaned against the demonstrated workflow rather than treating the raw transcript as authoritative code documentation.