Writing and validating your data with CastleDB
Our Ingame Database
Our Ingame Entities
A long list of static (read-only) definitions that always exist in the game:
Everything (ish) that is spawned in the game is an entity
Similar to Unity Prefabs.
Our
Data
Format
Problem #1: References!
Database references
Does the recipe need or produce an item that doesn’t exist?
Entity references
Is there no corresponding entity to an item or location?
Image references
Do we have all the icons and other images we refer to?
Localization
Do we have proper translation entries for everything in the database?
Problem #2: Typos and copy-paste errors!
Problem #3: Not super nice for non-techies
Problem #4: Hard to overlook
Can only fit 3-6 entries on screen
CastleDB
JSON based
Version control friendly!
Human readable!
Easily parsable!
Getting started
Many different types
References
Multiple items per field
Add some massage
Output:
Friendly
log
Can run in watch mode
File output, prettily formatted
Reference validation with clear error messages
Disabled invalid data:
WIP toggle
Entity
file
generation
Schema definition
The bad?
Columns are equal width!
It’s written in javascript/haxe/node.js (I think)
(only bad if you aren’t familiar with it… like me!)
No in-editor validation
100%
Done
Questions?