Guides / Whitelist

Whitelist and application pages

Whitelist pages sell the process before anyone opens a ticket. On templates like DayZ Ashfall, you get a dedicated whitelist.html with questions, a rules checkbox and a sidebar that points people at Discord. This guide covers what to rewrite — and what the demo form can and cannot do by itself.

Whitelist forms guide

Who needs a whitelist page

Public servers often skip applications. RP, semi-whitelisted DayZ, and gated clans need a clear path: read rules → join Discord → apply → wait. The website explains that path; GameSignal still hosts the web pages, not the game whitelist plugin itself. Staff approve people in Discord or on the game host — the site is the front door.

Ashfall is the DayZ premium layout that ships a full whitelist page. Other templates may send players to a #join section or Discord only. If your design has no whitelist.html, add a short “How to apply” block on the home page or rules page instead of forcing a form that is not in the kit.

Files to open

In the Ashfall folder you will usually touch:

  • whitelist.html — questions, success message, sidebar steps
  • js/config.js — Discord invite used by “Contact staff” / Discord buttons
  • rules.html — linked from the “I agree to the rules” checkbox
  • Home CTAs on index.html that say “Apply for whitelist”

Work on a copy, preview locally, then upload. The general VS Code workflow is in Edit Templates.

Rewrite the copy first

Demo text mentions fictional channels like #whitelist-desk and placeholder timelines. Replace them with your real channel names, expected review time (“usually within 48 hours”) and age or platform requirements. Keep the sidebar steps honest: if you never DM applicants, do not promise DMs.

Hero and section labels can stay atmospheric; the instructions must be boring and accurate. Players abandon forms that contradict Discord pins.

What the demo form does

Ashfall’s demo form is a front-end pattern: fields, validation messaging and a success panel that appears after submit in the template’s JavaScript. The form’s action is a placeholder (#). Out of the box it is not a guaranteed email pipeline, database or Softaculous app that files applications into a staff inbox.

That is intentional for a static community template: many groups already run applications inside Discord (tickets, bots, Google Forms). The page’s job is to collect the right info on-brand and push people into the process you actually staff. If you need server-side form mail or a custom endpoint later, that is a separate integration — ask via Contact rather than assuming the demo posts somewhere useful.

Linking Discord applications

Three patterns work well with GameSignal templates:

  1. Invite + instructions: Form (or page) tells applicants to join Discord and open a ticket. Set discord.invite in config so every Discord button matches. See Discord invite links.
  2. External form URL: Replace the form block with a short explanation and a primary button that opens your Google Form, Typeform, or Discord application bot link in a new tab.
  3. Hybrid: Keep a few on-page questions for tone, then a final button “Continue in Discord” for the official submit.

Update success-panel wording (“Pending review”, “Check Discord”) so it matches the pattern you chose. A success state that invents a ticket ID you do not generate will confuse people.

Changing fields

Duplicate an existing field block to add questions (age, hours available, prior bans, preferred map). Remove fields you will never read — unused Steam ID fields teach applicants that the form is theatre. Keep required markers only on fields staff truly need.

The rules checkbox should link to your live rules.html. If rules live only in Discord, say that explicitly and link the invite instead of a dead page.

Accessibility: leave <label for="…"> tied to input IDs when you rename fields. Broken labels make the form harder on phones, where most applicants sit.

Publish checklist

  • Channel names and review times match Discord
  • Discord buttons use your invite via config.js
  • Rules link opens your real rules
  • Success / next-step text matches how staff actually review
  • Home “Apply” CTA still points at whitelist.html (or your external form)
  • Uploaded to hosting and tested on mobile

Ashfall pricing and DayZ template choices are on the DayZ templates page. General hosting questions: FAQ.

Need the apply flow pointed at Discord?

Tell us your template and preferred app method (ticket, bot or external form) and we can outline the edit — or apply it on Managed plans.

Contact support DayZ templates