Overview and included content

Tap a source bolt to lift its matching top nuts, then tap a compatible destination bolt. Group every colour together to clear the bench.

This is an editable Unity game template and starting point for your own title. Customize the visuals, copy, level progression and release settings for your audience, then test your changes. The included Android demo is a showcase build; it is not a signing key or a production store submission.

URP procedural workshop meshes with uGUI; tap-based sort puzzle The campaign contains 25 authored levels and game-specific procedural continuation. The included service kit is HyperCasual LiveOps Kit. Ads ship in Dummy/simulated mode and IAP is Disabled; third-party advertising/billing SDKs are not bundled.

Installation and first successful play

1. Back up your project and extract the main ZIP completely. Read Documentation/Documentation.html before importing the package. Offline documents do not require the hosted page to be available.
2. Install Unity 6000.0.62f1 through Unity Hub. Add Android Build Support (including the matching SDK, NDK and OpenJDK) if building Android, and WebGL Build Support if building browser demos. A supplied source project can be opened with Add project in Unity Hub.
3. For package import into a new project, select a Universal Render Pipeline template. Use Assets > Import Package > Custom Package and import the complete package. Do not omit the private game Kit, HyperCasualLiveOpsKit, fonts, settings, scenes or their .meta files.
4. Check Window > Package Manager: Universal RP 17.0.4, Unity UI 2.0.0 and Input System 1.14.2. Standard Unity modules include com.unity.modules.screencapture and com.unity.modules.androidjni. Let Unity finish compilation before opening a scene.
5. Set Edit > Project Settings > Player > Other Settings > Active Input Handling to Both manually. Restart if Unity requests it. The documented setup is a user action; do not rely on an import hook changing a buyer's Project Settings.
6. In Edit > Project Settings > Graphics select the supplied URP asset, and check the pipeline assignment for the active Quality level. Retain the packaged Settings assets and GUID references. A pink scene usually indicates a missing pipeline or shader assignment.
7. Open Assets/Games/NutSort/Scenes/NutSort_Mobile.unity. Press Play, focus the Game view, and follow the first-level tutorial: Tap a source bolt to lift its matching top nuts, then tap a compatible destination bolt. Group every colour together to clear the bench.
8. Stop Play mode before editing source or authored content. Open the landscape scene Assets/Games/NutSort/Scenes/NutSort_WebGL.unity and verify the alternate layout as well. Runtime-created UI changes made only in Play mode are not a saved reskin.

Folder structure and source reference

The concrete paths in this manual match this standalone/Codester layout. The game root is Assets/Games/NutSort. Keep .meta files with their assets so scene, font, sprite and material references remain valid.

Assets/Games/NutSort/
  Scenes/            Mobile and landscape entry scenes
  Scripts/           Rules, HUD, board view and game data
  Editor/            Game-specific authoring tools
  Resources/         Level JSON, artwork and game audio
  Kit/               Required game runtime and editor helpers
  Documentation/     This manual
Assets/HyperCasualLiveOpsKit/        Included service kit
Assets/TextMesh Pro/              Required text resources

Nut Bolt Sort reskin: interface colours and visible text

The interface is constructed in C# when the scene runs. There is no single static scene prefab containing every final label. Use the exact game files below; changing only a shared-kit theme or localization table will not replace game-authored HUD/menu strings.

1. Change interface colours

Open Assets/Games/NutSort/Scripts/NutSortGame.Hud.cs in your C# editor. Find these declared palette symbols; change only the quoted hexadecimal value in the existing HzUI.Hex(...) assignment. Preserve the symbol, type and surrounding syntax. This keeps every caller using the shared colour in sync.

Concrete first colour edit: in Assets/Games/NutSort/Scripts/NutSortGame.Hud.cs, find this fragment within its existing declaration:

Navy = HzUI.Hex("#1B1F4B")

Replace only that colour value, for example:

Navy = HzUI.Hex("#24485C")

1. Save the source and return to Unity. Wait for compilation, resolve any Console errors, and start a fresh Play session so the UI and cached generated artwork are rebuilt.
2. Inspect the changed HUD surface, settings menu and a win/lose or booster popup. Verify that text remains readable, selected/disabled states remain distinct, and icons are visible against the new background.
3. Check the mobile and landscape scenes. Some popup, world, camera and material colours are separate literal assignments in Scripts/NutSortGame.Hud.cs or the .View.cs file. If one surface did not change, inspect the colour argument used by that exact control instead of replacing every matching hex value globally.
4. For a procedural colour change, stop and re-enter Play; if you deliberately disabled domain reload, restart the editor when testing static sprite/material caches. A bitmap with baked-in colours must be edited separately from the C# palette.

2. Change a visible HUD label

Open Assets/Games/NutSort/Scripts/NutSortGame.Hud.cs, find BuildHud and locate this exact source line:

_levelText = HzUI.Label("Level", _col, "LEVEL " + Level, 86, Color.white);

To call levels stages, change the display string while preserving the level expression and formatting:

