Writing a book on coding games for Playdate with Lua

brett · November 17, 2024, 3:57am

Hi there! I'm writing a book titled Make Games for Playdate with Lua that's about, you guessed it, coding games for Playdate in Lua using the Playdate SDK.

It's currently in Early Access. The first draft is complete. I'm refining and polishing it up. This is the book I wish I had when I started digging into making games with Playdate. I've written a couple of other technical programming books before, and I think the Playdate community would really benefit from having a comprehensive, beginner-focused book on how to get started.

Inside Playdate is absolutely an essential reference, but something a bit more guided will help get more people just started out into making games for Playdate.

You can get the book here:

There's a free sample available that includes the first three chapters!

Make Games for Playdate with Lua is primarily targeted at beginners with no experience writing code or making games. It covers the fundamental concepts of programming from functions to variables to tables to conditionals. If you're an experienced programmer looking to learn how to make games for Playdate, you'll fly through the book and find the examples of how to use the Playdate SDK helpful.

In each chapter you'll code a different small game, learning new concepts that build upon that last chapter. Throughout the chapters there are Bonus suggestions that encourage you to experiment and learn on your own.

All of the source is available on GitHub, broken down by section in each chapter:

Introduction — get yourself and your computer ready for making games for Playdate
Hello, Playdate! — display text and move it around the screen
Tennis — make a simple single-player Pong clone that uses the crank to move the paddle
Clock — coding a simple clock app
Snake — homage to the Nokia classic
Soaring — crank-powered infinite flying game
Sokoban — with level parsing from text files
Dungeon Crawler — making a turn-based RPG where you progress through dungeon floors
Playdate by Example — focused examples on how to use various parts of the SDK

Topics covered:

Drawing text
Drawing shapes
Game loop
Screen positioning
Variables
Tables
Conditionals
Playing sounds with the MIDI synth
Player input with buttons and crank
Functions
Refactoring code
Save data
Adding a Playdate menu option
Parsing and rendering custom levels
Scene switching
Menus
Organizing code into multiple files
Loading maps from Tiled
Turn-based combat

Bonus

Here are games from the book that I've polished up and released separately as reference:

What's Next

Polish up the book and get the final draft published!

If Make Games for Playdate with Lua is received well and there's interest, I'd like to record video versions of the chapters and explore making a print edition. Let me know what you'd like to see! Are there any specific topics you'd like to see covered or styles of game that'd be helpful to have explained in depth?

Feel free to report any issues here. Thank you!

brett · November 18, 2024, 2:21pm

Yesterday I added and published a new chapter in the book called Clock that goes over how to read the time from the system, respect user preferences for 24-Hour Time display, get battery percentage, and use a custom font!

I also figured out how to get nice looking gifs made using MP4 recording from the Simulator then converting with Gifski. Here's the crank-controlled paddle version of Tennis from chapter 2.

Playdate Tennis Demo

Next up is adding a chapter on coding Snake from scratch, including high score tracking (and reseting), scenes like main menu, and setting custom metadata for the game.

brett · November 19, 2024, 2:11am

The book has sold 6 copies in the first day of being on sale in Early Access. It's been neat seeing people being excited. I appreciate the support. I'll be as transparent as I can about the statistics and process of publishing the book alongside actually writing it.

My goal is to sell 100 copies within the first six months of it being available. I think that seems realistic!

Made good progress on the Snake chapter this evening. It reminds me how much fun Snake is to play while also being really beginner-friendly to make.

pepsiman · November 21, 2024, 5:09pm

Hey there! Looking forward impatiently for it to be released, I'd be the first one (or one of the first ones if I don't get to the correct timing heh) in buying it no doubt! Keep up the good work man, I'll stay tuned!

brett · November 24, 2024, 3:32pm

Thanks so much for your support!

Got some updates from about a week into the book being released in Early Access!

I just published a new version where I finished the first draft of the Snake chapter. Still a ton of fun to play. The new chapter covers a lot of topics: saving and loading high-score from the console, adding a menu option, advanced logic, loops, and working with nil.

Here's Snake in its minimalist glory:

Snake Demo

It was so easy to add a menu option to reset the high-score. The Playdate SDK being so friendly and simple really makes writing tutorials a joy.

Sales Update: The book has sold 26 copies so far. I wasn't expecting much at this point, so I am surprised and thrilled. It's been really motivating to see people excited about the book and supporting it. The feedback from r/PlaydateConsole and r/PlaydateDevelopers has been great.

Next up is Flappy Crank!

