# Developer roadmap

AlloyMC is growing from a launcher into a set of tools around Minecraft, and the API is how they connect. This is what's planned, in order. There are no dates until things work; the [changelog](https://api.alloymc.dev/docs/changelog) says when something ships.

## Apps and scopes

So that your own apps can act for people, not only Alloy:

- Register an app on alloymc.dev with a name, an icon and redirect addresses.
- People sign in through a consent screen that lists exactly what your app asks for, using OAuth 2.1 with PKCE.
- **Scopes** keep access narrow, for example `profile:read`, `profile:write`, `follows:write`, `minecraft:read`.
- Tokens appear under Devices on the person's account, where they can be revoked at any time.

## Extensions for Alloy

Add your own pages, buttons and checks to the Alloy launcher:

- An extension is a small package with a manifest that declares what it needs, and asks for nothing more.
- It runs sandboxed, talks to Alloy through a documented interface, and can use the AlloyMC API with the user's consent.
- First uses we have in mind: modpack checks ("this pack needs at least 6 GB of memory"), shortcuts for servers you play on, and themes.

## Plugin platform

A home for Minecraft server plugins and tools built around AlloyMC, starting with the [player lookup](https://api.alloymc.dev/docs/minecraft) that already works today: show players' AlloyMC profiles in game or on a server website.

## Posts and packs

Screenshots on profiles, shared modpacks and a feed. They'll be readable and writable through the API from the day they ship.

## Tell us what you need

The order above can change if something else matters more to the people building on AlloyMC. [Open an issue](https://github.com/Elchi-dev/AlloyMC/issues) or write to [contact@elchi.dev](mailto:contact@elchi.dev) with what you want to build.