Who to farm
Select heroes, queue order and target ranks.
AutoFarmer collects hero gear without manually walking through heroes, shops, missions, mail and energy bottles. It creates a plan, checks missing items, respects limits and only then sends requests.
AutoFarmer is available in two channels:
hwhauto.user.js.hwhauto-beta.user.js, version 1.8-beta.2.The beta channel is used to test the new planner, fast farming modes, result panel and UI fixes before stable rollout. Do not enable stable and beta at the same time: both scripts see the same account and can try to process the same resources.
Install options are direct .user.js download from the script page, GitHub raw and GreasyFork for the stable channel. Details: release channels.
Select heroes, queue order and target ranks.
Create an item map with sources, crafts and missing components.
Control energy, mail, bottles, gold and shop currencies.
The Auto Farm button opens in the main menu or in the More section, depending on settings. The script window is divided into several tabs:
Do all, export/import.Each tab contains accordions with parameter groups. Settings search works across the entire page — type part of a word, irrelevant blocks hide.
Auto Farm.Start farming and read the result window.Do not start with the whole account. One hero and one rank are enough to see how the script plans spending, which sources it uses and which limits block actions.
Heroes higher in the list receive resources first. Lower heroes may be skipped when resources run out.
The map shows required components, their sources and craft chains.
The final report shows purchases, raids, crafts and limits that stopped actions.
This defines who receives gear. Queue order matters: the hero higher in the list gets resources first. When sequential farming is enabled, the next hero starts only after the previous one is processed.
How to configure:
Practical advice: do not place every hero into one giant queue. Split heroes into groups: main team, secondary heroes and experiments. It is much easier to understand why resources went somewhere.
The item map shows missing items and their sources. It also helps with duplicates, craft chains and parallel goals. Treat it as the main control surface, not as a decorative table.
What the map shows:
If the map shows an unexpected item, check the target rank and the current hero slot. The “extra” item is usually part of a craft chain.
The script calculates how many items can be obtained through raids and sends requests in batches. Batch size and delay settings keep the game from being hammered too hard.
Raid settings:
If farming feels slow, increase the batch size carefully. If the game starts returning errors or reports become empty, move the value back. Faster is not automatically smarter, shocking news.
AutoFarmer checks allowed shops and buys only items useful for current goals. Currency reserves block purchases that would leave the balance below the configured limit.
Which shops AutoFarmer checks:
For events and heroes you are saving currency for, set a higher reserve. The script knows numbers, not your brilliant plan for tomorrow.
The script can craft available items and equip them. Rank-up runs only when all conditions pass, not when things are “almost there, surely fine”.
Order of actions:
Enable auto rank-up after a test run. If you only want to prepare gear, leave equip and rank-up disabled.
AutoFarmer can use energy purchases, bottles, mail, daily quests and energy boxes. Each source has separate controls, so one careless field does not empty the whole storage.
Available sources:
Limit 500-energy mail separately. It is event fuel, and spending it in one run is extremely easy when the field is too generous.
AutoFarmer can add its action to the shared Do all list. Position is configurable: do not add, start, end, before another action or after another action.
For daily runs, place AutoFarmer after tasks that refresh account state, but before manual checks. That makes the result report closer to reality.
Controls the order of raids, purchases, crafting and equipping.
Protect gold, shop currencies, energy, bottles and mail.
Control execution speed and pressure on the game.
When event hero priority is enabled, AutoFarmer detects the event target type first. A hero gets priority, while a titan blocks the run: hero farming under a titan event is not treated as normal behavior.
Each resource has its own limit. The script will not spend more than the reserve allows:
Settings are stored in browser localStorage. To transfer them to another browser or make a backup:
Export — copy the JSON from the field.Import.A backup is useful before major changes: if something goes wrong, you can roll back.
Do all — AutoFarmer executes in the shared queue.Check that a hero is selected, the target rank is higher than the current one, energy sources are enabled and reserves do not block every action.
Check allowed shops and currency reserve. If a purchase breaks the reserve, it will be skipped.
Usually the target is already reached, resources are insufficient or the selected mode does not allow the needed source.
Reduce the batch size and increase the delay. If the game is timing out, the server might be overloaded — try again later.
Check energy source settings. Energy purchase for emeralds might be enabled, or the mail limit is too high.
Do not run AutoFarmer during an important event if you do not understand which currencies are needed tomorrow. The script can respect limits, but it cannot read the account owner’s mind. Yet.