endgame 0.1.0

A turn-based game engine.
Documentation
  • Coverage
  • 0%
    0 out of 1 items documented0 out of 0 items with examples
  • Size
  • Source code size: 4.08 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 228.87 kB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 9s Average build duration of successful builds.
  • all releases: 9s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • gawashburn/endgame
    0 0 0
  • crates.io
  • Dependencies
  • Versions
  • Owners
  • gawashburn

endgame

The endgame library is a turn-based game engine, but not a Game Engine. There plenty of quality Game Engines out there for handling your graphics, audio, input, networking, and so forth. The endgame library is instead an engine and tools for helping you build out and test your game mechanics. It could even be paired with a Game Engine to flesh out the rest of your game.

This is the initial commit, which is essentially a minimal crate while I migrate my code from the existing internal repository and crate to this public one.

Table of contents

What's in a name?

I had originally chosen a name for this project that was more directly influenced by the game I was building this engine to support. But there was already a crate with that name, as well as libraries in other languages, and at least one company. I tried some investigation into other thematically related names, but most wound up being too long or esoteric.

Next I decided to try a sillier name, but it turns out that was already used by a series of games.

Musing, it struck me, what kind of name was a Godot for a Game Engine? Obviously, it was a reference to the play Waiting for Godot by Samuel Beckett. So I thought, why not another Beckett play? And after a quick web search, I found Endgame, which was so on the nose that I couldn't resist.