System Requirements Document for exl-private-server

1. Introduction

exl-private-server is a single-page public portal for the EXL - PS Growtopia private server. Its product intent is to give players and community members one striking, instantly legible entry point where they can (a) recognise the server brand, (b) join the community chat, (c) reach the Power Tuner tools for Android and iOS, and (d) obtain the exact host-file entries needed to connect from Windows or MacOS.

The audience is a young, phone-first gaming community that arrives from chat shares, social posts, or word of mouth and wants to be connected within seconds, on whatever device they are holding. The page is anonymous and public: no account, no login, no personal data. Its whole job is presentation and correct hand-off — the brand stack, the community link, the two Power Tuner links, and the two platform host-entry cards, in that fixed vertical order, on a dark violet "elixir" theme.

2. System Overview

The current delivery is a single anonymous, publicly reachable Landing page. It presents, in a fixed top-to-bottom order:

1. The centred brand stack — EXL - PS as the large wordmark, EXL directly beneath it as a wide-tracked subhead, and Private server beneath that as a smaller italic subtitle.
2. The WhatsApp Community capsule linking to https://chat.whatsapp.com/ElpUwqEQAIEGNGrBt6pOkt.
3. The Power Tuner (Android) capsule linking to https://dash.gtps.cloud/android/2157.
4. The Power Tuner (iOS) capsule linking to https://dash.gtps.cloud/ios/2157.
5. The Windows capsule card containing four host rows.
6. The MacOS capsule card containing the same four host rows.

The only accepted human actor is the Server Visitor. All outbound destinations (WhatsApp community, Power Tuner dashboards) are provider/external surfaces owned outside this product; the Landing page only presents and launches them. There is no application-owned identity, no session continuity, no stored user state, and no server-side data of any kind in the current scope.

Narrow exclusions for the current scope: no account creation or login, no user profiles, no dashboards or admin surfaces, no in-page chat, no server-status feed, no download hosting, no payment, and no analytics-driven personalisation. Host entries are presented as copyable text only — the product does not modify any device's hosts file.

2a. Product Interpretation and Delivery Boundary

The product is a presentation-and-hand-off surface, not an application. Everything a visitor needs is visible on one screen-scroll: the brand, the community invite, the two tool links, and the two sets of host entries. The page owns the presentation of these facts and the copy interaction for host lines; it does not own the destinations themselves.

Access ownership: the Landing page is anonymous and public. No identity is established, verified, or resumed, because no accepted behaviour requires durable actor-specific state, a commitment bound to a person, or a value transfer. The community link, Power Tuner links, and host entries are identical for every visitor, so there is nothing to bind to an individual.

Delivery boundary: the current horizon is the single Landing page described above. Anything beyond it — status feeds, account systems, in-page tooling, multi-page navigation — is out of current scope and is not implied by this document.

2b. Source Content Inventory

The following authoritative content-source facts are presented on the Landing page exactly as verified.

Community link

Power Tuner — Android

Power Tuner — iOS

Windows host entries (four rows, exact strings)

• 91.134.85.13 growtopia1.com
• 91.134.85.13 growtopia2.com
• 91.134.85.13 www.growtopia1.com
• 91.134.85.13 www.growtopia2.com

MacOS host entries (four rows, exact strings — identical set)

• 91.134.85.13 growtopia1.com
• 91.134.85.13 growtopia2.com
• 91.134.85.13 www.growtopia1.com
• 91.134.85.13 www.growtopia2.com

2c. Page Content and Component Coverage

Landing

Information and state presented

• Brand stack, centred: EXL - PS (display wordmark), EXL (wide-tracked subhead), Private server (italic subtitle).
• Community capsule: label "WhatsApp Community" with the invite URL as its destination.
• Power Tuner capsules: "Power Tuner (Android)" → https://dash.gtps.cloud/android/2157; "Power Tuner (iOS)" → https://dash.gtps.cloud/ios/2157.
• Windows capsule card: heading "Windows" plus four host rows, each showing one exact host string and its own copy control.
• MacOS capsule card: heading "MacOS" plus the same four host rows, each with its own copy control.
• No dynamic data, no user-specific state, no persisted state.

