WienerWiener
  • Introduction
  • Comparison
  • Pricing
  • FAQ
  • Use Cases
  • License
  • Unity Asset vs Standalone
  • Obfuscation & Tamper Detection
  • Mismatch Detection & Debug
  • Localization
  • Versioning
  • Google Sheets Input
  • Excel
  • YAML
  • Settings
  • Data Format
  • Convert
  • ValueOnly Format
  • Startup
  • Samples
  • Converter
  • YAML Editor
  • Setting Editor
  • 日本語
  • English
  • Introduction
  • Comparison
  • Pricing
  • FAQ
  • Use Cases
  • License
  • Unity Asset vs Standalone
  • Obfuscation & Tamper Detection
  • Mismatch Detection & Debug
  • Localization
  • Versioning
  • Google Sheets Input
  • Excel
  • YAML
  • Settings
  • Data Format
  • Convert
  • ValueOnly Format
  • Startup
  • Samples
  • Converter
  • YAML Editor
  • Setting Editor
  • 日本語
  • English
  • Samples

    • Samples
    • Convert the 2.2-Million-Cell Sample Data
    • Create the Item Master
    • Experience Hot Reload
    • Create the Unit Master
    • Create the Reward Master
    • Create the Equipment Master
    • Try Localization
    • Add Keys to Existing YAML

Samples

Overview

These samples walk through the Static Game Data creation flow.

What You Can Do in These Samples

Use sample data close to a real game development workflow to experience the Wiener conversion flow.

Prerequisite

  • Unity Startup - Install and import the Unity Asset version

Recommended Order

  1. Convert the 2.2-million-cell sample data (about 10 minutes) - Experience large-data conversion speed
  2. Create the item master (about 30 minutes) - Experience the basic conversion flow
  3. Experience hot reload (about 10 minutes) - Reconvert during Play Mode and reload with the R key
  4. Create the unit master and ID checks (about 15 minutes) - Experience validation and consistency checks
  5. Create the reward master (about 30 minutes) - Experience conditional ID validation
  6. Create the equipment master (about 20 minutes) - Add a reward target with multiple enums
  7. Try localization (about 15 minutes) - Output translation data and switch languages
  8. Add keys to existing YAML (about 10 minutes) - Add keys to existing Excel and YAML files

Try the validation flow

Intentionally enter an incorrect ID and run conversion to experience Wiener's error detection. Confirm that incorrect IDs entered by planners are caught during conversion.

Convert the 2.2-Million-Cell Sample Data - about 10 minutes

  • Replace the sample data and run conversion
  • Experience conversion time for large-scale data

Create the Item Master - about 30 minutes

  • Create Dictionary-format Static Game Data

Experience Hot Reload - about 10 minutes

  • Reconvert Static Game Data while Unity is playing
  • Reload basic.bytes with the R key and confirm the changes

Create the Unit Master - about 15 minutes

  • Check IDs with Validate.KeyExist
  • Create DictionaryList-format Static Game Data

Create the Reward Master - about 30 minutes

  • Validate IDs against different masters depending on reward type

Create the Equipment Master - about 20 minutes

  • Create an equipment master with rarity and equipment part enums
  • Add equipment as a reward target

Try Localization - about 15 minutes

  • Output translation data and enter Japanese translations
  • Switch languages from C# code

Add Keys to Existing YAML - about 10 minutes

  • Add keys to existing Excel and YAML files
  • Reference the added keys from C# code
Last Updated:: 6/16/26, 7:09 PM
Contributors: artisan-sawasaka
Next
Convert the 2.2-Million-Cell Sample Data