One attempt per map changes the price of a mistake
In the endgame a map closes when you die. Not "you lost some experience" but "the map is over", and everything invested into it goes with it.
That makes the request very different from a shooter:
- the whole map beats any help in a fight: routes are planned before entering, not inside;
- dangerous modifiers and rare enemies are visible early, and can simply be avoided;
- scripts remove routine where no decisions exist rather than where they do;
- the gain is measured in time: not "won", but "twice as many maps in an evening".
The first game lives on its own page, and the software is not shared. Those are different clients rather than two modes of one game.
What it does not do
It does not touch drop rates. The odds stay exactly where the developer set them, and claiming otherwise would be a lie.
It also does not hide you. Automation shows in how a character behaves, so running it in crowded places is a poor idea.
The developer’s rule is simpler than it looks
The game installs no kernel driver, and the hunt is for behaviour rather than files. GGG draws the line at automation: one key press, one action. The moment a program repeats actions on a timer or makes decisions for the player, it crosses that line.
One practical thing follows. A script that makes your own work faster and a script that plays instead of you are different things to the developer. The second is caught in server logs.
What comes inside
The range in this niche is narrow, and the choice is not made by counting features:
- Map only. ESP for the zone: exits, chests, bosses.
- Map with scripts. Automation of repeating actions joins in.
- Full menus. Item, movement and build-specific sections.
The choice is not about power but about how much routine goes. The more of it does, the less the character behaves like a person.
Questions that come up most
Will software for the first game work here? No. That is a different client, and builds for it do not run.
Does software change drop chances? No. The odds live on the server, and a local program does not touch them.
Where does the game draw the line? At automation: one key press, one action.
Why did the build stop working after a league start? A new league arrives with a patch, and a patch moves memory structures. The software needs an update.
