https://github.com/17cupsofcoffee/tetra-template
A blank Tetra template
https://github.com/17cupsofcoffee/tetra-template
game-development gamedev
Last synced: about 1 year ago
JSON representation
A blank Tetra template
- Host: GitHub
- URL: https://github.com/17cupsofcoffee/tetra-template
- Owner: 17cupsofcoffee
- License: mit
- Created: 2021-03-04T18:22:56.000Z (about 5 years ago)
- Default Branch: main
- Last Pushed: 2021-10-31T16:14:14.000Z (over 4 years ago)
- Last Synced: 2025-02-28T13:17:44.483Z (about 1 year ago)
- Topics: game-development, gamedev
- Language: Rust
- Homepage: https://tetra.seventeencups.net/
- Size: 10.7 KB
- Stars: 5
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# tetra-template
This repo contains an example of a blank [Tetra](https://github.com/17cupsofcoffee/tetra) project.
It comes with some pre-built functionality and opinionated defaults, based on what I usually
want/need when I'm starting a new project:
* Simple asset loading
* A hotkey to reload assets
* Screen scaling, for chunky pixel graphics
* Pre-multiplied alpha
* Error reporting via [eyre](https://github.com/yaahc/eyre)
Feel free to use this as a starting point for your own games!
## FAQ
### Why is the project split into a library and a binary?
The crash reporting code is fairly large, and I don't like having to scroll past it every time I'm editing the main file of my game. It'll probably get bigger in the future too, as I'd like to try implementing something like [Way of Rhea's crash handler](https://www.anthropicstudios.com/2021/03/05/crash-reporter/) eventually.
Originally, I worked around this by having a `game` submodule, but then that meant that pretty much everything had to be nested in a `game` subfolder too.
### Why are your assets in a seperate struct?
Assets like textures and sounds are reference-counted internally, so it can be tempting to scatter copies of them across your game. However, I've found it's usually better to try to keep them in one place, so you can easily update/reload them without needing to propagate that change throughout your game's state. I'll then pass this `Assets` struct around where it's needed (e.g. for drawing/playing sounds).
There are probably more robust solutions for asset management, but I think this is a good starting point for simple projects!
### Why do you pre-multiply textures at runtime?
This makes it so I can edit my textures and reload them while the game is running, without a recompile or extra build step. This massively reduces the friction of working with premultiplied alpha for me.
For textures that *are* already pre-multiplied, I use a `.pm` naming convention, which tells the asset loader to skip the runtime conversion.