Rimuru is the headline limited champion tied to the Kurama update and its follow-up Spring event window in Anime Fighting Simulator: Endless. He exists as a roaming world boss with a chance-based champion drop, and his main value is a heavy Chakra training multiplier, which is the slowest stat to grind in the game.
What Rimuru does and why he matters
Rimuru is classified as a limited champion, meaning he only drops while the event window is active. Once the limited period closes, he leaves the pool and may not return for months, if at all.
His core effect is a large Chakra gain boost during training. Chakra is the bottleneck stat for most progression checkpoints, so equipping Rimuru meaningfully shortens the grind to unlock further content, including champions like Ace that require Stat Points across multiple categories.
Rimuru spawn behavior
Rimuru spawns as a world boss at fixed points on the map rather than from a gacha pull. Multiple spawn locations exist, and only one server-instance copy is typically active at a time, so empty servers can still produce a fresh spawn shortly after joining.
Pain spawns share territory with Rimuru. One Pain spawn sits directly behind a Rimuru spawn, and another is near the Wizard Tower, so a Rimuru patrol route doubles as a Pain farming route.
How to qualify for the drop
Step 1: Load into a server and travel to a known Rimuru spawn point. If he is not present or already dead, hop servers rather than waiting in place.
Step 2: Land at least one damaging hit on Rimuru during the fight. A single registered hit is the qualification threshold for the drop roll, so contribution does not have to be high.
Step 3: Stay in the server until the boss dies. Leaving early can void your eligibility for that kill's drop roll.
Step 4: Check your champion inventory after the kill. If Rimuru dropped for you, the champion appears in your collection and can be equipped immediately for the Chakra training bonus.
Server hopping strategy
Server hopping is the single biggest time saver for limited world bosses. Because Rimuru's spawn timer is tied to the individual server, jumping between fresh servers lets you skip cooldown windows that would otherwise force you to wait.
| Action | What it does | When to use it |
|---|---|---|
| Check both spawn zones | Confirms Rimuru is present on the current server | Immediately after joining |
| Server hop | Resets your search across a new instance | When no Rimuru is visible at either spawn |
| Tag the boss | Qualifies you for the drop roll | As soon as you arrive at an active fight |
| Stay until death | Locks in your drop eligibility | Every active engagement |
Common reasons the drop does not trigger
The drop is random per qualifying kill, so dry streaks are normal. That said, a few specific situations remove eligibility entirely.
- You never landed a damaging hit before the boss died.
- You left the server before the kill finished.
- You attacked an enemy that looked similar but was not the Rimuru world boss (Pain spawns nearby and is a separate champion).
Pair Rimuru with Ace for faster progression
Rimuru accelerates Chakra, and the Ace champion questline requires 1 SP in Strength, 1 SP in Durability, and 1 SP in Chakra. Using Rimuru on your active champion slot while grinding the Chakra requirement clears the slowest leg of the Ace unlock, so the two limited champions feed directly into each other.
Pain and Kakashi round out the four limited champions in the same event window. Pain shares Rimuru's spawn area and uses the same one-hit qualification rule, while Kakashi is obtained through event-tab challenges and limited drop sources tied to the Kurama event.
How to confirm Rimuru is yours
After a successful drop, Rimuru shows up in your champion inventory under the limited or event category. Equipping him applies the Chakra training multiplier on your next training session, which is visible as a higher Chakra gain per tick at any training zone.
If he does not appear after a kill you participated in, the roll simply did not hit. Queue up the next spawn and try again before the event window closes.