Mikey of Legend

Week 10: Data-Driven Design in Godot

Learning objectives: Externalize all balance-relevant data using Godot custom Resources for fast, code-free iteration.

Estimated time: 7-9 hours

Signed in as loading...

Checking purchase access...

Previous Course overview Next

Introduction

Move tuning data out of scripts and into Resources so balancing can happen quickly and safely without code edits.

Lesson breakdown

  • Lesson 1: Custom Resource Modeling - Define data classes for enemies, upgrades, and probability systems with clear editable fields.
  • Lesson 2: Runtime Resource Wiring - Refactor shared scripts to consume Resource values so one behavior supports many data variants.
  • Lesson 3: Spreadsheet and Resource Sync - Keep spreadsheets as source modeling layer while applying final values through .tres data files.
  • Lesson 4: Integration and testing pass for this week scope.
  • Lesson 5: Final polish and handoff notes for next week.

Try this now

  • Complete one focused implementation pass before watching the next segment.
  • Capture a before and after snapshot for the system you changed.
  • Write one short note on what to tune in your next iteration.

How this week works

Move tuning data out of scripts and into Resources so balancing can happen quickly and safely without code edits.

Video segment plan

Work in short focused segments, then pause to apply each concept directly in your project, spreadsheet, or design document.

Worksheet and evidence capture

Record diagrams, tuning notes, and before-after decisions as you go so each week produces usable implementation evidence.

Interactive lesson parts (6-10 min each)

Part 1: Custom Resource Modeling

Watch Build Check
7 min Part video
Video part 1: Custom Resource Modeling

Keep this segment short and complete the practice action before continuing.

Define data classes for enemies, upgrades, and probability systems with clear editable fields.

Part 2: Runtime Resource Wiring

Watch Build Check
8 min Part video
Video part 2: Runtime Resource Wiring

Apply the method in your build or design artifact and capture what changed.

Refactor shared scripts to consume Resource values so one behavior supports many data variants.

Part 3: Spreadsheet and Resource Sync

Watch Build Check
9 min Part video
Video part 3: Spreadsheet and Resource Sync

Finish with validation and a concrete next-step decision.

Keep spreadsheets as source modeling layer while applying final values through .tres data files.

Hands-on milestone

  • Define Resource types for major balance data categories.
  • Create .tres instances for active mechanics and upgrades.
  • Demonstrate a balance retune done only through Resource edits.

Code checkpoint

Use this short checkpoint marker when your weekly implementation pass is complete.

Practice snippet GDScript 
# Step checkpoint for Week 10: Data-Driven Design in Godot
func _ready() -> void:
    print("Checkpoint complete for this week")