NRBot is an image recognition based bot for NieR Re[in]carnation. NRBot is based on Airtest framework (Python).
It currently only support English UI. Main goal of NRBot is to automate repetitive content in the game where a simple macro won't suffice.
- Install emulator with adb support (e.g. LDPlayer 64bit). Use 1080x1920 mobile resolution.
- Turn on adb: Settings -> Other settings -> ADB Debugging -> Open remote connection
- Install AirtestIDE. Extract it to your favorite path.
- Download ADB (e.g. from here) and add it to your system path.
- Copy
settings.default.jsonctosettings.jsoncand update config. Refer to comments for instructions. - Make sure you already set up proper team for the quests in game.
- Run
python NRBot.py <script_name>in this directory. Here<script_name>can be any of the following:resetfarming: farms purple grade item in daily dark lairs by resetting if no drop.darkdaily: clears all specified daily dark lairs.dungeon: farms specified dark dungeon for memoirs.arena: battles in arena.
Requirement: Position the game at Mama's room, or the dark memory quests page.
Action: Constantly reset on specified quests and look for purple items. It will try up to the specified attempts for each character and difficulty selected. In settings, you can make the bot save a screenshot for each time when it quits. You can review the screenshots to confirm if the bot is recognizing correctly.
Note: After reviewing the screenshots, you can count then discard them by running python CalcStats.py. It will accumulate data into stats.json. So you can track your progress over time. When you found incorrectly recognized screenshots, you can upload them to issues.
Requirement: Position the game at Mama's room or the dark memory quests page.
Action: Loop through all daily dark lair quests. You can specify which quests to farm for each character (make sure you have unlocked them). The bot will attempt configured quests and skip if the quest has been already cleared.
Requirement: Position the game at Mama's room.
Action: Loop through specified Dark dungeons to farm memoirs.
Requirement: Position the game at Mama's room or the arena page. (Currently only support refuel using gems.)
Action: Repeatedly battle in arena. It chooses opponent 1-3 in turns to avoid keep losing to very strong opponent. The bot use a very simple strategy, where it just spam tapping skills and focus. Due to spamming, it won't focus very well (it keeps going on and off). In settings, you can make the bot save a screenshot for each battle. You can review the screenshots for its performance.
Disclaimer: This strategy is not as good as manual play. It is very good at tapping skills, but very dumb on choosing targets. I arrange my team as (1) high-AGI high-ATK long-CD EX Gayle (2) mid-AGI short-CD sword unit (3) low-AGI high-ATK short-CD greatsword unit. The idea is to AA kill a unit, hopefully get another AA out, then use 4 short CD skills to kill the rest. (Short-CD means CDR set + 2 EX sub weapons.) Enemy counters AA or high AGI AA kills can cause loses. This is good enough for me to auto farm coins, YMMV.
Note: After reviewing the screenshots, you can count then discard them by running python CalcStats.py. It will accumulate data into stats.json. So you can track your win rate over time.
- Handle failure / crash for dungeon runs.
- Fix EX Akeha resetfarming cannot pause issue.
- Add a limit to gem replenishes. Support BP potions.
Some actions can be easily achieved using emulator built-in macro recording. Examples:
- Auto repeat any 10x loops: repeatedly tap the position of the "try again" button at bottom right corner until manual stop or X hours.
- Auto sell 2* and 3* memmoirs: record the sell loop (auto or choose 20, then sell) and repeat.
- Chapter / event summons: record the summon loop (try replenish, then summon 100x, wait and hit done) and repeat for X times.
Make sure you have "ASTC Texture" support turned on in your emulator, the game loading screen time would be much longer without it.
FWIW, LDPlayer + medium graphics setting gives me the best gameplay smoothness and least crashes (it still happens). You need to adjust the script for longer waiting times if your emulator is too slow.