# DoroHelper: automating NIKKE daily tasks with AutoHotkey > DoroHelper is an AutoHotkey v2 script that clears the daily errands of Goddess of Victory: NIKKE on the PC client, from shop purchases and arena runs to inbox and mail collection. The README now points most new users at MDA, a rewrite built on MaaFramework, and marks the AutoHotkey version as finished. **1204244136/DoroHelper** — Nikke日常任务脚本。A Time-Saving Script for Goddess of Victory: Nikke. - Repository: https://github.com/1204244136/DoroHelper - Stars: 859 · Forks: 49 - Language: AutoHotkey - License: AGPL-3.0 - Published: 2026-10-20 · Updated: 2026-10-20 · Language: en - Canonical page: https://hysenlabs.com/projects/1204244136-dorohelper ## A daily errand bot for Goddess of Victory: NIKKE DoroHelper is a Windows script written for one game, Goddess of Victory: NIKKE. The README describes it as a PC side helper for clearing daily tasks in one click, with each step selectable and executed in order, and it states that every client is supported except the Chinese server. The list of what it handles is long and entirely mundane, which is the point. In the paid shop it collects the free jewellery and the free gift packs. In the normal shop it takes the two free daily purchases, buys the chip dust box with credits, and buys the profile pack. The arena shop gets the attribute skill books, the code manual chest, the profile pack and the company weapon furnace. Beyond the shops it runs the simulation room, including the overclock variant when quick simulation is unlocked, and it works through the arena tiers, the infinity tower runs, and both normal and abnormal interception battles. It also collects the regular rewards: dispatch missions, affection consultations, friend points, the mail box, mission rewards, the battle pass, co-op operations and the solo assault dailies. The final group is the useful tools section, which covers story mode with automatic option clicking, a debug mode that calls a chosen function directly, a burst mode that opens the burst screen faster than the automatic route, and a push mode that plays main story stages for you. ## Running it: AutoHotkey V2, or the packaged executable The README offers two ways to run the tool, and the first is the one it recommends. Running the script from the repository means downloading the whole project as a zip from the green code button, installing AutoHotkey V2 from the official download, leaving the default installation path alone, and then launching DoroHelper.ahk as administrator. The administrator requirement is not incidental, since the script drives a full screen game client and needs input rights that a normal session does not have. The second route is the release build: download the exe from the releases page and run it as administrator. That skips the AutoHotkey installation entirely, at the cost of trusting a binary you did not build. The actual sequence in game is short. Start the NIKKE launcher, press start, and wait until the main program shows the SHIFT UP logo in the centre of the screen. Then switch to the script and press the DORO button. If the mouse starts clicking repeatedly in the lower left corner, the run has started. The README suggests making a coffee at that point. There is also a second entry point: if you are already in the lobby, on the page with the character standing in front of the board, you can switch over and press the same DORO button without going through the launcher. ## The escape hatch you need to know about The disclaimer section is the most useful part of the README for anyone actually running the script, and it is unusually blunt about two things. The first is that the program can become incompatible with the game and behave in ways that are not what you intended. The advice is to watch it the first time you use it, to stand next to the screen rather than to leave the room. The second is the panic control. If Doro misbehaves, Ctrl + 1 ends the process and Ctrl + 2 pauses it. Those two shortcuts are the difference between a misclicked script and a frozen machine, and they are the reason to read this section before the first run rather than after it. The disclaimer also states that using any script program carries a risk of the account being banned, and that users should be careful. That is a statement about the terms of service of a commercial game rather than about this project, and it is the reason to read the current rules of the publisher before you automate anything. A related instruction asks users not to publish modified builds of the software for the Chinese server in public places, and the project is described as being for personal study and research, with commercial use explicitly prohibited. ## Three lineages of the same idea, and where each one ended up The README contains a project evolution chart that is worth reading carefully, because it explains the current state better than a paragraph could. The first line is the NIKKE-scripts route, an emulator based project that ran from 2023-02-05 through version 1.2.22 on 2025-06-19. The chart marks its end as coming from official action against the emulator, and labels the project as no longer maintained. The second line is the NKAS line. An independent daily script appeared on 2023-04-30, was updated outside its main GitHub repository, and stopped when its author ran out of energy. The chart then points to a successor, megumiss/NIKKEAutoScript, described as a spiritual continuation that is still actively maintained, and it notes that a separate classic branch, DoroHelper_classic, is still maintained by kyokakawaii. The third line is the one this repository belongs to. DoroHelper was created on 2024-07-16 by kyokakawaii, reached version 0.1.16.1 in January 2025, and was handed over in April 2025, with version 1.15.8 on 2026-05-11 marked as the final version and the repository as archived. The history is therefore a record of three separate efforts at the same task, each ending when the author moved on. That is worth knowing before you invest an evening in a script. ## MDA is where the active development went The README announces that DoroHelper has been fully upgraded into MDA, Maa Doro Assistant, and gives the reason plainly: the architecture of the current script had become old and limited further feature work and long term maintenance. The rewrite is built on MaaFramework, an existing community tool, which the author says will make fixing problems and updating content more efficient and stable. The listed improvements are substantial. A new interface, simpler to look at, with native support for multiple languages and free choice of theme, colours and background. Reordering of tasks, with a much larger set of detailed configuration options. Support for running the game in the background. Support for all display resolutions instead of being tied to a particular one. And support for Linux, macOS and aarch64 architectures, which the AutoHotkey version never had. Downloads for MDA are listed on GitHub releases, Baidu netdisk and Quark netdisk, each with its extraction code. The old version is stated to be no longer maintained but still usable, and the README says the choice is yours if the new one does not suit you. The migration is also why the state of this repository should be read carefully: the last push was on 2026-08-26 and the most recent tags are v1.15.10 from 2026-05-25 and v1.15.8 from 2026-05-11, which is a project receiving occasional commits rather than active feature work. ## What the script is built on The repository is small and flat. It contains DoroHelper.ahk as the main entry point, an icon file, and directories for libraries, icons, images, groups and an expired folder, which suggests the project keeps both its dependencies and its historical assets under version control. The README has a borrowed components table listing two libraries: an API collection for AutoHotkey V2 from a GitHub repository, and FindText for AHK V2 from the AutoHotkey boards. FindText is the routine that finds text on screen, which for a game script is how the tool locates buttons, and the AHK v2 port matters because the original release is written for the v2 language. The acknowledgements list M9A from the MAA1999 organisation as a code reference, which connects the project to the same MaaFramework ecosystem that MDA now builds on. The licence is AGPL 3.0, which is the strongest copyleft in common use and carries obligations that matter if you distribute a modified build. The README states the project is for personal study and research only and forbids commercial use, which is a statement by the author rather than a licence term, and it asks that content elsewhere on the internet about the project not be treated as published by them. For feedback there is a QQ group and a Discord server, both linked from the README. ## Is this the right tool for you The honest answer splits on what you need. If you play the PC client daily and the errands take you twenty minutes of clicking, DoroHelper does exactly that and stops there. There is no configuration surface to learn beyond choosing which steps to run, no framework to install beyond AutoHotkey, and no accounts or APIs to configure. For a Windows user who wants a one click answer to the daily chore list, that is a reasonable deal. If you want the tool to keep working as the game changes, or you are not on Windows, or you want tasks to run while the game is in the background, then MDA is the version to look at, and the README is explicit that the old script will not be maintained. Three things make this a decision with a cost attached. The automation runs against a commercial game, and the author states plainly that any script carries a risk of account sanction. The client region is restricted, with the Chinese server excluded. And the script needs screen access, so it competes with whatever else you do on that machine while it runs. The sensible order is: read the current rules of the publisher, decide whether the risk is acceptable, try the version that matches your platform, and run the first session where you can watch the screen and where Ctrl + 1 is within reach. ## Conclusion DoroHelper still makes sense if you already run it, or if you want the small AutoHotkey approach on a Windows machine without installing a larger framework, since the script does the errands list and nothing else. New users should look at MDA instead, because the README states that the AutoHotkey architecture had become a limit on further development and that the rewrite is where active maintenance moved. Whatever you choose, verify first that your client region is supported, since the README excludes the Chinese server, and run the tool where you can see the screen, because the author warns that automation can misfire and that using any script carries a risk of the account being sanctioned. ## FAQ ### What does DoroHelper automate in Goddess of Victory: NIKKE? It clears daily errands in one pass, including the paid and normal shops, the arena shop, the simulation room, the arena tiers, the infinity tower, interception battles, regular reward collection, the battle pass and mail, plus story mode, burst mode and a push mode for main story stages. ### How do I run DoroHelper? Either download the repository, install AutoHotkey V2 without changing the default install path and run DoroHelper.ahk as administrator, or download the release executable and run it as administrator. The README says to use the script from the repository. ### What happens if the script misbehaves? The README warns that the program can become incompatible with the game, advises watching it during the first use, and states that Ctrl + 1 ends the process while Ctrl + 2 pauses it. ### Is DoroHelper still maintained? No. The README says the old version has stopped being maintained, that the project was rewritten as MDA on MaaFramework, and that the AutoHotkey version remains usable if the new one does not suit you. ## Sources - [1204244136/DoroHelper on GitHub](https://github.com/1204244136/DoroHelper) - [Issues](https://github.com/1204244136/DoroHelper/issues) - [License: AGPL-3.0](https://github.com/1204244136/DoroHelper/blob/main/LICENSE) - [README](https://github.com/1204244136/DoroHelper/blob/main/README.md) - [Releases](https://github.com/1204244136/DoroHelper/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/1204244136-dorohelper