project_launch

Behavior#

Get the launch page for the creator. The token's name, ticker, pairing, fees, recipient and signing are chosen and signed only on that page, in the creator's own wallet. Don't ask for them or advise on them in chat. Call it with confirm: true once the creator wants the game public or its token launched (a yes to deploying it counts; without confirm it refuses); it returns launch_url, the site's create flow at the token step (/create?project=<slug>), and launches nothing, and an agent cannot launch.

Hand launch_url over with one line saying the token's details are set there: when no build is verified yet, ready is false with the blocker, and the page asks the creator to play the draft once before Pay & launch. On that page the creator first pays a $14 launch fee in ETH or USDG to the Looping treasury, kept as the game's launch credit until its launch uses it (a failed launch never does); all sales are final. launch_fee in the result reports it: unpaid, credit or used; an agent never pays it.

The launch releases the newest build that started for someone playing it (its boot is ok) on the game's own address and lists the game; the registered launch makes the game public. Before it every build is a preview; project_status reports when the game is public. For a game that plays online the result also carries hosting (what its public matches cost per player-hour) and, when it has no hosting credits for them, must_act: say that line, with its link, in the same message as launch_url; an agent never buys credits.

Input parameters#

The descriptions above include conditional requirements. The full schema below shows structural validation; runtime checks also apply.

JSON Schema#

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "confirm": {
      "type": "boolean",
      "description": "true only after the creator has said they want to launch the token"
    }
  },
  "required": [
    "confirm"
  ],
  "additionalProperties": false
}