_levelText = HzUI.Label("Level", _col, "Stage " + Level, 86, Color.white);

This is a targeted edit to the displayed string, not a global search/replace of object names. HzUI.Label("Lvl", parent, "LEVEL " + Level, ...) uses its first string as a hierarchy/object name and its third argument as visible text. In assignments such as _levelTxt.text = ..., edit only the literal part; retain the number, interpolation braces, arithmetic, conditional branches and formatting.

3. Edit menus, popups, title and booster captions

Use this game-specific lookup table. The snippet is a search target in the named file; it shows the actual display-writing call rather than an assumed localization key. Line numbers are navigation hints for this revision and can shift after your edits.

1. Change the Title property in Scripts/NutSortGame.cs for the game title exposed by the base game. Also change any separate literal title built by the HUD/view; a Title property is not a universal replacement for all title art.
2. Change visible menu captions in ShowSettingsPopup and the help-page strings in NutSortGame.Hud.cs. Keep action callbacks, toggle variables and control object names unchanged.
3. For booster names edit BoostName in Assets/Games/NutSort/Scripts/NutSortGame.cs. For booster help edit BoostDesc in Assets/Games/NutSort/Scripts/NutSortGame.cs. Preserve array lengths/order, booster IDs, unlock logic and charge values. A cosmetic caption must not rename an ad placement, resource lookup or PlayerPrefs key.
4. For status counters, change the actual refresh method, not only the label initializer; otherwise the next frame or level load may overwrite your new caption. Update singular/plural and portrait/landscape variants together.
5. Translate tutorial/help/result text in the game files and level name / hint fields where used. Keep \n line breaks and {...} interpolations valid, and test long lines in narrow portrait popups.

4. What the shared localization guide does and does not cover

The shared HyperCasual LiveOps Kit localization guide concerns UI and content that use that kit's localization service. This game's literal strings in the files above are not automatically replaced by adding entries to an HLK table. For one-language reskinning, edit the literals and data shown here. For runtime language selection, explicitly route those game display assignments through your chosen lookup service, provide keys for each caption, and refresh active labels when the language changes. That is an integration task, not a delivered translation toggle.

The landscape title is the two-line string NUT BOLT\nSORT in BuildSides; the portrait level heading is created in BuildHud. Both live in NutSortGame.Hud.cs. Changing Title in NutSortGame.cs alone does not replace that landscape title. Booster display names are in BoostName. Nut colours and material/mesh details are in the view and material-generation code and are separate from the Orange/Blue/Navy/Brass/Cyan HUD constants.

5. Verify the reskin

1. Launch both supplied scenes with a normal player save. Confirm the edited level heading, game title, settings/help buttons, counters and booster names.
2. Open a result popup and a refill offer, and replay the first-level and first-booster tutorials using a disposable test profile or the documented developer controls. Confirm that the changed colours remain readable behind all overlays.
3. Test one valid move, one invalid action, progression to the next level, a retry and one available booster. A text reskin must not change goals, costs, rule checks or resource IDs.
4. Make a new Android/WebGL test build after source edits. Existing hosted demos and videos will continue to show their previously built appearance until rebuilt; editing this manual alone does not change those binaries.

Artwork, fonts and audio replacement

Game-specific resource directories in this edition:

1. Replace an existing sprite or audio clip through Unity's Project view while keeping its resource base name and .meta/GUID. If you rename or move it, update its Resources.Load lookup and any serialized references together.
2. For a UI icon, find the Art(...) / art-class Get(...) call in the HUD script and its base name under the Art directory. Imported sprite colours may be baked into the pixels; palette edits only affect code-applied tint or generated geometry.
3. For a 3D scene, inspect the .View.cs file and any game-specific material/import helper before rerunning material generation. Back up custom materials first; generation commands may overwrite generated material settings.
4. The game kit resolves its fonts in Assets/Games/NutSort/Kit/Runtime/HzUI.cs. Read Display and Body for the current resource paths. Use fonts with redistribution rights, retain their licence notices, and test accented characters/glyph coverage at the existing sizes.
5. For sound effects, inspect the game's sound-name constants/calls and Assets/Games/NutSort/Kit/Runtime/HzAudio.cs. Replace the matching Sfx resource without changing its base name. Named event variants and synthesized fallbacks are handled by the kit; a new filename does nothing unless a caller requests it.
6. Music is a separate resource/playback path. Match the PlayMusic lookup if this game supplies a track. Set reasonable clip/volume settings and test mute, focus/background behaviour and device output. Do not infer audio-device testing from a successful build.

Retain the original licence/attribution files for fonts, icons, audio and other included dependencies when distributing your customized game.

Level editor: concrete editing workflow

Open Nut Bolt Sort > Level Editor. Its implementation is Assets/Games/NutSort/Editor/NutSortLevelEditor.cs. The following names are taken from that editor, so use the displayed control name rather than assuming a generic inspector.

