Thorsten
07665595a2
The adventure-text field was buried at the bottom of the proposal form, after the whole interview — the user wanted it to be the very first thing shown when clicking "Neues Spiel", since pasting an adventure should drive the proposal rather than follow it. GameSetupChat now opens on an "Eigenes Abenteuer (optional)" step: paste the text (or skip) before the wizard chat starts at all. The setup-chat backend call now receives that text and, when present, infers genre/world/scope from its opening directly instead of asking about them — the proposed name/description come out already specific to the pasted adventure. Removed the now-redundant adventure textarea from the proposal form (it's collected once, upfront). Verified live: pasting a short pirate one-shot produced "Klingt nach einem klassischen Piraten-One-Shot rund um Port Royal – das Genre und den Umfang leite ich direkt daraus ab", skipping straight to the one remaining question (experience level), and the final proposal named Isabella Steel and Blackfin's fortress directly from the text. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
18 lines
341 B
Python
18 lines
341 B
Python
from pydantic import BaseModel
|
|
|
|
|
|
class GameSetupChatRequest(BaseModel):
|
|
messages: list[dict] = []
|
|
adventure_text: str = ""
|
|
|
|
|
|
class GameSetupProposal(BaseModel):
|
|
name: str
|
|
description: str
|
|
|
|
|
|
class GameSetupChatResponse(BaseModel):
|
|
messages: list[dict]
|
|
assistant_text: str | None
|
|
proposal: GameSetupProposal | None
|