Render and output products for manufacturing

Once you have completed your game in Forgefire, it is time to harvest the fruits of your labor: final rendering and output of files for manufacturing.

“Forging” is the process of rendering your data into final high-resolution manufacturing-ready output. Forgefire has many powerful options for this step of the publishing process.

File output requires a Blueprint…

To forge your output in Forgefire, you must first create a Forgefire Blueprint which defines the desired type of output, such as the selection of cards (i.e. the deck) and which scripts, if any, need to be applied to either cards or deck during forging.

  • Blueprints may be forged any number of times, which would be the case when you want randomized or procedurally created decks

  • Output formats range from manufacturing-ready PDF’s, InDesign Files, to JSON files. Additional output formats, such as Tabletop Simulator-compatible files, are in the pipeline

…and the fire

Once a Blueprint has been defined, it may be Forged any number of times. Forging is the processor-intense operation of collecting all your data elements and rendering them in high-resolution from your defined templates into cards and then a deck of cards.

Each time a Blueprint is forged, it will trigger any associated scripts relating to the related cards or the deck, for final output. Scripts can range from executing very simple parameters (such as picking random cards from rarity card pools), to very advanced behaviors.

  • Forgefire comes with a scalable processing solutions for high volume forging

  • Support for multi-plate outputs (for spot-colors, black-plate replacement, and card foiling) is in the pipeline

Amazed?

Forgefire is an expansive and powerful game development tool with myriad options. Our team would be happy to provide a demonstration of the tool to you and your colleagues.