> For the complete documentation index, see [llms.txt](https://cyr1en.gitbook.io/commandprompter/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cyr1en.gitbook.io/commandprompter/prompts/sign-ui-prompt.md). # Sign UI Prompt Use `s:` to collect text through a Sign editor. ``` /gamemode ``` Inline display text is split on `{br}` and placed around writable rows according to `SignUI.Input-Field-Location`: * `bottom` (default): Prompt text occupies lines 1–3 and player input is captured on line 4. * `top`: Input is captured on line 1 and prompt text occupies lines 2–4. * `bottom-aggregate`: Prompt lines are placed at the top and all remaining bottom lines are aggregated (concatenated with spaces) into the final argument. * `top-aggregate`: Prompt lines are placed at the bottom and all remaining top lines are aggregated (concatenated with spaces) into the final argument. In normal mode, single line modes (`top`, `bottom`) take the designated input line, while aggregate modes concatenate all non-prompt input lines with spaces. ![](https://i.imgur.com/AwiAJL8.png) ## Labeled multi-argument mode Multi-argument mode activates only when at least one `{br}` segment is exactly a non-space label followed by a colon, such as `Mode:` or `Value:`. On submission, each row matching `label:anything` contributes only the text after its first colon. ``` /time ``` If the player edits the labeled rows to `Mode:add` and `Value:1600`, the answer is `add 1600`. ![](https://i.imgur.com/40ayTIG.png) Labels containing spaces, or a segment that already has text after its colon, do not activate multi-argument mode. Sign answers always have color codes stripped. An empty result, the cancel keyword, or closing/cancelling the screen cancels the session. Sign prompts use version-specific providers for Minecraft 26.1.2 and 26.2.x and fall back to Chat if no compatible provider opens. See [Sign UI settings](/commandprompter/configuration/prompts-configuration/sign-ui.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://cyr1en.gitbook.io/commandprompter/prompts/sign-ui-prompt.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.