Skip to content

five-on-it / apps/client/src/ui/CreatePage

apps/client/src/ui/CreatePage ​

The creation page (?create, one of the game pages): an owner describes a game and the platform's own model makes it with them, in a conversation (TECHNICAL_SPECS §9.8). Its header says the creations left today (and when they start again) and whether creation is open now (off on the platform, the account: on a Steam platform a lent copy, or no Steam account; or the day's budget spent and when it resumes). The brief's composer: the brief (4,000 characters at most, counted, with examples to start from), where it is made as cards with a picture each (Riverbend, a new city drawn freely, the default; a grid town; a region), its size and its missions (1 to 3) as segmented controls, and the model that makes it (GET /creations/models: each with what it is good for and its price a million tokens, the best one recommended and picked). Then the owner's creations, newest first and filtered by tab (all, under way, the owner's turn, over; &job=<id>, the in-game toast's link, puts one in view): each a card with its state (its place in line or why it waits, its step while it runs), how long it has taken, the model making it, its conversation (the brief, the model's answers with what it did, the owner's messages, the platform's word when a turn could not finish), once the model answered (waiting) a box to say more with the model for the next turns (Send) or End the conversation, with the share of its budget spent; Cancel while it is under way; and its result, the draft so far: its preview, its missions, its level in text (or its places), Playtest, Look round, Open in the studio, Publish (by link), Revise (a new creation on the same draft, once its conversation is over) and Delete (its draft, level and missions, after a confirmation). The list is asked again every second and a half while a creation is under way. A guest is asked to sign in; on a platform for the game's owners, a visitor nobody signed in to is offered Steam's sign-in. The ids are the end-to-end tests' contract.

Interfaces ​

Functions ​