1. Exit Play mode. Back up Assets/Games/NutSort/Resources/nutsort/Levels/levels.json. Select an authored non-tutorial level to avoid unintentionally rewriting the onboarding sequence.
2. Use the available duplication/add control to make a working copy when offered. Change its display Name (or Picture name) and one gameplay property using the visual editor. Keep the first tutorial level intact until you understand its scripted guidance.
3. Run the editor's validation control and read the concrete warnings/errors. Fix missing references, invalid board geometry, impossible goals or malformed data before saving.
4. Save using the editor's Save control. If you intentionally edit JSON externally, save valid JSON, then use Reload/Reload from disk in the editor before continuing. Do not keep two unsaved versions of the same data open.
5. Use Play this level when available, or the documented DEV level navigation, to play the exact changed level. A solver/bot result is useful authoring evidence but does not replace checking the human controls, timing, tutorial and reward flow.

Procedural generation and level data reference

The level data used by this game is located here: Assets/Games/NutSort/Resources/nutsort/Levels/levels.json. Generation logic is in Assets/Games/NutSort/Scripts/NsGen.cs. Keep the authored campaign and generated continuation distinct when estimating your content count.

Generation controls exposed by the game editor include: Difficulty curve (bar = 1 - casual bot win rate after Validate All, else the design value; green = breather, red = HARD), Seed, Curve: values ramp linearly from the first to the last generated level, Generate.

1. Back up the level JSON before a generation operation. Choose a small trial range and a repeatable seed first, then inspect what is appended or replaced. Do not assume a command is append-only; a selected-level regeneration or Rebuild command can replace authored content.
2. Read the game-specific fields in the level editor and generator source. Match generated board dimensions, rule limits and special mechanics to the intended difficulty; do not copy parameters from another game.
3. Validate generated output, play several early/mid/late boards, and check that the tutorial still introduces mechanics before the generated content requires them. Keep a saved known-good seed for regressions.
4. Treat visual difficulty labels and bot/solver scores as authoring aids. They do not guarantee that every generated board is suitable for every player or that a target completion time is achievable.

Use these field names exactly. JSON keys are serialized identifiers, not interface captions; changing a field name requires corresponding changes to the serializable model, loader, editor and generator. Duplicate levels through the editor when possible rather than guessing a nested schema.

Authoring controls and booster configuration

Effect, unlock and first grant

The descriptions below are the actual game-authored booster help. Unlock and starting inventory are read from Assets/Games/NutSort/Scripts/NutSortGame.cs; existing saves keep their previously stored state.

To rebalance, edit the matching BoostUnlock and BoostStart values and the corresponding handlers; keep the four entries in the same order. To rename or translate, edit BoostName in Scripts/NutSortGame.cs and BoostDesc in Scripts/NutSortGame.cs. A targeted booster may require a second tap on an eligible object; read its handler and test invalid targets before changing consumption logic. Refills must be granted only after the successful rewarded callback; cancelling an ad must not grant a reward.

Game text versus saved data and service configuration

Game progress, tutorial flags, currency and booster inventory are stored through the private HzSave helper and Unity PlayerPrefs. Search that helper and the main game script for the current key prefix. Changing displayed titles does not require changing those keys. Renaming keys can make an existing player appear to lose progress; plan migration before doing so.

Use a separate test profile when replaying onboarding. Do not use a global DeleteAll operation in a buyer's existing multi-asset project. Developer resets and unlocks should be used deliberately on test saves. Confirm the state after stopping/restarting Play, because an old saved tutorial flag can correctly suppress the popup you expect to see.

The HLK settings asset is Assets/HyperCasualLiveOpsKit/Resources/HLK/HLKSettings.asset. Ads default to Dummy and IAP to Disabled. Keep those defaults while reskinning. A production provider requires its real, separately installed SDK, IDs, platform configuration and testing. Optional setup documentation does not mean a provider SDK is included or automatically installed. Keep service identifiers, ad-placement IDs and reward callback semantics separate from translated button text.

Reskin troubleshooting and release check

Before your own release: review branding, UI contrast, tutorial wording, authored/generated levels, saved progress, every booster, pause/mute controls and both layouts. Set your own application identifier, icons, version, signing and release privacy/service settings. Perform actual target-device/browser testing; this manual and its documentation-only update do not certify your customized binary.

Licences, support and documentation access

Keep the included font, icon, TextMesh Pro, audio and HyperCasual LiveOps Kit notices with your distribution. Marketing illustrations are separate from authentic gameplay screenshots. Refer to the included licence/AI disclosures for the supplied components; adding your own assets requires checking their distribution terms.

For product support, use the marketplace item support channel. SatisVizion support email: satisvizion@gmail.com. Include the game name, Unity version, target platform, exact Console error, changed files and clear reproduction steps. Do not send signing keys, passwords or private service credentials.

This is the main game manual. It is included offline in the main ZIP and the game's Documentation folder. Shared-kit detail is available in HyperCasualLiveOpsKit.html in the offline documentation bundle; within the Unity project, open the included kit's Documentation folder. The current online manual is linked in the publisher metadata. Installation and basic use do not depend on visiting an external storefront.