Maffin's Gamedev Services

MGDS documentation

Sign players in, keep their saves, hear about their problems, change your game without a patch, rank their scores and reach every running copy at once. Plain HTTPS and JSON, in any engine, with no SDK to install.

Every call starts with https://www.dasmaffin.com/api/mgds/v1/projects/{projectId}

Sign your first player in Your projects

Getting started

1

Make a project

On Projects. Its id, on the project's Configure page, goes in every address.
2

Activate what you need

Every service starts off. Turn on the ones your game uses under Configure, Services. Start with Authenticate.
3
Sign a player in

One call, no account needed. You get back a token for everything else.
```
POST/auth/anonymous
```

Players

Signing a player in Anonymous, Steam, s&box or a dasmaffin.com account, and staying signed in. The signed-in player Who is signed in, from the game itself. Signing out Ending one session, or every one at once. Linking accounts One player, signed in with Steam on one device and anonymously on another. A player's own data Exporting and deleting everything a player has in a project.

Services

Save files Each player's progress and settings, on every device, shareable between players. Reports Problems reported from inside the game, with logs, pictures and recordings, answered from the dashboard. Remote config Values, pictures and videos your game fetches, per environment, with rules for who gets what. Leaderboards Ranked scores, with buckets, tiers and scheduled resets. Push messages Make every connected game run a method, now or at a set time.

Your own server

Who is this player? Your own game server checking a player's token, with or without asking us. Service accounts Keys for your own servers and tools, with exactly the permissions they need.

Reference

Errors Every status code the API answers, and what it means. Examples Whole examples for Garry's Mod, s&box, Unity and Godot.

Before you start

Maffin's Gamedev Services: backend services for games, in any engine. Plain HTTPS and JSON, no SDK needed. Every call is made under one project:

https://www.dasmaffin.com/api/mgds/v1/projects/{projectId}

projectId is the GUID on the project's Configure page.

Always https. A call over plain http is refused with 403 and an error giving the https address, rather than redirected: a redirect would let the first request - and the player's token in it - cross the network unencrypted every time, without anybody noticing.

A service does nothing until it is activated. Each one - Authenticate, Save files, Reports, Remote config, Leaderboards, Push messages - is activated on the project's Configure page, under Services. Until then it is not in the dashboard's list on the left, and every call to it answers 403 with an error saying which service is not activated. Deactivating one refuses the game at once and deletes nothing: activated again, it picks everything back up. Save files and leaderboard scores belong to signed-in players, so a game that uses them activates Authenticate too.

Once Authenticate is active, anonymous sign-in always works. Steam and dasmaffin.com are identity providers the project adds on its Authenticate page; one it has not added answers 403.

Writing a client with an AI agent, or a program? Everything on these pages is one Markdown file: /api/mgds/doc.md. Hand it the whole thing.