Alliance Change Log

Sign in to review joins, leaves, name changes and rank changes in your alliance.

Sign in

What is the Kingshot Alliance Change Log?

The Alliance Change Log is a history view for your Kingshot alliance roster. It compares roster observations over time and records when a governor ID joined, left, changed their name or changed alliance rank. Each row keeps the governor ID, the observed before and after values, and the rank or power context available at that observation, so an officer can follow a rename without losing the player behind it.

It is not a combat log, kill feed or login tracker. It answers a narrower question: what changed in the alliance membership, and when was that change observed?

Joined

A governor ID appeared in the alliance roster. Use it to confirm a recruit or a returning member.

Left

A governor ID was no longer in the observed roster. The log records the absence, not the reason.

Name changed

The same governor ID now uses a different display name, so a rename does not hide the player behind it.

Rank changed

The alliance rank moved between R1–R5. Useful when officers change or a leadership handover happens.

How to use the Alliance Change Log

The Change Log works with the alliance you already manage in Kingshot Guide. You do not need to upload a second member list.

  1. 1

    Bind your alliance

    Open Alliance Roster and bind the kingdom and in-game alliance tag. The Change Log uses the same workspace, so there is no second setup.

  2. 2

    Turn on tracking

    Enable automatic tracking in Alliance Activity Tracker. The first observation creates a baseline; changes are detected between later observations.

  3. 3

    Open the Change Log

    Use the filters to review joins, leaves, name changes or rank changes. Search by governor ID, old name or new name.

  4. 4

    Review or export

    Open a player page for context, or export the filtered list as CSV for officer notes and leadership handovers.

How it helps alliance leaders

Follow a name change

A player can rename without changing their governor ID. The log keeps the old and new name together, so roster notes and recruitment checks stay connected to the right account.

Spot unexpected departures

See which governor IDs disappeared from the observed roster, then open the player page or compare the timing with your own officer notes. The log does not claim why a member left.

Verify a leadership change

Rank changes show when a member moved between R1 and R5. This is useful during an officer rotation, an alliance handover or a review of who held which role.

Keep a portable roster record

Export the filtered log as CSV for leadership notes, a monthly roster review or a handover to the next R5. The export keeps governor IDs and observed values.

What the log cannot tell you

  • It cannot identify the officer who invited or removed a member.
  • It cannot prove whether a departure was voluntary or a kick.
  • The timestamp is the observation time, not the exact in-game action time.
  • A tracking pause or failed observation can leave a gap in the history.
  • It does not prove that a player is inactive or has stopped logging in.
  • History is limited to the recorded alliance roster and the retention window.

How it fits with the other alliance tools

ToolQuestion it answersWhat it shows
Alliance RosterWho is in the alliance nowCurrent members, ranks, power and officer notes
Alliance Activity TrackerHow members are growingActivity signals, growth deltas and review candidates
Alliance Change LogWhat changed over timeJoins, leaves, name changes and rank changes

Use Alliance Roster to maintain the current member list, Alliance Activity Tracker to review growth and activity signals, and this Change Log when you need the membership history between those snapshots.

Data refresh and history

The log uses the alliance roster observations collected by the Activity Tracker. Automatic tracking is scheduled daily at 01:25 UTC; a manual update can be requested from the Activity Tracker page and is normally picked up within five minutes. Changes are detected by comparing the latest roster with the previous successful observation. A long pause, a failed observation or a change of alliance can create a gap. The page shows the last observed time and warns when the latest observation is more than two days old.

Roster events are retained for up to 180 days. The newest changes are shown first, with older rows available through the load-more control. CSV export includes the filtered rows and is limited to the events available in the current history.

Alliance Change Log FAQ

What is the Kingshot Alliance Change Log?

It is a history view of alliance roster changes. It compares roster observations and records four events: joined, left, name changed and rank changed. Each row keeps the governor ID and the observed before and after values.

How often is the Alliance Change Log updated?

Changes are detected when a new roster observation succeeds. Automatic tracking is scheduled daily at 01:25 UTC, and a manual update can be requested from Alliance Activity Tracker. A change can appear at the next successful observation rather than at the exact minute it happened.

Can it show who kicked or removed a member?

No. Public alliance data does not include the officer who invited or removed a player. A left event means the governor was no longer in the observed roster; it does not prove that the player was kicked.

Can it show the exact time a player left?

No. The timestamp is the time of the roster observation, not the in-game action time. If tracking was paused or an observation failed, the recorded time can be later than the actual change.

Why is a roster change missing from the log?

The log needs two successful observations to compare. A long tracking pause, a failed update, a change of alliance or a member who joined and left between two observations can create a gap. The page warns when the last observation is more than two days old.

How far back does the history go?

Roster events are retained for up to 180 days. The page shows the newest changes first and supports loading older rows. Events older than the retention window are removed.

Does the Change Log show a player's power or combat stats?

It focuses on membership history. A row can include the rank and power values observed at the time of the change, but the Change Log is not a power tracker, kill feed or battle report.

Is the Alliance Change Log included in Pro?

Yes. The Change Log is an Alliance tool included with Pro membership. It uses the alliance workspace and tracking you already configured for Alliance Roster and Alliance Activity Tracker.

Open the Change Log with your alliance

Bind your alliance once, enable tracking, and the Change Log will keep joins, leaves, renames and rank changes together with governor IDs. It is available with Pro membership.