Rolly Docs

Find and fix setup problems

Where Rolly products report a setup mistake, how to run their checks on demand, and how to quiet the lines they print on screen.

Sheet
10 of 64
Rev
1.0.0
Updated
On this sheet

Every setup check says what is wrong and how to fix it. The setup messages page lists every message with its fix.

Checks on save

Saving a data asset of a Rolly product (a settings collection, a Rolly Save Core UI Theme) checks it through Data Validation, on by default. Right-click an asset > Asset Actions > Validate Assets, or Tools > Validate Data for the whole project, runs the same checks on demand.

Reports while the game runs

Setup mistakes found while the game runs (an unknown tag passed to a node, a node used on the wrong kind of data, an asset or a class named in Project Settings that cannot be loaded) are reported once per session, and each Play In Editor session reports afresh:

  • one line in the Output Log (log category LogRollySaveCore);
  • the Message Log, under the Rolly Save Core listing, with a link to the object (not in Shipping builds);
  • a line on screen (not in Shipping or Test builds). The console variable rollysavecore.setuperrors.onscreen 0 turns the on-screen lines off.

Project Settings > Plugins > Rolly Save Core > Verbose Logging prints extra setup diagnostics to the Output Log while you wire a new project.