Primary actions

• Open the WhatsApp community invite (external navigation).
• Open the Power Tuner Android dashboard (external navigation).
• Open the Power Tuner iOS dashboard (external navigation).
• Copy an individual Windows host line to the clipboard.
• Copy an individual MacOS host line to the clipboard.

Supporting actions

• Scroll through the fixed vertical order of blocks.
• Hover/focus feedback on every capsule (scale, specular streak) that does not change behaviour.
• Per-line copy confirmation feedback ("COPIED") that reverts automatically.

Domain entities

• Brand identity — the EXL - PS wordmark stack.
• Community invite — label + URL pair.
• Power Tuner link — platform label + URL pair (Android, iOS).
• Platform host set — platform name (Windows, MacOS) + ordered list of four host strings.
• Host line — a single IP hostname string with its own copy control.

Component responsibilities

• Hero blob — contains the entire brand stack; morphing glossy violet shape; the only place the wordmark appears.
• Elixir drop — lime accent element that falls once on load and settles as the underline beneath "Private server".
• Community capsule — single prominent pill; the lime accent's second appearance as hover fill.
• Power Tuner capsule pair — two pills, side by side on desktop, stacked at 375px.
• Platform capsule card (Windows / MacOS) — card with heading and four host rows; paired side by side at ≥1024px, stacked below that.
• Host row — capsule row with circular chip bullet, the exact host string, and an inline COPY pill.
• Copy pill — per-line control; flashes accent and reads "COPIED" for 1.2s, then reverts.
• Section wave boundary — curved violet transition between blocks instead of a straight rule.

States

• Loading: static content; no data fetch. The only load-time motion is the elixir drop and the hero blob's slow border-radius morph.
• Empty: not applicable — all content is fixed and always present. There is no collection that can be empty.
• Success: a link opens its destination in a new context; a copy action places the exact host string on the clipboard and the pill shows "COPIED" for 1.2s.
• Error: if the clipboard API is unavailable or the copy is rejected, the host string remains fully visible and selectable so the visitor can select and copy it manually; the pill does not falsely report success.
• Recovery: the copy pill returns to its default label after 1.2s and can be retried immediately; a failed external navigation leaves the Landing page unchanged so the visitor can retry or use another link.
• Reduced motion: all motion collapses to static — the blob holds a fixed radius, the elixir drop is already settled as the underline, hover scale and streak are suppressed, and scroll fade-and-rise is removed.

3. Functional Requirements

FR-1 — Centred brand stack As a Server Visitor, I should see the title EXL - PS centred on the page, with EXL directly beneath it and Private server directly beneath that, so that I immediately recognise the server brand.

• Provenance: explicit
• Lifecycle: Trigger — page load. Input — none. Observable result — the three-line brand stack renders centred, in the fixed order EXL - PS → EXL → Private server.
• Access state: anonymous, public.
• Failure/recovery: if webfonts fail to load, the stack still renders in a legible fallback at the same sizes and order.
• Continuation: the visitor scrolls to the community capsule below.

FR-2 — Community link As a Server Visitor, I should see a community link to https://chat.whatsapp.com/ElpUwqEQAIEGNGrBt6pOkt below the title, so that I can join the community chat.

• Provenance: explicit
• Lifecycle: Trigger — visitor activates the community capsule. Input — the exact invite URL. Observable result — the invite opens at the provider destination.
• Access state: anonymous, public; the destination is provider-owned.
• Failure/recovery: if the destination is unreachable, the Landing page is unchanged and the capsule remains available for retry.
• Continuation: the visitor returns to the Landing page and continues to the Power Tuner links.

FR-3 — Power Tuner (Android) link As a Server Visitor, I should see a Power Tuner link to https://dash.gtps.cloud/android/2157 below the community link, so that I can reach the Android tool.

• Provenance: explicit
• Lifecycle: Trigger — visitor activates the Android Power Tuner capsule. Input — the exact URL. Observable result — the Android dashboard opens at the provider destination.
• Access state: anonymous, public; provider-owned destination.
• Failure/recovery: page unchanged on failure; capsule remains available.
• Continuation: the visitor continues to the iOS link.

