Guides / Wipe schedules

Keep wipe and schedule info updated

Players check your site when Discord is noisy. If the wipe clock, map day or BP note is wrong, they stop trusting the page. This guide covers where that copy lives on GameSignal templates — especially Rust and DayZ — and a habit that keeps it honest after every wipe.

Wipe schedule guide

What the website is for

GameSignal hosts your community website — the public pages for status, rules, Discord and schedule notes. It does not wipe the game server, push map files, or talk to your game host API. Treat the site as the source of truth players can open without joining Discord first. When Discord announces a delay, update the site the same hour, or remove the countdown until you have a firm time.

If you are still learning the template folder layout, skim Edit Templates first, then come back here for the wipe-specific pieces.

Where schedule copy lives

Most templates put schedule text in HTML on the home page (index.html), not in js/config.js. Config covers community name, Discord invite and server IP. Wipe headlines, “every Thursday” tiles, rates and team limits are plain text (and sometimes a small script) you edit by hand.

Search the template in VS Code for words like wipe, countdown, Thursday, or UTC. That finds every demo leftover in one pass — including footer CTAs that still say “Ready to wipe in?” after you changed the main section.

Rust wipe blocks

On the standard Rust template, the home page includes a section with id="wipe". Demo content looks like a big “Next wipe in …” heading plus tiles for map wipe, BP wipe, rates and team limit. Replace those paragraphs with your real cadence:

  • Map wipe day and clock (include timezone)
  • Whether blueprints wipe with the map or monthly
  • Gather / craft rates if you advertise them
  • Group size (solo/duo/trio, etc.)

Nav links that jump to #wipe can stay. Change the heading when the next wipe moves — a static “Next wipe in 2d 14h” line in the demo is placeholder marketing, not a live timer. Either write a clear calendar sentence (“Map wipe: Thursday 18:00 UTC”) or wire a real countdown script yourself if you want ticking numbers.

After a forced wipe or seed change mid-week, update the tile text and any hero lead that still mentions the old schedule. Stale rates on the site cause more tickets than almost anything else.

DayZ / Ashfall countdown

DayZ templates vary. Cherno Refuge and Blackpine lean on status panels and copy you edit in HTML. The premium Ashfall add-on includes a visible wipe countdown on the home “console” block — days, hours, minutes, seconds under a “Next community wipe” label, plus a short hint such as “Fresh stories begin at 18:00 UTC.”

In Ashfall’s js/main.js, the demo countdown is driven by a target date near the top of the wipe section (look for COUNTDOWN_TARGET). For production you set that date (and hour) to your next wipe, then update the matching hint text in index.html so the clock and the sentence agree. When the wipe completes, bump the target forward to the next cycle — do not leave a finished countdown sitting at zeros for days.

If you run multiple maps or a soft “economy wipe” that is not a full map reset, say so in the hint. Vague “wipe soon” copy trains players to ignore the site.

A wipe-day edit routine

  1. Decide the public wipe time in staff Discord first — one pinned message, one timezone.
  2. Open the template folder locally (or download from cPanel if that is your only copy).
  3. Update index.html schedule tiles / headings / hints.
  4. If Ashfall (or your own script) uses a target date, set it in the JS file that owns the countdown.
  5. Search the whole folder for the old weekday or old map name and fix leftovers.
  6. Preview in a browser, then upload only the files you changed.
  7. Hard-refresh the live site (Ctrl+F5) and check phone width once.

Assign one person as “site owner” for wipe weeks. Shared editing without a backup is how demo “Oxide Raiders” text resurfaces six months later.

Timezones and wording

Always name the zone: 18:00 UTC, 2pm Eastern, or your region’s equivalent. “Tonight” means nothing on a global server list. If you delay a wipe, change the site before the old time passes — a clock that hits zero while the server is still up looks broken even when Discord explained the delay.

Keep schedule language short. Players skim. Put long lore about why you wipe in a Discord announcement or rules appendix, not in the four-tile strip.

Upload and verify

Log into cPanel File Manager, open the community site folder under public_html (or the path from your welcome email), and overwrite the edited HTML/JS files. Keep folder structure identical. After upload, open the live URL in a private window so cached CSS or HTML does not hide your change.

Still stuck? Contact support with your game, template name and the exact wipe time you want shown. On Managed plans we can apply the text for you. Plans and SSL details are on Hosting; broader questions sit in the FAQ.

Wipe moved and the site is wrong?

Send the new day/time and template name — we’ll tell you which file to touch or update it for you.

Contact support Back to guides