Google Sheets for game designers on Mac: balancing stats, economy and progression in 2026

Most game designers who use Google Sheets do one of three jobs. They balance an economy, tune stats for a set of items or units, or lay out a progression curve for levels or experience points. All three need the same habits: clean inputs, named bounds, and formulas you can check by eye.

The most detailed public write-up of this method is a Game Developer article on economy balancing. It describes one row per object, a globals table, and normalized columns. That article uses Microsoft Excel and never mentions Google Sheets. So the Sheets steps below translate the ideas. They are not a copy of the article's workflow.

Set up one row per item and a Globals tab

Put one item on each row. A weapon, a unit, a potion, or a level gets its own row, and each property gets its own column. Keep a second tab called Globals for numbers that apply to the whole game. Examples are the cheapest and most expensive cost you allow, or the largest reward a player can earn.

The article gives a clear reason for this split. It lowers a weapon's maximum cost from 90,000 to 50,000 because players can only collect 50,000 coins. The bound follows what a player can actually earn. Write that reason in the Globals tab next to the number, so the next person knows why it is set.

• Freeze the header row so the headers stay visible. The freeze top row guide walks through it.
• Put the item name in column A, so every row has a label you can search.
• Keep one Globals tab. Do not type the same bound into many formulas.
• Add a Notes column at the far right for the reason behind each change.
• Use a dropdown for categories like weapon or potion, so spelling stays consistent. The dropdown guide shows the steps.

Name your bounds with named ranges

A named range gives a cell or a block of cells a readable name. Instead of pointing at Globals!B4 in every formula, you point at CostMin. Select the cell in Globals, then open Data > Named ranges and add it with a name. Names cannot contain spaces. CostMin and Cost_Min both work.

Named ranges make formulas easier to read a week later. Compare =(B2-Globals!B4)/(Globals!B5-Globals!B4) with =(B2-CostMin)/(CostMax-CostMin). The second line says what it does. The first line makes you remember which tab and cell hold each bound.

Normalize to 0 to 1 before you weight anything

Weighted averages only work when each input sits on the same scale. A cost in the tens of thousands and a damage value in the tens cannot be averaged fairly. Turn each value into a number between 0 and 1 first. The article describes this as a normalization column for each relevant value.

For a cost in column B, use =(B2-CostMin)/(CostMax-CostMin). The lowest allowed cost returns 0. The highest allowed cost returns 1. Costs in between land somewhere along the scale, so you can compare a cost with a damage value.

Watch for edge cases. A value outside the bounds returns a result below 0 or above 1. That result is a signal. Either the item breaks your bounds, or the bound is wrong. Decide which one, then fix the one that is wrong. Do not wrap the result in MIN and MAX to hide the warning.

Store the weights in cells too. Put each weight on the Globals tab and name it, such as W_Cost. Then a weighted mean looks like =(C2*W_Cost+D2*W_Damage)/(W_Cost+W_Damage). Change one weight, and every row updates. You never have to edit a formula to tune the game.

Color code inputs, curves, and formulas

The article uses three header colors. Green marks values you type by hand. Yellow marks columns that hold distribution curves. White marks formula outputs. The rule behind the colors is simple. Formula columns should change only as a last resort.

• Green header: typed values. These are the only cells you change during a normal tuning pass.
• Yellow header: curve or distribution values. Expect to edit these often, and test each change.
• White header: formulas. Treat them as read-only until a rule changes.
• Format > Conditional formatting: flag any normalized cell that falls below 0 or above 1.

To color a header, select it and use the fill color button in the toolbar. Paint format copies the look to other headers of the same type. Use the same three colors every time, so anyone who opens the file can read it at a glance.

Mac keyboard shortcuts for balancing sheets

Google publishes its own list of Mac shortcuts for Sheets. Most balancing work uses a handful of them. On a Mac, menus open with Control and Option held together, then a letter. For example, Ctrl+Option+D opens the Data menu.

