How does authorization and other things work in Realms Alpha

Initial Setup

To implement Realms Alpha functionality, you need:

• A web server/website to handle authorization
• Access to the game's binary file for URL modification
• Understanding of the API endpoints structure

---

1. Player Authorization Process

Step 1: Login Trigger

When a player clicks "Login" in the game settings, the authorization process begins.

Step 2: Authorization Redirect

After successful authentication, redirect the player to your server with the following URL format:

http://site/m/launchmc?accessToken=(PLAYER_TOKEN)&clientToken=(CLIENT_TOKEN)&sessionId=(SESSION_ID)&identity=(IDENTITY)&profileName=(PLAYER_NICKNAME)&profileUuid=(PLAYER_UUID)&email=(EMAIL)&newUser=(true_if_new_player_otherwise_false)

Parameters Explanation:

• accessToken - Player's access token
• clientToken - Client application token
• sessionId - Current session identifier
• identity - Player identity
• profileName - Player's nickname
• profileUuid - Player's unique identifier
• email - Player's email address
• newUser - Boolean indicating if this is a new player

---

2. Realms Service Status

Endpoint: GET /peo/info/status

The game sends this request on every launch (and possibly after authorization) to check the availability of Realms service.

Required Response (JSON):

{
    "buyServerEnabled": false,
    "createServerEnabled": false, 
    "serviceEnabled": true
}

Parameter Details:

• buyServerEnabled - If true, players can purchase servers
• createServerEnabled - If true, players can create their own servers
• serviceEnabled - If true, the Realms button appears in the menu; if false, it doesn't

---

3. Server List Request

Endpoint: GET /peo/server/list

When entering Realms, the game requests the list of available servers.

Response Format:

The response should be a JSON array of server objects with the following structure:

class ServerInfo {
    [JsonProperty("id")]
    public int ID { get; set; }

    [JsonProperty("name")]
    public string Name { get; set; }

    [JsonProperty("open")]
    public bool IsOpen { get; set; }

    [JsonProperty("ownerName")]
    public string OwnerName { get; set; }

    [JsonProperty("myWorld")]
    public bool IsMyRealms { get; set; }

    [JsonProperty("maxNrPlayers")]
    public int MaxPlayers { get; set; }

    [JsonProperty("playerNames")]
    public string[] PlayerList { get; set; }

    [JsonProperty("type")]
    public string RealmsType { get; set; }

    [JsonProperty("serverId")]
    public int ServerId { get; set; }

    [JsonProperty("invited")]
    public string[] InvitedPlayers { get; set; }
}

Property Descriptions:

• id - Unique server identifier
• name - Display name of the server
• open - Whether the server is currently accessible
• ownerName - Name of the server owner
• myWorld - Whether this realm belongs to the current player
• maxNrPlayers - Maximum number of players allowed
• playerNames - Array of currently connected player names
• type - Server type (likely "public" for public servers)
• serverId - Server identifier
• invited - Array of invited player names

---

4. Token Refresh

Endpoint: POST /refresh

The game sends this request on each game launch to refresh authentication tokens.

Request Body (JSON):

{
    "accessToken": "token",
    "clientToken": "client_token",
    "selectedProfile": {
        "name": "PlayerNickname"
    }
}

---

5. Server Connection

Endpoint: POST /peo/server/{server_index}/join

When a player clicks to connect to a server, the game sends this request.

URL Parameter:

• server_index - Index of the server in the previously returned server list array

Response Body (JSON):

{
    "ip": "127.0.0.1",
    "port": 19132,
    "serverId": "0"
}

Response Parameters:

• ip - Server IP address to connect to
• port - Server port number
• serverId - Server identifier

---

Attached Files

VBAmjnju.cs

---

Implementation Notes

---