brett · December 16, 2024, 2:56am

I just released a new version of the book in Early Access with a chapter where we make a game called Soaring. You control a bird by turning the crank (or pressing up and down), avoiding trees.

I started to code Flappy Crank (a Flappy Bird clone), but it just wasn't clicking or feeling good with the crank. But it led me to this idea for a game where you're a bird soaring through sky, which I think ultimately served the book better as I was able to explain how to make an infinite runner and introduce some new key concepts.

Soaring Demo

The new chapter introduces a few new key concepts:

Scenes and switching between them; e.g. main menu, gameplay, and game over
Breaking up code into multiple files
Relying less on global variables
Showing the crank indicator if the crank is docked

Next up is making Mini Survivors—a simple action game inspired by Vampire Survivors. I want to tie together the concepts so far into a fun and more polished game. After that, it's on to drawing sprites and digging into some more advanced topics.

Sales update: The book has sold 32 copies so far.

bbyford · December 21, 2024, 2:31pm

Bought, thanks @brett !

brett · February 19, 2025, 3:09am

Back at it with working on the book after taking a bit of a break.

The latest addition in the update I just published is a new chapter titled Playdate by Example which contains concise examples on how to use the SDK. Lots of programming languages and libraries have a Learn X by Example site (or page), and I find that to be extremely helpful. Here's an example of a section from that chapter:

Audio

Play a Sound Effect from WAV File

Given you have a sound effect file apple.wav in the sounds folder, it can be played it like this:

local sfxApple <const> = playdate.sound.sampleplayer.new("sounds/apple.wav")

function eatApple()
    sfxApple:play()
    -- other stuff happens too
end

Creating a Sound Effect Table Module

A slighty more advanced way of working with sound effects is to create an sfx table in sfx.lua that contains a play method and the various sampleplayers:

sfx = {}

sfx.apple = playdate.sound.sampleplayer.new("sounds/apple.wav")
sfx.death = playdate.sound.sampleplayer.new("sounds/death.wav")

sfx.apple:setVolume(0.5)
sfx.death:setVolume(0.5)

sfx.play = function(sound)
	if sound == nil then
		print("ERROR: nil sound provided")
		return
	end

	-- optionally check whether or not sound effects should be played (if you have a global settings.playSfx value)
	if settings.playSfx then
		sound:play()
	end
end

-- then call it
sfx.play(sfx.death)

function eatApple()
	sfx.play(sfx.apple)
end

This approach is more resilient because of a few reasons:

Logic can be added for whether the sound effect should be played.
If you pass in a sound effect that doesn't exist, you can print an error to the console.
You can use sfx anywhere throughout your game code, keeping all of the sampleplayer creation in one spot.

I also added a Style Guide chapter that I've been using for my own projects, largely inspired by what's in the Playdate SDK. I hope to continue to expand upon that further and publish it separately from the book.

The book is at 54 sales so far.

brett · August 10, 2025, 6:49pm

After about a 6 month break due to personal reasons (being overwhelmed with young children and a new-ish job), I've picked back up on the book! Here's the latest update I sent to purchasers:

I added most of a new work-in-progress chapter where we make Sokoban, a box-pushing puzzle game. It's unedited, but I thought best to send some sort of pulse for this project!

See the source for each section here:

I was originally going to do a chapter making a game like Vampire Survivors, but I wasn't excited about it, and the Sokoban chapter is perfect foundations for the last quarter of the book.

Thank you everyone for your support and patience between updates. It's been six months since I last published a new version. I'm in a good groove right now, working on it during a dedicated time weekly. I started writing this book when my son was born, and having two little kids growing up is far more challenging than I could have imagined. I appreciate your patience.

I'm going to finish the Sokoban chapter (parsing levels and rendering sprites). Then the final 25% of the book will be dedicated to building a dungeon crawler RPG. That's something I'm genuinely excited about, and it'll be a nice capstone project for the book.

Once the first draft is complete, I'll edit the book and refine it. Then explore print if anyone's interested.

One aspect on my mind is AI... When I started writing this book, I was quite uninterested in using AI for programming. But in the months since, especially by using AI Agents at work, I find myself wondering if anyone's interested in even just a section in the book on how to effectively plan and guide AI Agents for Playdate game programming. Let me know if you have any feedback on this, as I've done some exploring with promising results.

But also on this note, the book and project code is written entirely without AI, as it's more fun for me and what I want to do.

If you have any questions or feedback, let me know! Thanks again.

