Projects

Spreadsheet systems / Live workbook, version-bound

Mage's Survival Calculator

Mage's Survival Calculator exists to make build planning inspectable in a game system with many interacting spell, item, trait, passive, and stat values.

I built a live Google Sheets workbook and retained a local XLSX copy with named ranges, hidden support tabs, layered formulae, and workbook validation.

Mage's Survival Calculator backend worksheet showing staged stat columns for final values, sub-final values, percentage totals, item totals, passives, mage values, traits, base values, and custom inputs.
Backend worksheet view showing how final stat values are split across staged calculation columns.
Role
Sole developer
Focus
Spreadsheet modelling and calculation structure
Maturity
Live workbook, version-bound
Access
Limited public workbook
Technologies
  • Google Sheets
  • XLSX
Last reviewed
Jul 2026

The problem

What the project had to handle

The current constraint is version scope. The workbook reflects the captured game/system values it was built around, while active development paused after announced game reworks.

The workbook is presented as a version-bound spreadsheet systems project, not as an official calculator or current game-balance reference.

Key decisions

The shape of the build

Layer the formula model

Inputs, support tabs, named ranges, and final calculations are separated instead of packed into one unreadable sheet.

That makes the workbook easier to audit, update, and reason about when values change.

Keep a portable workbook copy

The Google Sheet is paired with a local XLSX copy and validation notes.

The calculator can remain inspectable even while active development is paused.

How it works

End-to-end flow

Editable inputs, named ranges, support tabs, and formula layers produce build comparison outputs in the live workbook while the local XLSX copy keeps the model inspectable.

Spreadsheet model

Traits
Formulae
Builds

Mage's Survival Calculator

Layered game systems modelled as editable calculations.

Inputs, named ranges, support tabs, formulae, and build comparison outputs.

What I implemented

The working surface

Spreadsheet model

  • Built a live Google Sheets workbook for builds, spells, items, passives, and stat outcomes.
  • Used named ranges and support tabs to organise the calculation layers.
  • Separated editable inputs from support data and final stat outputs.

Portable workbook copy

  • Kept a local XLSX copy so the model remains inspectable outside Google Sheets.
  • Checked that the workbook structure and formula model remained intact.
  • Audited 5,043 formula elements within the version-bound workbook.

Validation

Checks and evidence

Live workbook available

The public Google Sheets workbook can be opened and inspected directly.

Portable copy retained

A local XLSX copy keeps the formula model inspectable outside Google Sheets.

Formula structure checked

Validation inspected 5,043 formula elements across the version-bound workbook.

Current state

Live, version-bound workbook based on the captured game-system values.

Development paused after later game changes altered the underlying model.

It is not presented as a current game-balance reference beyond the recorded version.