Game data: column math, models and CSV

The Game data panel opens a table of your server's game data as a document, for RF Online 4.55, 4.15, 1.5 and Golden Age. These tools work on the table in front. Every change they make is a pending edit like one you type: it shows tinted, Save checks it against the table's rules, and one undo takes the whole step back.

Column math

Select cells in one or more number columns, then press Ctrl + M, choose Math on the toolbar, or right-click a header and choose Column math on this column.

• Every row shown applies it to the column in every row the filters keep, not only the selection. Filter the table first to pick the rows, for example >=40 under a level column.
• Whole-number columns round the result to a whole number.
• Clamp to range keeps every result inside the column's own limits. Without it, a result outside them is marked red and Save refuses it until you fix or undo it.
• Text and flag columns, and locked columns, are refused with the reason.

Viewing a row's model

On a row that draws something, press Ctrl + Shift + M, choose the person button on the toolbar, or right-click and choose View model. The model opens in a new tab of the model viewer.

• Monsters open the creature their code draws.
• Weapons, armour parts, shields and cloaks open the mesh the client's own item table gives that row. An armour part opens on the first body allowed to wear it.
• Other items, such as potions, amulets, rings, bullets, ore, boxes and siege kits, open the model the client draws for them, which for most kinds is the one model it shows on the ground.
• Animus items open the animus they summon. An animus level table opens that animus in its first form, because the game's data does not say at which level its look changes.
• Guard towers, traps, mining machines and barricades open the structure they place.
• A unit part opens on its unit's frame. A unit frame, and a unit key, open the whole unit wearing its default parts.

Rows with no model

Some rows link a mesh that the client does not ship. About a quarter of the weapons and a third of the helmets and cloaks are like this, and some kinds of item, such as tickets and coupons, have no model at all. Studio checks every row once when the table opens and puts a small warning sign beside the row number of each one. Rows that are fine show nothing extra.

On a marked row, View model is greyed out. Its tooltip and the status line at the bottom say why: the row links a mesh the client does not ship. Studio never shows a different model in its place. To fix the row, change its model code to one the client has. Once you edit a marked row, View model is available again and checks your new value.

Tables whose rows are not models at all, such as experience or skills, have View model greyed out with a note saying so.

CSV export and import

CSV on the toolbar has three choices.

• Export the whole table writes every row in row order.
• Export this view writes the rows the filters keep, in the order they are sorted.

The file starts with a _rid column, the row number (and _seq for a table that holds several entries per row), then every column by its name. Values are written as the grid shows them, including your unsaved edits, as UTF-8, which spreadsheets open with the text intact.

Import a CSV reads a file back and shows what it would do before it changes anything:

• each line is matched to a row by _rid (and _seq), and only cells that differ are changed;
• a line whose _rid continues the table from its last row adds a new row;
• lines that match no row, columns the table does not have, and locked columns are listed and left alone;
• a cell that breaks the column's rule, or that the server's own checks refuse, is listed. On a row the table already has, that whole row is skipped and the other rows still change;
• new rows are added in order and stop at the first one that has a refused cell. The new rows before it are added. That row and every new row after it are not imported, and the preview says which row stopped the import and why. This keeps the row numbers in your file matching the rows in the table.

Apply as one edit records the rest as pending edits and new rows in a single undo step. If the table changes between the preview and Apply, Apply refuses and asks you to import again.