Food, lumber, stone and gold: decide what you need
A resource plan begins with the material you intend to obtain. In VRA’s gathering configuration, resource choice is separate from search level, territory filters and march limits. Inventory resources and city objects are handled through their own workflows rather than assumed to be world-map deposits.
Avoid evaluating performance from a stockpile number alone. A farm may spend resources on research or construction during the same routine. A recorded search, eligible target and squad departure explain gathering activity more directly than an unexplained before-and-after total.
World-map gathering needs an available march
An auto-gather workflow must navigate to the search controls, locate an eligible deposit, choose a squad and verify that a march actually starts. Resource availability, distance, territory, troop availability and occupied march slots can all affect the result.
VRA’s development catalogue supports configured resource searches and march boundaries. If the requested search is unavailable, it should not silently substitute an unrelated level or target. A route that opens correctly but never dispatches is not a successful gather.
City errands and inventory are separate resource paths
City Event Reports can direct the camera toward an animal or material object. Pressing Go identifies a destination; it does not necessarily start collection. A moving animal may also leave the original marker position before input arrives.
The expanded visual-recognition experiment includes berries, ore, timber, material piles, deer and sheep. It remains under controlled validation. Separately, Use Inventory works with configured owned resource categories; consuming a bag item is not the same event as sending a gathering squad.
When gathering appears idle, inspect the state first
Check whether squads are already gathering, returning or otherwise occupied. Then inspect the selected resource, available search level and first unexpected screen. Repeating the entire action without reconciling a possible departure can create confusion about what actually happened.
A useful test record pairs the chosen configuration with the visible target and resulting march. Long travel or gathering timers should not be treated as a requirement to wait for all resources before the routine continues.
- Record the requested resource and level.
- Check available troops and march slots.
- Verify departure rather than a successful button press alone.
- Keep already-running and newly-started gathering separate in the result.
Viking Rise automation questions
Does auto gather include berry bushes and animals inside the city?
Not necessarily. World-map gathering and City Event collection are separate workflows in VRA. Their controls, prerequisites and verification differ.
Can VRA guarantee a resource amount per hour?
No. Travel, game state, available squads, selected actions and remaining validation work affect outcomes. No representative production resource-per-hour figure is published.
Why can a completed gather action still show troops travelling?
An immediate automation goal can be to start the correct march. Travel and collection then continue in the game; successful dispatch does not mean the entire gathering timer finished.