Zeeshaun e79f473ce4
All checks were successful
Deploy Promiscuity Auth API / deploy (push) Successful in 45s
Deploy Promiscuity Character API / deploy (push) Successful in 57s
Deploy Promiscuity Locations API / deploy (push) Successful in 44s
k8s smoke test / test (push) Successful in 7s
Updating character location based on occupied tile
2026-03-13 21:34:59 -05:00

1.0 KiB

CharacterApi document shapes

This service expects JSON request bodies for character creation and stores character documents in MongoDB.

Inbound JSON documents

  • CreateCharacterRequest (POST /api/characters)
    {
      "name": "string"
    }
    
  • UpdateCharacterCoordRequest (PUT /api/characters/{id}/coord)
    {
      "coord": {
        "x": "number",
        "y": "number"
      }
    }
    

Stored documents (MongoDB)

  • Character
    {
      "id": "string (ObjectId)",
      "ownerUserId": "string",
      "name": "string",
      "coord": {
        "x": "number",
        "y": "number"
      },
      "visionRadius": "number",
      "createdUtc": "string (ISO-8601 datetime)"
    }
    

Outbound JSON documents

  • VisibleLocation (GET /api/characters/{id}/visible-locations)
    [
      {
        "id": "string (ObjectId)",
        "name": "string",
        "coord": {
          "x": "number",
          "y": "number"
        }
      }
    ]
    
    Missing locations within the character's vision window are created automatically before this response is returned.