The Idemas is a mid-game monster available from level 35, making it a prime target for characters in the thick of their power progression. Its level range (35-47) keeps it relevant for a long stretch without going stale too quickly.
Understanding its resistances lets you optimise every fight and squeeze the most xp and kamas out of each session.
Why target Idemas at this stage of the game
Between level 35 and around fifty, players look for monsters that offer a solid xp-to-fight-duration ratio. The Idemas fits perfectly: tough enough to be worth fighting, soft enough to go down quickly, which means fewer trips back to the fountain.
Its drops regularly supply the mid-range crafting market, making it a consistent kamas source even without specifically hunting rare items.
Reading resistances and picking the right element
The Idemas resistance table (see the resistance table) tells a clear story: Earth, Fire, Water and Air all sit at 30 % resistance, while Neutral weighs in at only 10 %. That 20-point gap is significant enough that ignoring the Neutral weakness is a major strategic mistake.
No immunities or vulnerabilities are present, which means Neutral will always perform well regardless of the fight context. In practice, an Iop swinging a strong hammer in Neutral build, or a Sram in a Neutral configuration, will deal noticeably more damage than an elemental character on this enemy.
If your class has no reliable Neutral damage, any elemental element still works at 30 % — not ideal but far from useless.
- Neutral: 10 % resistance — the element to prioritise above all else
- Earth / Fire / Water / Air: 30 % each — viable but suboptimal
- No immunities: no element to avoid entirely
Chaining fights efficiently
The key to a profitable Idemas session is consistent engagement. Look for dense monster spawns to cut down travel time between fights. The shorter the path between combats, the higher your xp-per-hour climbs.
With level-appropriate gear, each fight should wrap up in two or three turns. If you regularly need five or more turns, it usually means you are not exploiting the Neutral weakness or your character stats are still below the monsters' level range.
Keep a healing item or a teleport scroll handy to avoid time-consuming detours if your character is fragile.
Profitability: xp earned and kamas generated
Idemas delivers solid xp for levels 35-45 without being exceptional beyond that point. The real appeal is consistency: short fights mean a high number of combats per hour, which compensates for a moderate per-fight xp gain.
On the kamas side, Idemas drops include crafting resources whose value shifts with market supply. Without citing exact drop rates, a few hours of farming typically generates enough resources to help fund part of your next gear tier.
Automating the farm with MoonBot
MoonBot lets you script the entire farming cycle in Lua: engaging Idemas groups, handling combat turns with the Neutral element, then re-engaging immediately after each fight ends. The script below illustrates this loop.
The advantage of this automation is maintaining peak engagement even across long sessions where human focus naturally dips. MoonBot also handles clean stops: as soon as isRunning() returns false, the script finishes the current combat and exits gracefully.
Idemas resistances
Resistance profile from the game data (★ = weakness, ∞ = immunity, ×2 = vulnerable):
| Element | Resistance | Note |
|---|---|---|
| Neutre / Neutral / Neutro | 10 % | ★ |
| Terre / Earth / Tierra | 30 % | — |
| Feu / Fire / Fuego | 30 % | — |
| Eau / Water / Agua | 30 % | — |
| Air / Air / Aire | 30 % | — |
Ready-to-use Lua script
Paste this script into MoonBot to automate it:
-- Farm Idemas en boucle (élément Neutre recommandé) -- Target monsters: Idemas function move() config.setBankThreshold(90) -- back to the bank at 90% pods return { { map = "MAP_1", path = "right", fight = true }, { map = "MAP_2", path = "right", fight = true }, { map = "MAP_3", path = "bottom", fight = true }, } end function bank() return { { map = "BANK_MAP", npcBank = true } } end function phoenix() return { { map = "PHOENIX_MAP", phoenix = true } } end -- Replace MAP_1, MAP_2… with the “x,y” coordinates of your maps.
Watch on YouTube




