Skip to content
Help and guidesSVTSVT

Help and guides

Find your next step: from starting with your alliance to turning its data into useful information.

Using DWS Stats

Guides found: 12

Video or screenshots, the same result

Choose how to provide the game screens. Then review the data and decide when to save it to history.

Screenshots

Choose images from your gallery. You can include different screens; the app organises them into batches by type and period.

Choosing images starts the upload and, when connected, AI reading. There is no prior credit confirmation as there is for video.

Video

Record your way through the screens. The app selects the images it needs to read; it does not treat the whole video as one screenshot.

Before using AI, review the thumbnails: remove proposals or choose alternatives. You will see the total and credits before confirming. Check the date using the time zone saved in your account; if your device provides a generic name, we do not invent another one. Keep this page open while uploading; processing then continues on the server. Additional readings also need your confirmation.

From the game to history

  1. Prepare and uploadInclude every required row or detail, with legible text and figures.
  2. Review the dataAI extracts and organises it. Check the period and resolve any questions highlighted by the app.
  3. Save to historyUploading or finishing the reading does not save results to history on its own: your confirmation is still needed.

How to take each screenshot

The diagrams are illustrative. Where an Example button appears, you can open a real screen with identifiers replaced. Take clear, consecutive portrait screenshots without covering the header or active tab.

Members

Anonymous diagram of a multi-row member list

Members example

Real game screen. Only in this example, names, avatars and identifiers have been replaced; the game figures are preserved. In your files, keep names and required fields visible so the data can be linked.

View full-size image (new tab)
Real Members screen with identifiers replaced for the example
Game language in this image: Spanish.
Where
Alliance › Members.
What must be visible
The Members tab, complete order, and rows with name, rank, level, power and IND.
Video
Record from the beginning to the end of the list, scrolling without skipping rows. Keep text and figures legible as you move and show the last row.
Screenshots
Start at the top and take consecutive screenshots through the last row without skipping any. Rows may overlap between images; every row must be fully visible at least once.
Where
Alliance › Members.
What must be visible
The Members tab, complete order, and rows with name, rank, level, power and IND.
Screenshots
Start at the top and take consecutive screenshots through the last row without skipping any. Rows may overlap between images; every row must be fully visible at least once.
Video
Record from the beginning to the end of the list, scrolling without skipping rows. Keep text and figures legible as you move and show the last row.
Suggested period
The screenshot day in server time.

Avoid

  • Starting halfway down the list.
  • Skipping rows between screenshots.
  • Capturing the Alliance or Administration tab.

Alliance Duel (VS)

Anonymous diagram of a weekly VS ranking with six bars

Alliance Duel (VS) example

Real game screen. Only in this example, names, avatars and identifiers have been replaced; the game figures are preserved. In your files, keep names and required fields visible so the data can be linked.

View full-size image (new tab)
Real Alliance Duel (VS) screen with identifiers replaced for the example
Game language in this image: Spanish.
Where
VS › Ranking › Duel week.
What must be visible
The closed week, ranking tab, positions, names and scores.
Video
Record from the beginning to the end of the list, scrolling without skipping rows. Keep text and figures legible as you move and show the last row.
Screenshots
Start at the top and take consecutive screenshots through the last row without skipping any. Rows may overlap between images; every row must be fully visible at least once.
Where
VS › Ranking › Duel week.
What must be visible
The closed week, ranking tab, positions, names and scores.
Screenshots
Start at the top and take consecutive screenshots through the last row without skipping any. Rows may overlap between images; every row must be fully visible at least once.
Video
Record from the beginning to the end of the list, scrolling without skipping rows. Keep text and figures legible as you move and show the last row.
Suggested period
For a full week, capture the closed VS on Sunday SVT: it belongs to the ISO week containing that Sunday. The game removes the ranking at 00:00 SVT on Monday; VS has no grace hour.

Avoid

  • Using a daily ranking that is still open.
  • Hiding the heading that identifies VS.
  • Mixing weeks in one batch.

Contribution

Anonymous diagram of a contribution table

Contribution example

Real game screen. Only in this example, names, avatars and identifiers have been replaced; the game figures are preserved. In your files, keep names and required fields visible so the data can be linked.

View full-size image (new tab)
Real Contribution screen with identifiers replaced for the example
Game language in this image: English.
Where
Alliance › Ranking statistics › Contribution.
What must be visible
The Contribution tab and complete rows with values.
Video
Record from the beginning to the end of the list, scrolling without skipping rows. Keep text and figures legible as you move and show the last row.
Screenshots
Start at the top and take consecutive screenshots through the last row without skipping any. Rows may overlap between images; every row must be fully visible at least once.
Where
Alliance › Ranking statistics › Contribution.
What must be visible
The Contribution tab and complete rows with values.
Screenshots
Start at the top and take consecutive screenshots through the last row without skipping any. Rows may overlap between images; every row must be fully visible at least once.
Video
Record from the beginning to the end of the list, scrolling without skipping rows. Keep text and figures legible as you move and show the last row.
Suggested period
The week shown by the game; a screenshot from 00:00 to 00:59 SVT on Monday may belong to the previous week.

Avoid

  • Confusing contribution with power.
  • Cropping the value on the right.
  • Changing order between screenshots.

Power breakdown

Anonymous diagram of a circular power breakdown
Where
Player profile › Power › Details.
What must be visible
Name, total power and every component: building, technology, troop, hero, vehicle and pet.
Screenshots
Open Details for each member and capture their name, total power and every component. If they do not all fit, scroll and add the remaining images.
Video
Open Details for each member while recording. Show their name, total power and every component; scroll only if the full content does not fit.
Suggested period
The screenshot day in server time.

Avoid

  • Cropping the name or total.
  • Leaving out a component.
  • Uploading the summary instead of Details.

