Skip to content
EN

HWH AutoFarmer

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:

  • Stable - normal daily channel, hwhauto.user.js.
  • Beta 2 - testing channel, 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.

Who to farm

Select heroes, queue order and target ranks.

What to find

Create an item map with sources, crafts and missing components.

What to spend

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:

  • Heroes — hero selection, queue order, target ranks.
  • Map — visualization of missing items, sources and crafting.
  • Raids — mission farming settings, batch size, delay.
  • Shops — allowed shops, item types, currency reserves.
  • Energy — energy sources: purchase, bottles, mail, quests, boxes.
  • Craft — auto-craft, auto-equip, auto-rank.
  • Settings — interface, farm mode, 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.

  1. Open Auto Farm.
  2. Go to the Heroes tab.
  3. Select one hero from the list.
  4. Set one close target rank.
  5. Go to the Energy tab and configure gold, energy, bottle and mail reserves.
  6. Press 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.

1. Queue

Heroes higher in the list receive resources first. Lower heroes may be skipped when resources run out.

2. Item map

The map shows required components, their sources and craft chains.

3. Report

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:

  1. Open the Heroes tab.
  2. Check the heroes you want.
  3. Drag heroes into the desired order: top hero goes first.
  4. For each hero, select a target rank from the dropdown.
  5. If “one at a time” mode is enabled, the script processes each hero fully before moving to the next.

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:

  • Missing items — what is needed for the target rank.
  • Sources — where to get them: raids, shops, crafting.
  • Craft chains — which components are needed to craft an item.
  • Duplicates — items already in inventory but not equipped.

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:

  • Batch size — how many raids per pass. More = faster, but higher error risk.
  • Delay — pause between batches in milliseconds. Do not go below 500 unless you want trouble.
  • Mission priority — which missions to farm first.

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:

  • Guild shop
  • Hero shop
  • Titan shop
  • Pet shop
  • Daily offers
  • Event special shops

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:

  1. The script checks which items can be crafted from available components.
  2. Crafts them.
  3. If auto-equip is enabled — equips them on the hero in the correct slot.
  4. If all items for the rank are collected — raises the rank.

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:

  • Energy purchase — spends emeralds on extra energy.
  • Energy bottles — uses bottles from inventory.
  • Mail energy — collects energy from mail.
  • Daily quests — collects quest rewards.
  • Energy boxes — opens boxes from inventory.

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.

Farm mode

Controls the order of raids, purchases, crafting and equipping.

Reserves

Protect gold, shop currencies, energy, bottles and mail.

Request batches

Control execution speed and pressure on the game.

  • Raids → Shops → Craft → Rank — standard order. Farm first, buy second, craft third.
  • Shops → Raids → Craft → Rank — when shops matter more, like during a sale.
  • Normal mode — keeps target order and follows the plan without jumping to the closest fragment.
  • Fast mode — farms gear with the smallest missing fragment count first, while still respecting hero queue and priorities.
  • Craft only — when items are already collected, just need to craft and equip.
  • Rank only — when everything is ready, just raise the rank.

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:

  • Gold — base currency for crafting and raids.
  • Energy — needed for raids.
  • Bottles — alternative energy source.
  • Mail — another source, but limited.
  • Shop currencies — guild coins, titan stones and more.

Settings are stored in browser localStorage. To transfer them to another browser or make a backup:

  1. Open the Settings tab.
  2. Click Export — copy the JSON from the field.
  3. On another browser, open the same settings, paste the JSON and click Import.

A backup is useful before major changes: if something goes wrong, you can roll back.

  • One hero in queue.
  • Raids before shops.
  • Gold reserve above daily planned spending.
  • Shop currency reserves enabled when saving for a hero or event.
  • Only a few bottles and mail rewards for the first test.
  • Auto craft enabled; auto rank-up only after checking the first report.
  1. Open the game in the morning, refresh the page.
  2. Run Do all — AutoFarmer executes in the shared queue.
  3. Check the report: what was farmed, what was bought, what remains.
  4. If there is an event — raise currency reserves before running.
  1. 2-3 days before the event, raise all currency reserves.
  2. Leave only raids enabled, disable shops during accumulation.
  3. After the event, return to normal settings.
  1. Split heroes into groups of 3-5.
  2. Run AutoFarmer for each group separately.
  3. Check resource remainders between runs.
  4. Do not enable auto-rank for the entire group at once — one hero at a time.

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.