This schema documents the structure of game data files used in Utopia Fleet Builder. All data is stored as JavaScript module exports containing arrays of card objects.
Overview
The Utopia data model consists of several card types, each with specific fields and structure:- Ships - Starship cards with stats and abilities
- Captains - Captain cards with skill and abilities
- Admirals - Admiral cards with fleet-wide effects
- Ambassadors - Ambassador cards with diplomatic negotiation mechanics
- Upgrades - Upgrade cards (weapons, tech, crew, elite talents)
- Resources - Fleet-wide resource cards
- Missions - Scenario and mission definitions
- Others - Special cards and tokens
Common Fields
All card types share these base fields:Card type identifier:
"ship", "captain", "admiral", "ambassador", "upgrade", "resource", "mission", etc.Unique identifier for the card (e.g.,
"S415", "Cap053", "A044")Game identifier (always 1 for Star Trek Attack Wing)
Array of set identifiers this card belongs to (e.g.,
["75016"], ["OP1Participation2"])Display name of the card
URL to card image (typically imgur links)
Whether this is a unique card (only one allowed per fleet)
Array of faction strings:
"federation", "klingon", "romulan", "dominion", "borg", "independent", etc.Squadron point cost of the card
Card ability text with HTML formatting and special image tags for icons
Ship Cards
- Required Fields
- Optional Fields
- Example
Always
"ship"Ship class name (e.g.,
"Sovereign Class", "Galaxy Class")Primary weapon attack dice
Base agility (defense dice)
Hull points
Shield points
Array of action types available:
"evade""target-lock""scan""battlestations""cloak""sensor-echo""regenerate"
Array of upgrade slot types:
"tech""weapon""crew""talent""borg""squadron"
Captain Cards
- Required Fields
- Optional Fields
- Example
Admiral Cards
- Required Fields
- Optional Fields
- Example
Ambassador Cards
Ambassadors are diplomatic cards that offer negotiation mechanics with two possible outcomes.- Required Fields
- Optional Fields
- Example
Upgrade Cards
Upgrade cards have different subtypes:tech, weapon, crew, talent, borg, squadron, question
- Tech Upgrades
- Weapon Upgrades
- Crew Upgrades
- Elite Talents
Special Upgrade Fields
Upgrades may have additional constraint fields:Only one copy allowed per ship
Requires Federation ship
Additional cost for Federation ships (e.g.,
"+1")Limited to Sovereign class ships
Hull requirement (e.g.,
"4+", "5+")Resource Cards
- Structure
- Example
Mission Cards
- Structure
- Example
Always
"mission"Array of mission set identifiers
Unique mission identifier
Components required (note: typo in source - “Componets”)
Mission narrative and background
Setup instructions including point limits and requirements
Special rules for the mission
Victory conditions and objectives
Other Card Types
Token Cards
Token Cards
Special game tokens and rules references:
Question Cards
Question Cards
Special utility cards for fleet building:
Text Formatting
Card text uses HTML and special image tags:Data File Structure
All data files follow this pattern:Available Data Files
ships.js
All ship cards with stats and abilities
captains.js
Captain cards with skills and talents
admirals.js
Admiral cards with fleet abilities
ambassadors.js
Ambassador cards with negotiation mechanics
upgrades.js
All upgrade cards (tech, weapon, crew, talents)
resources.js
Fleet resource cards
missions.js
Mission scenarios and objectives
others.js
Special tokens and rules cards
sets.js
Set and expansion definitions
ship_classes.js
Ship class definitions and groupings
missionSets.js
Mission set collections
starship_construction.js
Starship construction rules and cards
rulings.js
Official game rulings and clarifications
Validation Rules
When working with this data:Required Fields - All cards must have
type, id, name, and costUnique IDs - Card IDs must be unique across all cards of same type
Valid Types - Type must be one of the documented card types
Faction Arrays - Factions must be arrays, even for single faction
Numeric Fields - Stats (attack, agility, etc.) must be numbers
Usage Examples
Related Documentation
FAQ
Frequently asked questions
Rulings
Official game rulings and clarifications