Tämä artikkeli ei ole vielä saatavilla kielelläsi. Alla näytetään englanninkielinen lähde.

Before you change the URL alias

Only the active leader of the exact clan can change its URL alias. Admins, officers, members, inactive memberships, another clan's leader, and the demo clan cannot submit the change.

Choose a globally free alias containing 3–63 lowercase letters, numbers, or hyphens. Runekist normalizes the value before checking it. A current, grace-period, or retired alias is permanently claimed, including an old alias that belonged to this clan, so it cannot be reused.

If collection has been configured, fully pause it first. Pausing is not enough: wait until the pause is confirmed and every external run, including linked-account work, has finished. A clan with no collector configuration or run history may change its alias before setup.

Changing the alias intentionally gives the next Screeny run a clean browser profile. It may require the game login and 2FA again. Runekist does not resume collection automatically.

Change the alias

  1. Open Leadership → Settings → Clan name and find Clan URL alias below the separate display-name form.
  2. Review the current canonical URL and collector-readiness status. If needed, open the collection pause controls, request a pause, and return only after Runekist confirms it.
  3. Enter the new alias. Check the normalized requested URL preview and fix any format or availability error.
  4. Review the displayed retirement date. The previous alias remains directly usable for exactly seven days after confirmation.
  5. Type the normalized alias again in the confirmation field.
  6. Select Change clan URL alias.

Runekist moves this dashboard to the equivalent Clan name settings URL under the new alias. Other open dashboards refresh their clan identity and generate links with the new canonical alias.

What remains the same

The clan keeps the same internal clan identity. Existing and queued imports, members, periods, rules, billing, notifications, Discord and Telegram mappings, API records, and other integrations remain attached to that same clan.

The previous alias works directly during the seven-day grace period. At the exact deadline it becomes redirect-only: old paths and the old vanity host permanently redirect to the new canonical alias while preserving the applicable path and query. The old alias remains reserved forever and never becomes available to this or another clan.

When you are ready, deliberately resume collection. Expect the first Screeny run under the new alias to use a clean browser profile and complete login or 2FA again if requested.

Troubleshoot the change

  • If the action is disabled, finish pausing collection or wait for every external run to finish.
  • If Runekist says the alias is taken, choose another value; the owner of an existing or historical alias is not disclosed.
  • If confirmation fails, type the normalized alias exactly as shown in the requested URL preview.
  • If a previous alias is still in its grace period, wait until it retires before requesting another change.
  • If the next Screeny run requests login or 2FA, complete it as a deliberate consequence of the clean browser profile. Do not create a new clan.
  • If old links do not redirect after the deadline, contact support with the old alias, new alias, and the affected path. Do not try to reclaim the old alias.

For a display-name-only change, read Rename the displayed clan name. For the pause workflow, read Pause or resume collection. For related clan-wide controls, read Manage public sharing, rewards, and clan settings.

Selaa Ohjeita