Player profile

Anonymous diagram of a player profile
Where
Avatar › Player profile or settings.
What must be visible
Name, full UID, server and headquarters level.
Screenshots
Capture the full screen with every required field. There is no need to scroll if all the information is already visible.
Suggested period
No period; this verifies your player.

Avoid

  • Covering or cropping the UID.
  • Uploading someone else's profile.
  • Sharing the image outside the verification flow.

Power ranking

Anonymous diagram of a power podium
Where
Ranking › Player power.
What must be visible
Tab and server scope, positions, names and power.
Screenshots
Start at the top and take consecutive screenshots through the last row without skipping any. Rows may overlap between images; every row must be fully visible at least once.
Video
Record from the beginning to the end of the list, scrolling without skipping rows. Keep text and figures legible as you move and show the last row.
Suggested period
The screenshot day in server time.

Avoid

  • Capturing a different event ranking.
  • Mixing servers.
  • Skipping positions while scrolling.

Frankie

Anonymous diagram of a damage ranking
Where
Frankie event › Damage ranking.
What must be visible
Event name, completed phase or edition, and full ranking.
Screenshots
Start at the top and take consecutive screenshots through the last row without skipping any. Rows may overlap between images; every row must be fully visible at least once.
Video
Record from the beginning to the end of the list, scrolling without skipping rows. Keep text and figures legible as you move and show the last row.
Suggested period
The closing day of the edition shown.

Avoid

  • Capturing before the edition ends.
  • Confusing personal damage with alliance ranking.
  • Cropping the phase.

Zombie Siege

Anonymous diagram of a shelter and Zombie Siege ranking
Where
Zombie Siege › Ranking.
What must be visible
Completed edition, positions, names and scores.
Screenshots
Start at the top and take consecutive screenshots through the last row without skipping any. Rows may overlap between images; every row must be fully visible at least once.
Video
Record from the beginning to the end of the list, scrolling without skipping rows. Keep text and figures legible as you move and show the last row.
Suggested period
The closing day of that edition.

Avoid

  • Using provisional results.
  • Hiding the event name.
  • Mixing two editions.

Black Gold Battlefield (BGB)

Anonymous diagram of two alliances in a BGB battle ranking
Where
BGB › Battle Ranking.
What must be visible
Battle day, both alliances, exact tags, player names and scores.
Screenshots
Start at the top and take consecutive screenshots through the last row without skipping any. Rows may overlap between images; every row must be fully visible at least once.
Video
Record from the beginning to the end of the list, scrolling without skipping rows. Keep text and figures legible as you move and show the last row.
Suggested period
The battle day in server time.

Avoid

  • Hiding a row tag: it is required to distinguish the two alliances.
  • Leaving out your own rows; usually 2 to 5 screenshots are needed.
  • Mixing different battle days.

Alliance power

Anonymous diagram of an alliance power ranking
Where
Server ranking › Alliance power.
What must be visible
Server, positions, tags, names and power for each alliance.
Screenshots
Start at the top and take consecutive screenshots through the last row without skipping any. Rows may overlap between images; every row must be fully visible at least once.
Video
Record from the beginning to the end of the list, scrolling without skipping rows. Keep text and figures legible as you move and show the last row.
Suggested period
The screenshot day in server time.

Avoid

  • Capturing only the top alliances.
  • Cropping tags or figures.
  • Mixing servers.

VS + Survival Preparation guide

A routine for saving resources and spending them when the daily VS task matches the Survival Preparation objective.

Game rules and rewards can change. Always check the in-game calendar and wording before spending resources.

Principles

  • Save fragments, speedups, radar tasks, cores and chests for the VS day when they score.
  • Improving the Duel branch and Quinn's third skill increases points for the same actions; verify current values in the game.
  • Before starting, check the active Survival Preparation objective and the next time slot.
  • Aim for the last VS chest without spending resources that score better on another day.

Survival Preparation

  1. Wait for the objective matching that day's VS actions.
  2. Reach the third chest without going far beyond the threshold shown by the game.
  3. If Replace is available, it can reset or bring forward an objective once a day; confirm the on-screen conditions.
  4. For a Training round, leave completed troops uncollected, collect them while the objective is active, then train again.

Monday-to-Saturday plan

Monday · Shelter Development

VS: Finish buildings and research; use precise components, medals and scoring speedups. Do not collect gold if the screen says it does not score.

Preparation: Combine Research Technologies, Build the Shelter and Train Units according to the calendar.

Tuesday · Cultivate Heroes

VS: Use advanced recruitment, hero fragments, exclusive gear and radar tasks when they score.

Preparation: Match Cultivate Heroes to planned spending and save Train Units for its time slot.

Wednesday · Keep Progressing

VS: Escort an S truck, complete Shadow Action, train or promote units, and use cores or chests when they score.

Preparation: Alternate Train Units and Armament Expert according to the calendar.

Thursday · Armament Expert

VS: Open chip boxes; use gears, titanium, blueprints, cores and speedups; complete radar and zombies if they score.

Preparation: Spend the resource that reaches the threshold with least excess first, then reassess before Replace.

Friday · Comprehensive Development

VS: Combine hero, vehicle, building, research and training upgrades only where they score.

Preparation: Choose Cultivate Heroes or Armament Expert based on reserves; do not force an objective that harms next week.

Saturday · Defeat Enemies

VS: Shadow Action, S trucks, allowed speedups and rival units under the current KE rules.

Preparation: The legacy guide recommends saving ordinary resources for Monday to Friday; check whether the current calendar offers a useful match.

Content checked against the Spanish, English and Portuguese versions of the legacy FÉNIX guide. It has been rewritten as native content without copying its HTML, images or scripts.