Between levels 22 and 43, the Glutin Boxer is one of the most consistent monsters to chain without blowing your kamas on consumables. Its clear Earth weakness makes every fight predictable, and its drops sell reliably on the market.
This guide walks you through exploiting its resistances to the fullest, stringing fights together safely, and β if you want to step away from the keyboard β automating the whole session with MoonBot.
Why Target the Glutin Boxer?
In the mid-game progression window, the Glutin Boxer delivers solid XP without sending you across the continent to find it. Its level range of 22-43 sits in a comfortable bracket to strengthen your build before tackling tougher zones.
Its resistance profile (see the resistance table) shows moderate protection across the board β except for one glaring gap: Earth. That single weakness is your fast lane to short, efficient fights.
Reading the Resistances: Go Full Earth
The Glutin Boxer's resistance table shows 0% Earth resistance, making it the absolute weakest point. Every other element sits in positive territory β Water and Air at 10%, Neutral at 9%, Fire at 5% β all of which slow your kills for no real gain.
In practice: Iop, Sacrier, or Feca players oriented toward Earth are the prime candidates here. A Sadida or Ecaflip with secondary Earth spells can also benefit. Stack Earth damage, keep your spell rotation tight, and most fights will end in just a few turns.
- Earth: 0% resistance β your top pick by far
- Fire: 5% resistance β passable in a pinch
- Neutral: 9% resistance β decent but not optimal
- Water and Air: 10% resistance β avoid to maximize output
Chaining Fights Safely and Efficiently
Consistency is the cornerstone of a profitable session against the Glutin Boxer. At levels 22-25, keep groups to one or two monsters while you calibrate your damage output. By the 35-43 range, three to five at once becomes feasible with the right gear. Watch for buffs or summons mid-fight that could extend the encounter unexpectedly.
Sit down to regenerate HP between fights rather than spending kamas on potions β every potion you skip is pure profit. With a 0% Earth resistance, fights should stay short enough to maintain a high kill-per-hour rate.
Profitability: XP and Drops to Fill Your Bag
The XP yield from the Glutin Boxer across the 22-43 bracket is strong for open-world farming, especially when you chain multiple groups per run. On top of that, its drops find buyers on the HDV β check prices regularly to decide whether to sell immediately or batch for a larger lot.
The real kamas secret here is tempo. The less time you waste between fights, the higher your hourly income climbs. A well-configured script can turn a two-hour session into a hefty haul without any effort on your part.
Automating the Farm with MoonBot
MoonBot runs a Lua script that engages the Glutin Boxer on a loop, automatically applying the Earth strategy. You can leave your account running while you step away: fights chain together, drops land in your inventory, and XP ticks up without any manual input.
The script below is plug-and-play: it locks in the Earth element, targets the weakest enemy first to reduce damage taken, and loops as long as the bot is active. Paste it into MoonBot's Script tab, tweak if needed, and hit start.
Glutin boxeur resistances
Resistance profile from the game data (β = weakness, β = immunity, Γ2 = vulnerable):
| Element | Resistance | Note |
|---|---|---|
| Neutre / Neutral / Neutro | 9 % | β |
| Terre / Earth / Tierra | 0 % | β |
| Feu / Fire / Fuego | 5 % | β |
| Eau / Water / Agua | 10 % | β |
| Air / Air / Aire | 10 % | β |
Ready-to-use Lua script
Paste this script into MoonBot to automate it:
-- Farm Glutin boxeur : element Terre (resistance la plus basse) -- Target monsters: Glutin boxeur 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




