THE MANUAL LOOP
Another account. The same checks.
Open emulator → switch farm → inspect the game → run the task → wait → check again. Repeat for the next farm.
Viking Rise bot for PC. PRE-RELEASE
Run the routine.
Handle the exceptions.
Less switching farms. Less repeating tasks. VRA is being built to run your Viking Rise routines, check what actually happened and show you what needs attention.
In development for Windows + LDPlayer. Join for testing and launch updates. Free to join.
Join the conversation on Discord ↗26 current workflowsYour Windows PC + LDPlayerPer-farm routines & limits7-day free trial at launch
NOT A MOCK-UP. A REAL RUN.
Start troop training.
See it actually worked.
Follow the highlighted controls as VRA configures a troop batch, starts training and confirms the result. Short on-screen notes explain every step.
- 01Choose and configure
The highlighted troop and batch controls show exactly what VRA selects.
- 02Start normal training
Watch the blue Train button become an active queue. No instant-training purchase.
- 03Confirm and finish
The GUI records the completed action. The game’s training timer continues normally.
Actual single-action Lab validation, recorded 23 September 2026. Continuous screen recordings, presented at 2× speed with idle waits trimmed and explanatory annotations added; the final result plays at normal speed. Initial preparation is omitted. Account HUD, chat and developer internals are excluded. This shows the automation successfully starting training—not instant troop completion or a fleet reliability benchmark. Playback loops after you press play; pause at any time.
Explore all 26 action settingsOur product aim: The Viking Rise bot that can prove what it did, knows when to stop, and improves only with your permission.
See a verified farm run →Join the waitlist Explore the Product TourHOW IT FEELS TO USE
Routine work runs.
You keep control.
Choose the work once. Follow the outcomes. Investigate the exceptions instead of watching every emulator.
- 01
VRA runs the routine
Assign actions, schedules and limits to each farm. The same workflow engine powers validation runs and farm routines.
- 02
VRA checks the result
It looks for the expected game state. Starting a queue, having nothing to do and failing are different outcomes.
- 03
You handle the exceptions
Review the farm, result and available evidence when something needs attention. Uncertain effects can stop a repeat.
MORE FARMS. FEWER WINDOWS TO CHECK.
Manage the fleet.
Find the exceptions.
Different farms can keep different routines. One overview brings readiness, assigned work and attention together.
THE VRA APPROACH
See the work and what needs you.
Review your farms → run configured workflows → inspect outcomes → act on the exceptions.
Start with one farm and a small routine, then increase concurrency within your PC’s capacity. Longer concurrent runs remain under validation.
How schedules and farm capacity workIT DOESN’T JUST CLICK
A click is an attempt.
The result needs evidence.
In the healing example below, VRA started timed healing and checked the active queue. It did not mistake pressing Heal for finished troops.
- 01 / ACTIONStart normal healing
- 02 / OBSERVATIONRead the new game state
- 03 / VERIFICATIONCheck the active queue
- 04 / OUTCOMERecord what happened
Explore a completed healing action or an uncertain City Event attempt. These are two separate, sanitised development records, with original evidence—not a full routine or a reliability sample.
DEVELOPMENT EVIDENCE REPLAYTwo separate recorded cases · not live telemetry or an unedited video
Initial observed state
The Infirmary showed wounded troops and an eligible timed Heal control after ready city output was collected.
1 / 6
Completed21 September 2026
Read the complete text record
- Initial observed state
- The Infirmary showed wounded troops and an eligible timed Heal control after ready city output was collected.
- Teacher / workflow decision
- Use the deterministic healing workflow. Preserve existing work and exclude instant healing or premium spending.
- Action attempted
- Start normal timed healing, then request available tribe assistance.
- Expected result
- A new active healing queue, followed by an assistance acknowledgement and return to the city.
- Observed result
- Saved frames show the timed queue and the explicit assistance confirmation. The final frame is the city.
- Retry or stop decision
- No repeat Heal was needed after the active queue was verified.
This accessible replay is a sanitised transcription of retained development evidence, not a reconstructed live video. A reviewed, unedited 60–90 second recording can accompany it when available.
BUILT TO BE INSPECTED
Know what ran.
Know when to step in.
History you can use
See the observed state, attempted action, outcome and reason for stopping. Available captures help explain a problem without replaying every step yourself.
Explore VRA EvidenceLimits that remain yours
Choose supported spending permissions, resource limits and workflow policies. Recovery is bounded; an uncertain previous action is not permission to repeat it.
See the reliability approachRecognition with a purpose
Moving targets make fixed positions unreliable. Sector Vision is testing local recognition and tracking on real game captures. This is controlled development work, not a released autonomous model.
Inside Sector VisionScripts teach. Evidence verifies. VRA improves only with permission. How optional contribution works →
THE WORK YOU REPEAT
Build a routine
around your farms.
26 implemented workflows, each with its own checks, settings and limits. Some game variants remain under refinement; the reference explains which.
Rewards & errands
Check ready city output, mail, quests and tribe rewards.
Explore workflows ↗City & tribe
Set research and building priorities; preserve work already in progress.
Explore workflows ↗Troops & heroes
Configure training batches, healing and eligible free recruitment.
Explore workflows ↗Resources & protection
Choose gathering targets, march limits and which owned items to use.
Explore workflows ↗Exploration & dailies
Set boundaries for commissions, exploration and daily buildings.
Explore workflows ↗RECENTLY BUILT & TESTED
Follow the work.
See what is changing.
Development milestones with their limits attached. VRA is pre-release; these are not public releases or fleet reliability guarantees.
Sharper vision. Built for the living city.
VRA has completed the first internal milestone of its custom Sector Vision pipeline: focused visual recognition trained on reviewed Viking Rise captures. It brings moving animals and resource objects into the same perception layer, extending the work behind our core farming workflows.
What changed and what it provesMore deliberate inputs. Clearer control.
Alongside recognition, we have completed another pass on the machinery that turns a screen observation into a farm action: report entry, city recognition, navigation checks, update preparation and recoverable development tooling.
What changed and what it provesReal farm work. End-to-end action runs.
Since our last update, development has focused on running VRA against real farms, reviewing the screenshots and fixing what actually happens in-game. Successful end-to-end action runs now cover core farm growth, rewards, recruitment and march workflows—not just opening the right menu.
What changed and what it provesTHE VRA COMMUNITY / DISCORD
Watch the build.
Help shape what’s next.
See real VRA demonstrations, follow development updates and talk through the farm jobs you want off your hands.
- Real recordings and build updates
- Questions, setup discussions and shared experience
- Your ideas for better farm routines
Free to join. Discord and the email waitlist are separate; neither guarantees a beta place.
A real run. A visible result.Recorded development test · Watch the 12-second demonstrationGO AS DEEP AS YOU LIKE
The detail is here
when you need it.
Explore the real interface, inspect the reliability method or work through the support Wiki. The technical detail stays available behind every product claim.
BEFORE YOU JOIN
A few clear
answers.
Can I download VRA today?
Not yet. Viking Rise Automation is pre-release and not publicly downloadable. The beta list is for development, testing and launch news; joining does not guarantee a place or a release date.
Will I need to share screenshots?
No. Dataset contribution will be optional, default-off and separate from your licence and email subscription. If you opt in, VRA will handle eligible example collection during normal use. You will not need to prepare screenshots or train a model. Declining will not reduce core farm automation.
Does the model learn live from my account?
No. Teacher-guided development uses structured examples and offline evaluation. A customer action does not immediately retrain a model or change its control permissions. Models do not get to authorise their own spending or retries.
What will the trial cost?
The launch trial will be free for seven days when access opens. Joining now does not start the trial. Continued-use pricing will be published before trial activation. No final price or per-farm pricing model has been announced.
Is VRA official or safe from bans?
IGG’s terms prohibit bots and automation software. Using any Viking Rise automation can result in restrictions, suspension or account termination. VRA cannot make automation risk-free or guarantee protection from enforcement. Young Studio is independent of IGG and Viking Rise.
Understand the account risk.
IGG’s terms prohibit bots and automation software. Using any Viking Rise automation can result in restrictions, suspension or account termination. VRA cannot make automation risk-free or guarantee protection from enforcement.
Read IGG’s official terms Independent software by Young Studio. Not affiliated with or endorsed by IGG or Viking Rise.Ready to follow the build?
Real demonstrations. Practical setup guidance. News when the seven-day launch trial opens.