FR-4 — Power Tuner (iOS) link As a Server Visitor, I should see an iOS link to https://dash.gtps.cloud/ios/2157 below the Power Tuner link, so that I can reach the iOS tool.

• Provenance: explicit
• Lifecycle: Trigger — visitor activates the iOS Power Tuner capsule. Input — the exact URL. Observable result — the iOS dashboard opens at the provider destination.
• Access state: anonymous, public; provider-owned destination.
• Failure/recovery: page unchanged on failure; capsule remains available.
• Continuation: the visitor continues to the Windows host entries.

FR-5 — Windows host entries As a Server Visitor, I should see a Windows link/section below the iOS link containing the host entries 91.134.85.13 growtopia1.com, 91.134.85.13 growtopia2.com, 91.134.85.13 www.growtopia1.com, and 91.134.85.13 www.growtopia2.com, so that I can configure my Windows device to connect.

• Provenance: explicit
• Lifecycle: Trigger — visitor reaches the Windows card. Input — none. Observable result — all four exact host strings are visible, each on its own row, each with its own copy control.
• Access state: anonymous, public.
• Failure/recovery: if a copy fails, the string stays fully visible and selectable for manual copying.
• Continuation: the visitor continues to the MacOS host entries.

FR-6 — MacOS host entries As a Server Visitor, I should see a MacOS link/section below the Windows link containing the same host entries 91.134.85.13 growtopia1.com, 91.134.85.13 growtopia2.com, 91.134.85.13 www.growtopia1.com, and 91.134.85.13 www.growtopia2.com, so that I can configure my MacOS device to connect.

• Provenance: explicit
• Lifecycle: Trigger — visitor reaches the MacOS card. Input — none. Observable result — all four exact host strings are visible, each on its own row, each with its own copy control.
• Access state: anonymous, public.
• Failure/recovery: if a copy fails, the string stays fully visible and selectable for manual copying.
• Continuation: the visitor has reached the end of the page and can act on any link or host line.

FR-7 — Fixed vertical order As a Server Visitor, I should see the page content ordered vertically as title, community link, Power Tuner link, iOS link, Windows link, MacOS link, so that I always know where to look next.

• Provenance: explicit
• Lifecycle: Trigger — page load. Observable result — the six blocks appear in exactly that top-to-bottom order at every viewport.
• Access state: anonymous, public.
• Failure/recovery: order is structural and does not depend on any runtime condition.
• Continuation: n/a — this is a layout invariant.

FR-8 — Purple elixir visual theme As a Server Visitor, I should see a visually striking purple "elixir" theme, so that the server feels live, exclusive, and worth joining.

• Provenance: explicit
• Lifecycle: Trigger — page load. Observable result — dark violet ground, glossy violet capsules with glow, one acid-lime accent, curved section boundaries, and the specified typography.
• Access state: anonymous, public.
• Failure/recovery: if decorative layers fail, all text and controls remain legible and operable.
• Continuation: n/a — this is a presentation invariant.

FR-9 — Per-line host copy As a Server Visitor, I should be able to copy each host line individually, so that I can paste exactly the entry I need without picking it out of a block of text.

• Provenance: required_inference (indispensable mechanics for the accepted host-entry outcome: the entries are only useful if the visitor can transfer them accurately to their own device)
• Lifecycle: Trigger — visitor activates the COPY pill on one host row. Input — that row's exact host string. Observable result — the string is placed on the clipboard and the pill flashes the accent and reads "COPIED" for 1.2s.
• Access state: anonymous, public.
• Failure/recovery: if the clipboard is unavailable or the write is rejected, the pill does not report success and the host string remains fully visible and selectable for manual copying.
• Continuation: the pill reverts to "COPY" after 1.2s and can be used again.

FR-10 — External link hand-off As a Server Visitor, I should be taken to the correct external destination when I activate a link capsule, so that I reach the community or tool I chose.

