Old School Ops

Checking the project

One report of everything in the project that would stop an Install or look wrong in the game, from map clashes to textures, game data, scripts, dialogs and the model being edited.

Every game · updated 2026-10-10

Tools > Check the project looks over everything the project changes before you Install it, and lists what it finds in one place. Each check is one Studio already runs somewhere; the report runs them all at once, so nothing is missed because its panel was closed.

What it checks

areawhat it looks for
Installevery edited map and file planned together: two maps changing the same place in one file, and anything else that would stop the Install
Filesthe project's own textures: ones the game cannot read, sizes that are not a power of two or are past 2048 a side, and textures with no smaller levels
Game dataedits waiting to be saved that break a column's rule, such as a value too large for its field
Scriptsevery script the project changes, and every open script with unsaved edits
Dialogsthe NPC dialogs (Gate to Heavens), such as a button that leads nowhere
Modelthe model being edited on its Edit tab, as Check reports it there
Soundsreplaced sounds whose format the game will not play

Reading the report

Findings are listed worst first:

  • Blockers stop an Install or break something in the game. Fix them first.
  • Warnings are worth fixing; the Install still goes ahead.
  • Notes are worth knowing, such as a texture with no smaller levels.

Each finding says where it is, and Open takes you there: the Install dialog, the texture, the game data table, the script at its line, the dialog, or the model with the problem vertices selected. An area that cannot be checked right now, such as game data with no server linked, is listed as skipped with the reason, so you know it was not looked at.

The check takes a few seconds on a large project and can be run as often as you like; it changes nothing.

Something here wrong?

Out of date, incomplete, or assuming something it should not. Documentation errors are bugs, and this one arrives tagged and pointed at this page.

Top xp sources

How xp works
Loading…

Open the full search page