Studio checks the map after every edit, the same way Install does, so you find out about a broken portal when you make it, not when you install.
Problems
The Problems panel on the rail, and the Problems and changes dock under the map, list what would stop an install and what it would warn about. The rail icon and the dock's title carry the count. Click a row to select the object it is about and fly to it.
Click the dock's title to open or fold it, and drag its top edge to make it taller. It stays the way you leave it.
Changes
The Changes view, beside Problems, covers the map in front:
- Review every project change… at the top opens the review below.
- Install would write: the files this map's install writes, each marked client or server. On RF Online the map's spawns, NPCs and portals are one row, placement rows of map …. Click a row to open it in the review.
- Every object added, changed or deleted since the map was opened, folded across the undo history, so moving a crate there and back again shows as no change. Click a row to find the object. The arrow at the end of a row reverts that one object as one step, and Undo brings the change back. A deleted object comes back at the end of the map's list.
Edits loaded from a saved project count from when the map was opened, so the list starts empty each time; the review below compares with the game's own copy instead.
Reviewing every change
Review changes…, in the File menu, at the top of the Changes view and in the Install dialog, lists everything the next Install writes, compared with what the client and server hold now. Its title bar has the Install dialog's choice: Only … the map or document in focus, or Whole project. The choice is shared with Install, and the review opened from the Install dialog starts on that dialog's choice. Esc or Close leaves it, and the round arrow checks again.
For the whole project it lists, with or without a map open:
- every edited map's files, open or not, and, on RF Online, their spawns, NPCs and portals in the server's database (placements);
- game data tables you edited;
- the project's own files: textures, models, scripts, dialogs, and archives Studio rebuilds around them.
Each row says whether the change adds, changes or removes something. A file two maps both change is one row, merged from both; when the two changes overlap it is marked clash and shows what each map changes there. See When two maps change the same file.
Ticking what to install
Every row has a tick, all ticked to begin with, and the box at the top ticks or unticks them all. Install N of M… opens the Install dialog for the ticked changes only. See Installing some of the changes.
What a change does
Pick a row to see what it changes:
- a text file: the lines added and removed, with three lines around each;
- a game data table: the cells that change, row by row;
- RF Online placements: the spawns, NPCs and portals added, changed or removed;
- an archive: its size and the project files it takes in;
- anything else, such as a map's own binary files, a sound or an animation: its size and checksum before and after.
Open shows a game data table, script, dialog, texture or model in its own editor. A model opens only when Studio can tell which catalogue entry it belongs to.
Reverting
Revert takes a change back out of the project:
- A change a map makes puts back, as the game has them, only the parts of the map that make that file: one kind of object on the client or server side, a painted grid, or a map setting. The rest of the map's edits stay. An object you removed goes back in its old place. A revert works on whole parts, never on one object, because the game's files number objects by their place in the list. When the map is open in a tab it is one step, and Undo brings it back; when it is not open, Studio asks first, and Undo cannot bring it back. A file two maps merge into reverts the same parts in both.
- Revert map to the game's copy throws away every change to the map, saved and unsaved, after asking. A map the game has no copy of, such as one you built from a scene, reverts only this way.
- A game data table goes back to the server's copy, after asking.
- A project file or an archive's files are taken out of the project after asking, and a copy of each is kept in the project's
revertedfolder.
The preview
Changes to things the client draws, such as props and map settings, are rebuilt into the map a moment after you make them, exactly as Install would write them. The status bar shows Updating the preview while that happens. The map you are looking at stays on screen until the new one is ready.
Undo and redo
Ctrl + Z undoes and Ctrl + Y (or Ctrl + Shift + Z) redoes, as far back as the map was opened. The undo and redo buttons in the toolbar, and the Edit menu, name the step they will undo or redo. The History list on the Tools panel jumps several steps at once.
Every drag, stroke, paste, arrangement and macro replay is one step. Esc during a drag puts everything back without adding a step.