• Provenance: explicit
• Lifecycle: Trigger — visitor activates the community, Android, or iOS capsule. Observable result — the corresponding provider destination opens; the Landing page remains intact behind it.
• Access state: anonymous, public; destinations are provider-owned and outside this product.
• Failure/recovery: on failure the Landing page is unchanged and the capsule remains available.
• Continuation: the visitor returns and continues down the page.

4. User Personas

Server Visitor

Product context. A player or community member who has heard about the EXL - PS Growtopia private server — typically from a chat share, a friend, or a social post — and opens the Landing page on a phone or desktop to find out what it is and how to get in. They arrive with no account and no prior relationship with the site, and they may be on Android, iOS, Windows, or MacOS.

Primary goal. Get connected as fast as possible: join the community chat, grab the right tool for their device, or copy the host entries they need — without hunting, reading documentation, or creating anything.

Distinct accepted responsibilities.

• Recognise the server from the brand stack and confirm it is the private server they were told about.
• Choose the correct entry point for their situation: community chat, Android Power Tuner, iOS Power Tuner, Windows host entries, or MacOS host entries.
• For host entries, transfer the exact IP hostname strings to their own device accurately.

Relevant inputs or decisions. Which device/platform they are on; whether they want the community or a tool; whether they need the Windows set or the MacOS set. The two host sets are identical, so the decision is about which platform label matches their machine, not about differing content.

Interactions with other accepted participants. None within the product. The visitor's counterparties are external: the WhatsApp community and the Power Tuner dashboards, both provider-owned and reached by outbound link. There is no other accepted human actor in the current scope.

Observable success. The visitor lands on the correct external destination, or has the exact host string on their clipboard and pastes it into their device's hosts configuration. They can tell they succeeded because the destination opened, or because the copy pill confirmed "COPIED" and the pasted text matches the row exactly.

What makes this role distinct. The Server Visitor is a one-shot, anonymous, device-driven actor. Their entire job is selection and hand-off — pick the right capsule, or copy the right line — with no state to maintain, nothing to return to, and no identity to establish. That is why the product is a single public page rather than an application.

5. Core User Flows

Flow 1 — Visitor arrives and identifies the server

1. The Server Visitor opens the Landing page from a shared link on a phone or desktop.
2. The page renders the dark violet ground and the hero blob containing the centred brand stack: EXL - PS, then EXL, then Private server.
3. The lime elixir drop falls once and settles as the underline beneath "Private server".
4. The visitor recognises the server and scrolls; the WhatsApp community capsule is already peeking above the fold at 768px and below.
5. Next step: the visitor chooses a destination — Flow 2, Flow 3, or Flow 4.

Flow 2 — Visitor joins the community

1. From the Landing page, the visitor activates the WhatsApp Community capsule.
2. The capsule's glossy streak sweeps and the lime accent fills it on hover/focus.
3. The invite at https://chat.whatsapp.com/ElpUwqEQAIEGNGrBt6pOkt opens at the provider destination.
4. Observable result: the visitor is in the community invite surface, owned by WhatsApp.
5. If the destination fails to open, the Landing page is unchanged and the capsule remains available; the visitor retries or continues down the page.
6. Next step: the visitor returns to the Landing page and continues to the Power Tuner capsules or the host cards.

Flow 3 — Visitor reaches the Power Tuner tool for their device

1. From the Landing page, the visitor scrolls to the Power Tuner capsule pair.
2. On desktop the two capsules sit side by side; at 375px they stack.
3. The visitor selects the capsule matching their device: Power Tuner (Android) → https://dash.gtps.cloud/android/2157, or Power Tuner (iOS) → https://dash.gtps.cloud/ios/2157.
4. Observable result: the corresponding dashboard opens at the provider destination.
5. If the destination fails to open, the Landing page is unchanged and the capsule remains available for retry.
6. Next step: the visitor returns and continues to the host-entry cards if they also need to configure a desktop device.

Flow 4 — Visitor configures a Windows or MacOS device

