Go to file
Sage Vaillancourt 5c45b7bba0 Add box score and transitions
Add constants defining the top of the outfield wall (not used yet)
Take scores out of mutable global state (that might be just about all of it sewn up)
Finish switching batttingTeam to a TeamId value
2025-02-17 13:21:28 -05:00
lib Add LuaPreprocess for asset-processing. 2025-02-08 01:53:26 -05:00
src Add box score and transitions 2025-02-17 13:21:28 -05:00
.gitignore Start up some simple baserunning. 2025-01-26 21:34:19 -05:00
.luacheckrc Add .luacheckrc, remove selene.toml 2025-02-16 18:43:09 -05:00
.luarc.json Add music + sound effects to assets.lua2p 2025-02-08 09:39:56 -05:00
.styluaignore Fix linting 2025-02-09 14:47:37 -05:00
Makefile selene -> luacheck 2025-02-16 15:14:59 -05:00
README.md Backfill with <const> 2025-02-01 17:45:10 -05:00
__stub.ext.lua Queue up announcement messages. 2025-02-02 17:36:25 -05:00

README.md

Batter Up!

Style Guide

This project uses StyLua for linting, and Selene for various other checks.

In addition to using <const>, where applicable, PascalCase is used for any values which should never be mutated, including any elements in a table.

E.g.

local Screen <const> = { x = 400, y = 240 }

should be treated the same as

local ScreenX <const> = 400
local ScreenY <const> = 240

Though the compiler will not enforce this. Furthermore, PascalCase is also used for values that may mutate themselves through method calls. For example, instances of playdate.graphics.animator. The one exception is gfx

N.b. Selene does not understand <const>, so make check uses a sed hack to filter them out.

camelCase tables may be <const>, but can still have mutable fields.