MaechuriMainServer

API Documentation

Game Session Management

The server automatically manages game sessions using cookies. When a client makes their first request, a game_session_id cookie is automatically created with a UUID value. This cookie is used to track interactions and maintain game state across requests.

Cookie Details:

• Name: game_session_id
• Type: UUID (automatically generated)
• Max Age: 30 days
• HttpOnly: true
• SameSite: Lax

Interaction API

Interact with Scenario Objects

Interact with suspects, clues, or detective in a scenario. Game session is automatically tracked via cookies.

Endpoint: POST /api/scenarios/{scenarioId}/interact/{objectId}

Path Parameters:

• scenarioId (Long): The ID of the scenario
• objectId (String): The object identifier in format tag:id
  • s:id - Suspect (e.g., s:101)
  • c:id - Clue (e.g., c:1)
  • i:id - Detective/Investigator

Request Body:

{
  "message": "안녕하세요"
}

Response for Suspect Interaction:

{
  "type": "two-way",
  "message": "대답 내용...",
  "pressure": 50,
  "pressureDelta": -15,
  "revealedFactIds": [31, 32]
}

Response for Clue Interaction:

{
  "type": "simple",
  "name": "피 묻은 칼",
  "message": "주방 싱크대에서 발견된 피 묻은 식칼."
}

Automatic Record Saving:

• Game session is tracked via game_session_id cookie (automatically created on first request)
• Suspect interactions (s:n) are saved to the record table
• Clue interactions (c:n) are saved to the record table
• Revealed facts from suspect conversations are automatically saved

---

Records API

Get All Interacted Records

Retrieve all records that have been interacted with in the current game session (tracked via cookie).

Endpoint: GET /api/scenarios/{scenarioId}/records

Path Parameters:

• scenarioId (Long): The ID of the scenario

Response:

{
  "records": [
    {
      "name": "피 묻은 칼",
      "content": "주방 싱크대에서 발견된 피 묻은 식칼. 혈액형은 피해자의 것과 일치합니다."
    },
    {
      "name": "집사 지브스",
      "content": "수십 년간 이 저택에서 일해 온 충직한 집사. 항상 침착함을 유지합니다."
    }
  ]
}

Example Request:

GET /api/scenarios/1/records

Error Responses:

• 400 Bad Request: Invalid scenarioId
• 500 Internal Server Error: Game session ID not found (cookie missing)

---

Get Record by ID

Retrieve a specific record (fact, suspect, or clue) from a scenario.

Endpoint: GET /api/scenarios/{scenarioId}/records/{recordId}

Path Parameters:

• scenarioId (Long): The ID of the scenario
• recordId (String): The record identifier in format tag:id
  • f:id - Fact record (e.g., f:102)
  • s:id - Suspect record (e.g., s:101)
  • c:id - Clue record (e.g., c:1)

Response:

{
  "name": "피 묻은 칼",
  "content": "주방 싱크대에서 발견된 피 묻은 식칼. 혈액형은 피해자의 것과 일치합니다."
}

Example Requests:

Get a clue:

GET /api/scenarios/1/records/c:1

Get a suspect:

GET /api/scenarios/1/records/s:101

Get a fact:

GET /api/scenarios/1/records/f:102

Error Responses:

• 400 Bad Request: Invalid record ID format or invalid tag
• 404 Not Found: Record not found