1. From the Landing page, the visitor scrolls to the platform cards.
2. At ≥1024px the Windows and MacOS cards sit side by side as a paired platform block; below that they stack, and at 375px each host line wraps under its own copy control.
3. The visitor identifies their platform card — Windows or MacOS — and reads the four host rows, each with a circular chip bullet and the exact string.
4. The visitor activates the COPY pill on the first row, 91.134.85.13 growtopia1.com.
5. Observable result: the string is placed on the clipboard; the pill flashes the lime accent and reads COPIED for 1.2s, then reverts to COPY.
6. The visitor repeats step 4–5 for 91.134.85.13 growtopia2.com, 91.134.85.13 www.growtopia1.com, and 91.134.85.13 www.growtopia2.com.
7. If a copy fails — clipboard unavailable or the write rejected — the pill does not report success, and the host string stays fully visible and selectable so the visitor can select and copy it manually.
8. The visitor pastes the four lines into their device's hosts configuration. The product does not modify the hosts file itself.
9. Next step: the visitor has completed the page; they can return to any capsule or host row at any time.

Flow 5 — Visitor on a small screen

1. The Server Visitor opens the Landing page at 375px.
2. The hero blob scales down and the brand stack renders at its mobile clamp sizes, fully inside the viewport.
3. The Power Tuner capsules stack vertically; the Windows and MacOS cards stack; each host line wraps under its own copy control.
4. No headline, wordmark, label, host line, or control is cropped, overlapped, or covered at any point.
5. Observable result: every link and every host line is fully readable and tappable.
6. Next step: the visitor proceeds with Flow 2, Flow 3, or Flow 4.

Flow 6 — Visitor with reduced motion enabled

1. The Server Visitor opens the Landing page with prefers-reduced-motion set.
2. The hero blob holds a fixed radius; the elixir drop is already settled as the underline beneath "Private server"; hover scale, specular streak, and scroll fade-and-rise are suppressed.
3. All content, links, and copy controls remain fully present and operable.
4. Observable result: the page is static and complete.
5. Next step: the visitor proceeds with Flow 2, Flow 3, or Flow 4.

6. Visuals Colors and Theme

Muse and headline. Karim Rashid — Sensual pop minimalism in violet elixir: glossy curves for a private server portal. The page is a dark violet void holding one enormous glossy blob with the wordmark printed on it, followed by a column of candy capsules. Loud, glossy, welcoming — but every link and host line stays dead-legible and tappable.

Colour tokens (dark mode)

Distribution: roughly 90% violet family, 8% neutral, 2% acid. No blue or indigo anywhere.

Typography

• Headings: Unbounded. EXL - PS at weight 800, caps, -0.02em tracking, so the two glyph blocks read as moulded plastic.
• EXL subhead: Unbounded 300, uppercase, +0.35em tracking, lilac.
• Private server: Quicksand 500 italic — a whispered subtitle, not a third headline.
• Body: Quicksand.
• Scale (1.333 modular): display clamp(56px, 14vw, 148px); subhead clamp(20px, 4.5vw, 34px); subtitle clamp(15px, 3vw, 20px); section heading clamp(22px, 4vw, 32px); card label 18px; host line 15px/1.7 in Quicksand 600 with tabular spacing; body 16–18px.
• Inter, Roboto, Poppins, Arial, and system-ui are not used.

Shape language. Full capsules and organic blobs. Every interactive element is a pill (border-radius: 999px) or a blob with a continuous-curve radius (28–44px). Section boundaries are curved — each block ends in a soft violet wave or blob-masked edge, never a straight rule. Buttons carry a 1px inner highlight along the top edge and a glossy specular streak that slides on hover. Host entries sit in capsule rows with a small circular chip bullet, never a square table.

Spacing rhythm. Single centred column: max-width 720px for text, 960px for the hero blob, with clamp(64px, 10vh, 120px) between blocks.

Imagery style. No photography. Imagery is generated geometry: 2–3 glossy 3D-looking blobs and capsules built in CSS/SVG with radial violet-to-magenta gradients and a specular highlight, plus a faint halftone dot field behind the hero. A small pixel-art "server" glyph — a rounded violet cube with a lime status dot — is the only iconographic motif and repeats as the bullet in each host row.