RustySabre · August 11, 2025, 8:32pm

First, I completely get it. I have three children myself (which I know many consider child's play - sorry, I had to), and trying to raise kids, work a full time job AND do something on the side is quite the challenge.

I'm a bit sad to hear that the Vampire Saviors section wasn't working for you, mainly because I'm a huge fan of that game, but I love a good dungeon crawler as well, so I'm good either way.

Not sure how I feel about the AI thing. I keep telling myself I need to get into it, because I am, after all, an IT guy, but the thought just gives me the willies. I mean I do use ChatGPT - barely - but otherwise I've tried to avoid it to this point. Maybe this would be what would finally get me into it!

thenoble1 · September 6, 2025, 3:36pm

Just wanted to thank you for writing this book. I have minimal coding experience (well I've been doing it a long time but at very basic levels and quite off-and-on) and your book has gone a long way to demystifying this cute little yellow handheld!

brett · September 7, 2025, 8:05pm

Thank you for this feedback! I’ll consider returning to it, maybe as an “Expansion Pack” to the book once I get the initial version complete.

Thank you so much!

I just published a new version of the book on Leanpub and itch.io with the complete Sokoban chapter. I also fixed some typos throughout the book.

Playdate Book - Sokoban

I’m really proud of the Sokoban chapter for a few reasons: it’s the first time readers get to do some game design! The code is not overly complex, but it contains everything a non-trivial game has: level loading, a form of scoring, and a main menu. Building blocks that I hope people can use for pursuing their own games.

The levels are defined in multi-line strings that then get parsed and rendered:

local levels <const> = {
    [[
    #####
    #@BT#
    #####
    ]],
    [[
    #######
    #     #
    #     #
    #@B#T #
    #  ####
    ]]
}

Where @ is the player, B is a box, T is a target spot, and # is a wall.

Next up is the Dungeon Crawler three chapter special. I’m excited for this, as it’ll be a good jumping off point for anyone interested in making an RPG for Playdate. The book is 153 pages now, and I’m thinking it’ll settle in at around 200 pages when all is said and done.

The Dungeon Crawler game will build upon everything in the book so far, dig into rendering sprites, developing a combat system, and more.

I’ve found my rhythm writing it. I go to a cafe every Sunday for a few hours and hack away at it. Having fun and enjoying the process, which is really important to me.

ElisavBizau · September 23, 2025, 5:45am

Bought! Super hyped to start going through it. Haven’t done any Playdate programming since 2023 and this book is great to get back into things. Excited something like this exists. Big ups man <3 ^^

brett · November 12, 2025, 4:01pm

I just published an update to the book adding a new chapter: Dungeon Crawler - Part 1! It covers rendering maps from Tiled, collision detection, and talking to non-player characters.

Playdate Book Dungeon Crawler Part 1

I just published the update on Leanpub and itch.

Here’s the source code for the new chapter: playdatebook/c7-dungeonCrawler at main · brettchalupa/playdatebook · GitHub

The next chapter, Dungeon Crawler - Part 2, will cover exploring multiple levels and engaging enemies in combat. I took this week off from work to focus on writing the book, so I’m hoping to continue to make good progress.

N0P3 · January 14, 2026, 3:01am

I just bought this book. Thank you so much for your hard work!

AmorBielyi · January 22, 2026, 3:20pm

Thank you so much for this book, @brett ! and a special thank you for making it open source even not all chapters for obvious reason!

wampa · February 24, 2026, 2:52pm

I would personally love some book space devoted to AI/agents!

I spent a lot of time coding in college (was one class away from getting a CS minor ) but haven’t done much in terms of coding over the last ~decade apart from tiny Python projects. I used to LOVE doing Ludum Dares & other gamejams every chance I got.

AI has largely given me back that joy. Ideas that I’ve shelved because they’d take weeks/months of weekend-time to get to a barely-playable stage can now be playable prototypes in a single weekend.

I love making art, writing, storytelling, & occasionally making music. A few of those things, I’m even lucky enough to get to do for a living.

I don’t love coding. (I mean, it’s fun to an extent, as a mental exercise. Less fun when my incompetance means it’s possible I never finish what I start, even with ample hair pulling.)

But, I need that coding capability to package together the things I enjoy most.

Now, that’s less true, thankfully.

I don’t have the time or energy to (re-learn to) code, so I’m super thankful AI can step in and handle much of the process, even if it’s in a suboptimal, unoptimized way. I’m making little goofy things for myself, so I see no harm in using AI. If I was working at Amazon and was using AI agents that had the ability to shut off AWS for 13 hours or so, I would certainly think harder about how & where to utilize it…

That said, I also want to have a deeper understanding of Playdate gamedev and refresh my long-gone Lua familiarity, which is what led me to find your original post!

My previous, dusty knowledge may enable me to query AI more effectively than a complete newcomer to coding, but I have a lot to learn in this area still, which would make a chapter written by an expert very helpful.

I know AI can make gamedev a feasible hobby for me again, but I’m figuring out how to best utilize it. AI lacks humanity/creativity, so its unguided design choices basically all suck compared to a decent human’s, but sometimes automated mediocrity suffices, especially when it enables me to spend more time on things I enjoy more + am better at…

But that’s tertiary to the primary thing I want to get out of your book, however: a solid enough understanding to be able to actually debug & understand what AI codes for/with me.

I know much of that background context wasn’t entirely relevant, but maybe it helps provide some info on who is in your audience, plus potentially explains (for some anti-AI/on-the-fence-about-AI people) how AI can be leveraged in a way that doesn’t contribute to the erosion of brain cells and/or society.

Ironically, thanks for writing the book without the use of AI! That may sound contradictory, but I don’t actually think it is!

Long live human creativity/agency.

Looking forward to digging into the book this weekend!

(Now if I can just figure out how to use an IDE, because I’ve only ever used VIM )

brett · March 24, 2026, 1:51pm

I totally hear where you're coming from Wampa! Using AI to help learn and do something that otherwise felt impossible is a really interesting application of it. I still haven't decided if I'll add a chapter specifically about using AI to help with Playdate Lua dev, as I go back and forth on whether it's appropriate for the book (like does the capability of AI make my book less necessary then? that makes me a bit sad to think about). But I can at least share some thoughts on it here that could help!

If you're using an agentic tool like Claude Code or Cursor or an open one like Ollama, a good starting point is to point it to the Inside Playdate.html that comes with the SDK and ask it to summarize it into a Markdown file (like PLAYDATE.md) for easy reference. It's a large document by default, but summarizing it helps agents quickly reference it without using a ton of tokens. If you're stuck or confused, the AI will reference it and know the SDK pretty well and can help get you unstuck.

I've found AI to be particularly helpful for reviewing code after I write it. It's the best of both worlds—I get to have the fun and creativity of coding and it helps me catch bugs and mistakes sooner. Using git to track your code also helps make it easier to work in smaller chunks.

Much like you, I enjoy experimenting and trying things out while I figure out how to best use (or not use) a tool. I've done quite a bit of experiments with AI and Playdate dev, and it's so fast and capable that it's a bit frightening to me. But something I realized is that 1) programming is fun for me and that's reason enough for me to do it, as this is all a hobby for me 2) when AI writes the code, I feel less connected to the project and ultimately then care less, it feels more disposable 3) coding is creative, especially for games! I get ideas while writing code that I otherwise wouldn't if an agent wrote it. So I've decided to not use AI to code my game projects.

