Server-side Output Use Cases

The currently sold Unity Asset version 1.0.0 can generate Json / PHP / SQL / CSV from the Converter inside the Unity Editor. These server-integration files can use the same input as Unity Binary / CSharp output and the reviewable Manual output.

Wiener generates files only. You must implement placement into APIs or databases, incremental rollout, client/server version checks, and post-deployment verification.

Coming Soon

Unity-independent command-line conversion in the Standalone version and UE5 C++ output are not currently sold. Do not treat them as current Unity Asset version 1.0.0 features.

Unity Asset Version 1.0.0 Output Scope

PurposeSelectable output formats
UnityBinary / CSharp
Server integrationJson / PHP / SQL / CSV
Reviewable documentationManual
UE5 C++Coming Soon (Standalone)

1. JSON Output — REST API / BFF

Use case: Game API server distributes Static Game Data as JSON

[
  {
    "id": 1,
    "name": "Heart Potion",
    "type": "Consume",
    "heal_point": 100,
    "price": 50
  }
]

Settings (YAML):

output_format:
- format: Json

Example: A BFF architecture where the frontend fetches Static Game Data from an API. Placement, caching, and version management for the generated JSON must be implemented separately.

2. PHP Output — PHP Server

Use case: PHP game API server needs to reference Static Game Data

The following is a simplified usage example. Actual class names, namespaces, and fields are generated from the input and YAML settings.

<?php
class ItemMaster {
    const DATA = [
        ['id' => 1, 'name' => 'Heart Potion', 'type' => 'Consume', 'heal_point' => 100, 'price' => 50],
        ['id' => 2, 'name' => 'Magic Shield', 'type' => 'Equipment', 'heal_point' => 0, 'price' => 200],
    ];
}

Settings:

output_format:
- format: PHP

Example: PHP server game logic references item effects and prices. Useful when you want to keep everything in files without a database.

3. SQL Output — DB Seed Data

Use case: Load Static Game Data into an RDB for server-side access

SQL output produces a CSV containing only the fields selected by YAML. Verify column mapping and import settings for the target database before loading it with LOAD DATA INFILE or other database import tooling.

id,name,type,heal_point,price
1,Heart Potion,Consume,100,50
2,Magic Shield,Equipment,0,200

Settings:

output_format:
- format: SQL

Example: Applying delta data to a DB during version updates. Automating Static Game Data seed injection.

Generating Client and Server Files from the Same Input

Excel / Google Sheets + YAML
  `-- Converter inside the Unity Editor
      +-- Binary (.bytes)              → Embed in Unity
      +-- C# classes (.cs)             → Type-safe access in Unity
      +-- JSON (.json)                 → Serve from API server
      +-- PHP (.php)                   → Reference from PHP server
      +-- SQL (.csv)                   → Load into DB
      +-- CSV (.csv)                   → Pass to custom server processing
      `-- Manual                       → Review generated content

Benefits:

  • Client and server-integration files can be generated from the same input
  • The same conversion can apply an update to every selected output format
  • The same validation workflow can run before distribution

Using the same source does not guarantee that deployed environments stay synchronized. Old files, partial deployments, or stale caches can create mismatches. Version generated artifacts and verify them after deployment.

→ Data Format Details　→ Unity Asset Converter

Last Updated::