Ultimate Progression Framework System
v1.0.0
Reference & Support

Troubleshooting & Validation

Most UPFS issues come from missing references, unstable identities or dependent data that was not refetched after a structural edit. Start with the exact validation message, then verify the relevant relationship below.

Read Inspector validation first

UPFS surfaces configuration problems near the component that needs attention.

UPFS Inspector validation messages
Capture a representative Inspector showing clear UPFS warning and error messages.

Purchase fails

SymptomLikely causeResolution
No next upgradeProgression is complete or contains no generated entriesCheck IsFullyUpgraded and review Big Upgrades
No matching costCurrency names differ between definition and Wallet assetMatch names exactly and refetch/distribute
Cannot affordBalance is below the next generated costInspect GetNextUpgradeCost and Currency.GetValue
Player Choice rejectedSelected Currency is unavailable or not affordablePresent GetAffordableOptionsForNext results
Stale cost/indexUpgrade structure changed after economy fetchFetch Upgrade Info again

State does not load as expected

  • Confirm the current Upgrade Name or Currency Name matches the name used when the save was created.
  • Confirm Currency Type has not changed between Int and Float.
  • Use PlayerPrefs Viewer to verify that the expected key exists.
  • Check whether another development tool or reset flow cleared PlayerPrefs.
  • If first-as-base is enabled, remember that reset reapplies the first entry as the base state.

Info Provider data is stale

  1. 01
    Check source

    Verify that the correct Upgrade SO is assigned.

  2. 02
    Check structure

    Compare Big and Small Upgrade counts with fetched records.

  3. 03
    Refetch safely

    Use preserveExisting when custom metadata should be retained.

  4. 04
    Revalidate queries

    Confirm name and index-based consumers still point to the intended entries.

Confirmation dialogs

Destructive Editor operations request confirmation before replacing or clearing data.

UPFS confirmation dialog
Document one representative confirmation dialog used before a destructive generation or reset action.

Custom Inspector is missing

Unity must compile successfully before UPFS Editor tooling can load.

  • Open Console and resolve the first compile error in the project.
  • Confirm the UPFS package imported completely, including its Editor folder.
  • Reimport the affected script only after resolving compilation failures.
  • Verify that runtime code uses the bcylyLabs.UltimateProgressionFramework namespace.