Unsure if this is even a bug as my initial assumption was that this could be a function of MP eater + time. A couple nights ago I attempted a Zakum solo between my three characters (Night Lord, Bishop, and Bowmaster). While it took maybe 40 minutes to start damaging the 3rd body, I spent about 45 more minutes on the 3rd body before I encountered this bug. To explain why MP Eater is related, it's important to know that the sheer volume of summons appearing was overwhelming. In fact, there were so many that I needed to spam Genesis on my bishop for a couple minutes to even allow my Night Lord to attack. Anyways, by the time roughly 45 minutes or so had passed, the 3rd body was at roughly 47% HP and I noticed it had... completely stopped attacking. No summoning, no 1/1s, no Seal skills. It sat, continuing the idle animation Zakum does, but nothing else. I tried clearing the remaining summons on my Night Lord to see what happened. Nothing changed. My assumption was that after using Genesis so many times, Zakum simply ran out of MP. However, just in case of a misunderstanding it was suggested to me that I report this as a potential bug. I've personally been on many Zakum runs that took over 1 hour, especially back in the 2000s before 4th job was released, and yet I have never seen this behavior before. Mages were a rarity on Zakum runs even then, so MP Eater's effects over a long time seem to be the only missing factor, unless this is a genuine bug with the Royals client.
I always thought this was normal behavior when zakum simply runs out of mana. This happens even without a mage with MP eater. Happened in my ironman solo zak, at the end of the third body zak stopped using skills and summoning monsters: https://royals.ms/forum/threads/gam...olo-diy-no-trading.42779/page-79#post-1441174 https://royals.ms/forum/attachments/zak6-png.190932/
