Artikel mit Tag "pipeline"

Re-exporting by hand after every balance tweak is a habit it's too easy to skip. Auto-export watches your collection, regenerates the files on save, and the exported JSON is the exact file your Godot scene loads

The engine and the team need the cards data shaped differently than the editor shows it. A custom export format picks the data, the structure and a post-processing script so every consumer gets files they can load as-is

Scrolling finds you the top of the list, not the answer. Filter expressions narrow the collection by what the values mean - a field, a comparison, a range - and combine into saved queries that find the problem cards instantly

A damage pass and a cost review want different columns from the same grid. A view saves the arrangement - type of display, columns, sort and filter - so each job opens its own layout of the data instantly

Forget about routine balancing. The collection transfers all the data into a single table: one row - one map. Make any changes and apply them to the entire pack of cards in just one save.