7. Signature Design Concept

The wordmark lives inside the object.

The first screen is a dark violet void (#150726) with one enormous glossy blob — roughly 720×520 at desktop, 340×300 at 375px — centred in the viewport, lit from the top-left with a violet-to-magenta radial and a single hard specular streak. Inside the blob, stacked and centred: EXL - PS at clamp(56px, 14vw, 148px) in Unbounded 800 near-white, then EXL as a wide-tracked lilac subhead, then Private server in italic Quicksand.

A lime elixir drop falls from the top edge of the blob and lands under the subtitle, leaving a thin lime underline. There is no nav bar and no centred headline-plus-subtext-plus-button pattern — the type is printed on the object, not floating on a background. The first capsule (WhatsApp) peeks above the fold at 768px and below, pulling the scroll.

The concept recomposes only accepted content: the brand stack, the community capsule, the two Power Tuner capsules, and the two host cards. It introduces no new behaviour, page, or destination.

8. Interaction Model & Motion Direction

Interaction Model: Animated Motion Tempo: expressive Hero Dimensionality: layered_2d

Landing Hero Motion Brief

• Focal subject. The single enormous glossy violet blob containing the entire brand stack, with the lime elixir drop descending onto it.
• Input → transformation → outcome thesis. On load, the blob's border-radius begins a slow 12s morph and the lime elixir drop falls from the blob's top edge; the drop lands beneath "Private server" and settles as a thin lime underline. The outcome is a first frame that reads as a live, poured material holding the server's name — with the WhatsApp capsule already peeking above the fold to pull the scroll.
• Motion vocabulary. Liquid and springy but never blocking: a 12s border-radius morph on the hero blob; a single elixir drop on load; capsules scaling to 1.03 with a 260ms cubic-bezier(0.34, 1.56, 0.64, 1) on hover; a glossy specular streak sweeping across a button on hover; section blocks fading and rising 24px on scroll; copy pills flashing the accent and swapping their label to "COPIED" for 1.2s.
• Composed first frame. Dark violet void, halftone dot field faint behind, one glossy blob centred with a hard specular streak from the top-left, the three-line brand stack inside it, the elixir drop mid-fall, and the top edge of the WhatsApp capsule visible at the bottom of the viewport.
• Reduced-motion state. Under prefers-reduced-motion, everything collapses to static: the blob holds a fixed radius, the elixir drop is already settled as the underline beneath "Private server", hover scale and specular streak are suppressed, and scroll fade-and-rise is removed. All content, links, and copy controls remain fully present and operable.

9. Non-Functional Requirements

NFR-1 — Readable text and controls stay whole. Headlines, the wordmark, labels, host lines, and controls stay entirely inside the viewport and their container at 375px, 768px, and 1280px, wrapping or scaling (for example font-size: clamp(...) with its mobile size) to fit. No element covers any part of them. Host text stays whole and wraps at 375px. Provenance: explicit (user design constraint).

• Rationale: the host entries are the page's most consequential content; a cropped or covered host line makes the page useless.

NFR-2 — Reduced-motion support. All motion collapses to static under prefers-reduced-motion, with content, links, and copy controls fully present and operable. Provenance: explicit (creative direction).

NFR-3 — Contrast. Body and headline text at #F4ECFF on #150726 reaches approximately 14:1; muted lilac #B79AD8 is used only for secondary labels at 16px+ at approximately 7:1. Provenance: explicit (creative direction).

NFR-4 — No blue or indigo. The palette is violet and acid-lime only; the generic indigo/blue-on-white SaaS template is forbidden. Provenance: explicit (creative direction).

NFR-5 — No photography. Imagery is generated geometry only — CSS/SVG blobs, capsules, gradients, and the pixel-art server glyph. No stock people or dark-tech particle fields. Provenance: explicit (creative direction).

NFR-6 — Static, dependency-light delivery. The page presents fixed content with no data fetch, no server-side state, and no persistence. Provenance: required_inference — the accepted content is entirely static, so no backend is needed to satisfy any accepted behaviour.

• Rationale: keeps the page fast on mobile connections and removes any failure mode unrelated to the accepted content.

NFR-7 — Clipboard failure is honest. A copy action must never report success when the clipboard write did not succeed; the host string remains selectable as the fallback. Provenance: required_inference — the copy mechanic is only trustworthy if its confirmation is truthful.

NFR-8 — External links open their exact destinations. The community, Android, and iOS capsules must point at the exact verified URLs, unmodified. Provenance: explicit.

10. Tech Stack

• React for the Landing page UI. [Default — not specified by user]
• Vite as the build tool. [Default — not specified by user]
• Plain CSS with custom properties for the token system (colours, type scale, radii, spacing) and for the blob/capsule geometry and motion. [Default — not specified by user]
• No backend, no database, no authentication provider — the accepted content is static and the page is anonymous. [Default — not specified by user]
• Static hosting of the built assets. [Default — not specified by user]
• Docker / docker-compose are not required for this scope; Kubernetes is not required. [Default — not specified by user]

No source-specified technology choices were given, so the above are labeled defaults and carry no product behaviour.

11. Assumptions and Constraints

Assumptions

• A-1. The Landing page is the only page in the current scope, and it is anonymous and publicly reachable. [Assumption — required_inference]
• A-2. The Windows and MacOS host sets are intentionally identical; the platform labels distinguish the visitor's device, not the content. [Assumption — from source]
• A-3. The product presents host entries for the visitor to copy; it does not modify any device's hosts file. [Assumption — required_inference]
• A-4. The WhatsApp community and the two Power Tuner dashboards are provider-owned destinations reached by outbound link; their content and availability are outside this product's control. [Assumption — from source]
• A-5. The page is delivered in the language of the source content (English labels for the capsules and platform headings). [Assumption — from source]

Constraints

• C-1. The title must read EXL - PS with EXL above Private server, centred on the page. [Explicit]
• C-2. Content must be ordered top to bottom: title, community link, Power Tuner link, iOS link, Windows link, MacOS link. [Explicit]
• C-3. Windows and MacOS host entries must be exactly 91.134.85.13 growtopia1.com, 91.134.85.13 growtopia2.com, 91.134.85.13 www.growtopia1.com, 91.134.85.13 www.growtopia2.com. [Explicit]
• C-4. The theme must use a purple elixir colour scheme and a visually striking presentation. [Explicit]
• C-5. The community link must be exactly https://chat.whatsapp.com/ElpUwqEQAIEGNGrBt6pOkt; the Power Tuner links must be exactly https://dash.gtps.cloud/android/2157 and https://dash.gtps.cloud/ios/2157. [Explicit]
• C-6. No account creation, login, profile, dashboard, admin surface, in-page chat, server-status feed, download hosting, or payment is in the current scope. [Explicit — narrow exclusion]

12. Glossary

• EXL - PS — The server's wordmark and the page's primary title, rendered as EXL - PS with EXL and Private server stacked beneath it.
• Private server — The server type; a Growtopia server operated privately rather than on official infrastructure.
• Server Visitor — The single accepted human actor: an anonymous player or community member who opens the Landing page to reach the community, a tool, or the host entries.
• Landing — The single anonymous public page that presents the brand stack, the community link, the Power Tuner links, and the Windows and MacOS host cards.
• Community link — The WhatsApp group invite at https://chat.whatsapp.com/ElpUwqEQAIEGNGrBt6pOkt, presented as the "WhatsApp Community" capsule.
• Power Tuner — The external tool reached at https://dash.gtps.cloud/android/2157 (Android) and https://dash.gtps.cloud/ios/2157 (iOS).
• Host entry — A single IP hostname line, for example 91.134.85.13 growtopia1.com, that a visitor copies into their device's hosts configuration.
• Host set — The four host entries presented under a platform heading (Windows or MacOS).
• Elixir drop — The single acid-lime accent element that falls on load and settles as the underline beneath "Private server".
• Capsule — The pill-shaped interactive element used for every link and host row.
• COPY / COPIED — The per-line copy control and its 1.2s confirmation state.