UGTK / Toolkit / Gameplay Systems / Loading System Completed

Loading System

Summary

The Loading System is a singleton loading-screen manager that instantiates a loading prefab under a chosen (or auto-found) Canvas and shows an animated "Loading..." text with a progress slider and percentage. It supports timed loadings, indefinite/visual-only loadings, and multi-step weighted processes.

Modules Dependencies

Design Pattern / Singleton: Mn_LoadingManager derives from Mn_Singleton<Mn_LoadingManager>.
TextMeshPro: the loading and percentage labels use TMP_Text.

Setup

Put the LoadingManager prefab in every scene that shows a loading screen, or call DontDestroyOnLoad on it yourself. Mn_LoadingManager is a Mn_Singleton: there must be exactly one at a time, and it does not survive a scene load on its own.
Use LoadingPrefab for the visible part - the screen, the bar, the label - or replace it with your own and keep the same references.
Describe the work as LoadingProcess entries rather than loading in one call. Each one reports its own progress, and the bar is their sum.

The reason for the third step is worth stating plainly: SceneManager.LoadSceneAsync reports progress for the scene only, so a bar driven straight from it reaches 90% and freezes there while everything else - databases, textures, a server round trip - happens with no feedback at all. Splitting the work into processes is what makes the last tenth of the bar mean something.

How To Use

Add Mn_LoadingManager to a bootstrap GameObject and assign loadingObjectPrefab (must contain a TMP_Text, a Slider and a child TMP_Text named "Advanced").
Leave autoFindCanvas on to auto-pick a Canvas named "Main" (or the first active one), or disable it and assign canvasRef manually.
Access it via Mn_LoadingManager.Instance:
StartLoading() / StartLoading(startAction, endAction) runs a timed loading of defaultDuration; a negative duration means infinite (text only, no slider).
EndLoading() hides the loading UI.
SetProcesses(List<LoadingProcess>, onComplete) then UpdateProcessProgress(current, max) drives a weighted multi-step progress bar (each LoadingProcess has start, end, name).
Enable autoStart to begin loading automatically on Start.

Testing Scene

Open LoadingScene in the module's Debug/ folder.

What to do, in order:

Call SetProcesses() with two or three steps, then StartLoading().
Drive each one with UpdateProcessProgress() and watch the bar.
Call EndLoading() before the last process has finished.

Step 3 is the case that matters in a real game: loading almost never ends exactly when the bar reaches the end, and a bar that jumps from 60% to gone looks like a crash rather than a finish.

LoadingScene with Test Loading Processes pressed from the manager's inspector. The loading prefab is inactive until a process starts, which is why the scene looks empty at rest; the bar then advances through the queued processes rather than through one scene load.

Technical Info

Mn_LoadingManager: singleton that spawns and controls the loading UI (animated dots text, slider fill coroutine, percentage, process sequencing).
LoadingProcess: serializable data holding a process start, end (0-100) and name used for the weighted progress mode.
Mn_LoadingManager_Editor: custom inspector.