LÖVE Game Development & Automated Build System

Turn your LÖVE game ideas into polished multi-platform releases with this powerful template! Featuring professional IDE integration, automated builds, and everything you need to go from prototype to published game. Built for LÖVE 💕

• 🛑 Don't fork this repository directly!
• 🟢 Create a new repository from this template for your game.

Features

• 🗂️ Organized with Workspaces
  • 🌕 Rich Lua language features with Lua Helper
    • Superior, high-performance, cross-platform compatible Language Server Protocol for Lua. And so much more.
    • .luarc.json is included for people wanting to use Lua Language Server
  • 🩷 Intellisense for the LÖVE API
  • 🐛 Debugging with Second Local Lua Debugger
    • A maintained fork of the original Local Lua Debugger
  • 🎑 Deterministic Lua code formatting with StyLua
  • 👨‍💻 Consistent coding styles with Editorconfig
  • ️⛱️ Shader languages support
  • 🐙 GitHub Local Actions
  • ️👷 Automated builds of the .love file from within the IDE
• 📦 GitHub Actions for automated builds - compatible with act
  • 🤖 Android (.aab and .apk)
  • 📱 iOS (.ipa)
  • 🌐 HTML5
  • 🐧 Linux (.AppImage and tarball)
  • 🍏 macOS (App bundle and .dmg Disk Image)
  • 🪟 Windows (Installer, SFX .exe and .zip)
  • 🔐 lua-https built-in to LÖVE 11.5
  • ⤴️ Automatic publishing to itch.io
• ️⚙️ Shared product configuration between the game and the GitHub Actions
• 🎮 SteamOS DevKit integration
• 📊 Integrated performance metrics overlay
• ️❄️ Nix flake to provision a dev shell

Prerequisites

• Visual Studio Code or VSCodium
• LÖVE 11.5 (currently only 11.5 is supported)
  • love should be in your PATH
• bash
• 7z
• miniserve (optional ️for local testing of HTML builds)

Platform Support

• The Store column indicates which store front the artifact is best suited for.
• The lua-https column indicates if supplemental HTTPS support is included with LÖVE 11.5 builds
  • The .love file includes https native libraries for supported platforms, see USAGE.md for more details.

Quick Start

• Don't fork this repository directly!
• Create a new repository from this template for your game, then clone that repository.
• Open the Workspace.code-workspace file with Visual Studio Code or VSCodium
  • You will be prompted that there are recommended extensions.
    • Click 'Install'
• Remove our example "game" by:
  • Rename game/main.template.lua to game/main.lua.
  • Delete game/eyes directory.
• Configure game/product.env and game/conf.lua with the settings specific to your game.
  • Disable any platforms you do not want to target.
  • Full details on configuration can be found in the USAGE.md file.
• Replace resources/icon.png with your game's high-resolution icon.
• If you are targeting Android, you need to create a keystore for signing your game; full details are in the USAGE.md file.
• If you want to publish your game to itch.io, you need to add BUTLER_API_KEY to your GitHub repository; full details are in the USAGE.md file.

Running

• Press Ctrl + F5 to Run the game.
• Press F5 to Debug the game.
  • In debug mode you can use breakpoints and inspect variables.
  • This does have some performance impact though.
  • You can switch to Release mode in the Run and Debug tab (Ctrl + Shift + D)

Building

Builds a date stamped .love file and puts it in the builds folder.

• Press Ctrl + Shift + B to Build the game.

Performance Metrics

When the game is running you can access the performance metrics overlay by pressing F3.

Keyboard Controls

• F3: Toggle Overlay
• F5: Toggle VSync (only when benchmark is active)

Controller Controls

• Select + A: Toggle Overlay
• Select + B: Toggle VSync

Touch Controls

• Double Tap top right corner: Toggle Overlay
• Double Tap the overlay itself: Toggle VSync

How to Register/Unregister Particle Systems for performance metrics

Basic Usage

-- When creating a particle system
local particleSystem = love.graphics.newParticleSystem(imageData)
overlayStats.registerParticleSystem(particleSystem)

-- Later, when you no longer need the particle system
overlayStats.unregisterParticleSystem(particleSystem)

Implementation Details

• Where to register: After creating any particle system you want tracked in your stats overlay
• When to register: Immediately after creating the particle system, typically in your load/initialization code
• When to unregister: When destroying the particle system or when it's no longer relevant to track
• Implementation note: Only active particle systems (particleSystem:isActive()) are counted

Detailed Documentation

• USAGE.md

For more detailed technical information about development workflows, build configurations, and deployment processes, please see USAGE.md. This companion document covers:

• Complete project structure and file organization
• Project configuration and settings
• Local development and GitHub Actions workflow details
• Platform-specific build configurations
• Release management and publishing workflows
• Web deployment configurations
• Android signing setup
• Local testing procedures

References

Inspired by and adapted from LOVE VSCode Game Template, LÖVE Actions and love.js player from 2dengine.

Credits

The sample "game" included in this template uses the following assets:

• Aargh! (male screams)
• Eyeballs
• Fireplace Sound Loop
• Parallax Backgrounds