Ctrl+Space selects a column in Sheets. It is not the Command key. On a default Mac, Command+Space opens Spotlight, so the Control key matters here. Many people press the wrong key once, then assume Sheets is broken. Check the key before you retry.

Charts and distributions in Google Sheets

Sheets now creates box-and-whisker charts natively. Google's October 2026 Workspace update says the chart includes quartile and outlier calculations. The Rapid Release rollout started October 22, 2026, and the Scheduled Release rollout started November 6, 2026. Check which release track your account uses before you plan around it.

Distribution curves are harder. The article calls adjusting them cumbersome, and says they can stump designers without balancing experience. A practical approach is to build the curve in a yellow column with plain formulas, then chart the output. You can change one number and watch the chart move.

To make a chart, select the data, then go to Insert > Chart. The chart guide covers the chart editor step by step. Chart the normalized values as well as the raw ones, so you can see when a scale is off.

Limits to plan for before a sheet gets big

Google Drive's help page says Sheets supports up to 20 million cells or 100MB for a spreadsheet. The page does not say whether that cap covers every tab. Some third-party guides still say 10 million. Treat Google's page as the reference when you plan a large economy model.

Connected Sheets adds its own ceilings. Pivot tables built on a connected data source stop at 200k rows. Extracts stop at 500k rows or 5 million cells. Excel conversion removes any cell with more than 50,000 characters, so long notes in older files can disappear. Check long text before you convert an old workbook.

Scripts have limits too. Google's Apps Script quotas page sets a 6-minute maximum for each run, for consumer and Workspace accounts. Daily trigger time is 90 minutes on consumer accounts and 6 hours on Workspace. Fill with Gemini handles 3,000 cells per request, and only on plans that include it.

Mistakes game designers make in Google Sheets

• Typing a bound into a formula. Change it once in Globals, and every formula follows. Miss one, and the numbers quietly disagree.
• Weighting raw values. A large raw number wins the average. Normalize first.
• Dragging a formula down each column by hand. Select the target cells and press ⌘+D, then check the last row, since a range can end early.
• Forgetting the Excel conversion limit on old files. Check long text cells before you convert.
• Tuning with no record of the last good version. Save a named version before a big pass.

Version history is your undo for a whole session. Open File > Version history > See version history to compare earlier states with the current one. The revision history guide shows the steps in more detail.

Where Lazur fits while you stay in the sheet

Lazur runs next to Sheets. It is not a plugin, an add-in, or part of the file. Hold ⌥ ⌘, which means Option and Command together, and ask about anything on screen. Lazur answers out loud. Ask where something is, and it draws a circle and a label around it. Ask how to do something, and it guides you one click at a time, waiting for each click.

Lazur does not click for you. It does not edit your file or operate Sheets. You still type each formula, pick each cell, and make each change. That keeps the balance decisions in your hands, where they belong when a bound is tied to what players can earn.

Hold fn to dictate. Lazur types clean, formatted text at the cursor in any app. Use it for design notes in a comment or a Notes column. Snippets, a personal dictionary, and clipboard slots help with names you type often, like CostMin and W_Cost.

For research, Lazur runs searches in its own Chrome tabs through the Lazur for Chrome extension. It comes back with a summary and a report. Use that for a quick read on how other studios describe their curves, then check the sources yourself before you change a number.

Lazur listens and looks at the screen only while you hold the shortcut. Audio and the screenshot go to AI providers so they can answer, and they are not stored. Content is never used to train AI models. If your balance numbers sit under an NDA, check that against your studio's rules before you ask about them.

Next steps for your first balancing sheet

1. Build the Globals tab with only the bounds you can justify. Write the reason beside each one.
2. Name each bound with Data > Named ranges, then reference the names in your formulas.
3. Normalize one column and check one row by hand before you copy the formula down.
4. Color the headers green, yellow, and white, and add conditional formatting for values outside 0 to 1.
5. Check your file size and any Apps Script plans against the limits above, before the model grows.

When the setup works, save a named version, then start tuning. If you want Lazur beside you for the menus and the notes, get it from the download page. Pricing is on the pricing page.