So, I guess, with all that being said, I hope some of that was helpful.

I continue to work on the book! The finish line is in sight. Unfortunately my family and I were sick a lot this winter, so progress was slow. I'm on a little side quest to make a free dungeon crawler roguelike for Playdate called Enigmata so that I can apply some of the learnings to the final project in the book. I hope to have some new updates on the book in the coming weeks!

brett · April 10, 2026, 3:32pm

I'm so pleased to share that the first draft of the book is complete! I just added the final chapter, Dungeon Crawler - Part 2 where we build out a turn-based JRPG like Dragon Quest or Final Fantasy with map exploration, NPCs, and combat.

Playdate Book Dungeon Crawler Preview

It's been a wild 18 months for me to get to this point. I had various starts and stops, and I'm really proud to have the first draft complete. I can see the finish line! I just need to refine and revise, fix typos, incorporate feedback I've gotten. I really appreciate all of the support for the book. The book has sold 148 copies so far. When I started writing it, I had no idea what would come from it. I was just having fun and learning the Playdate SDK.

Just a reminder of some key links:

There's a free sample/demo of the book available on both Leanpub and itch.io
You can find all of the source code for each game on GitHub for free

My next immediate steps are to proofread and revise. I'm going to add some illustrations to explain parts I think would benefit from that. And just try to make sure everything in the book makes sense.

A question: would people be interested in a print version of the book? If there's interest, I'm considering either doing print on demand or doing a limited run high-quality print version. It'd be dependent on interest and cost. Let me know!