Skip to content
A set of data and constructs to use in games.
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
LICENSE docs page Gitter

Support what I do on Patreon.

The goal of the library is to share common game features between developers.

Fully cross platform and on its way to be cross language!

Open Source Game Features

Are you tired of games keeping their features for themselves?

Wouldn't it be great if we could share the general features that are really common and spend the time we would save making awesome games?

No one wants to spend 30 hours programming an inventory system that is (almost) the same as those currently released in closed source games.

Its time we change this!

By making as many of the general game features as possible open source, the game developement community will finally be able to focus on what really matters: Making their game unique and enjoyable!

This library aims to do just that. It is a repository where we will share and develop together those reusable game pieces.

Here's some examples of such game features:

  • Inventory systems
  • User management
  • Game chat
  • Permissions
  • And many others


We aim to be data-oriented to facilitate the integration in whichever workflow you have.

Everything here is composed of serializable data and generics. We are not constraining you to a specific way of handling changes in the data.

Integrating those game features is easy:

  • Take the events coming from your game engine or game logic
  • Use them on one or many of the features from this repository
  • Notice the changes in the data
  • Give feedback to your user/player

Its that simple!

Even better, since all data is meant to be serialized, and is created by composing structures together, you can easily:



  • Extensible and fully-featured Inventory system
  • Complex Loot Trees


  • Statuses, effects and transitions
  • Player Authentication
  • User Management (kick, ban, mute, etc)
  • User Permissions
  • Group Based Chat Formatting and Scopes
  • World ownership and protection systems
  • Faction-based claiming systems.

Statuses, what are those?

This will be one of the main features of this library.

That's a bit of an abstract concept, so I'll use an example to explain it.

Let's say you have a heat/temperature value associated to the player.

The inventory attached to the player will pick that up and if the heat is high enough, it will trigger an item transition on the items inside (smelt iron ore into iron bar) and an effect (burn the player).

This can be abstracted to represent the majority of the game state. For example:

  • Player speed, health and mana
  • Electricity propagation through wires and consumed by machines
  • Spoiling food
  • Trading currency, buying and selling items

In this case, the heat is the status, the transition is the ore smelting and the effect is burning.


I highly encourage contributing to this library. All of the game developement community will be able to benefit from it. And when they benefit, you benefit too via the increased amount of visibility of the library, which means more developement effort and more features!

If you cannot or don't want to contribute code, you can still help! All money that goes into my Patreon is a huge help and allows me to spend more time working on this project.


I am currently looking into FFI bindings compatibility. If the library is compatible (which it should), that means that it will be usable in any language that can bind to a C API. Yes, that means you will be able to use this library in your c, c++, c# projects, making this library compatible with the following engines:

  • Source
  • Unity
  • Unreal
  • Cry Engine
  • Amethyst Engine
  • Piston
  • ggez
  • Any engine that can load a c static library in any way (.dll, .so).



Add this line to your Cargo.toml file:

game_features = "*"

For more information on each feature, see the docs badge at the top of this page. Alternatively, for usage examples, there are unit tests at the bottom of each file (except in the src/ directory which are good examples.

Good luck! Feel free to ask any questions you may have.

Other Languages



When possible, report issues through Github's issues page.

Questions can be asked in our gitter channel. See the badge at the top of this page.

You can’t perform that action at this time.