Playing Oxyotl in Total War: Warhammer 3
Oxyotl is a Legendary Lord for the Skaven (Disciples of Hashut) faction, and by extension the Chameleon Skaven campaign path. He is not a frontline brawler. He is a stealth/infiltration lord whose whole design revolves around disappearing from the battlefield, repositioning, and picking apart enemy armies from ranges that should be safe. If you try to use him like a standard Skaven raid lord, you will waste your turns. The core loop is simple: cloak, advance, harass, retreat. His passive Cloak of Deception makes him invisible to enemies unless they have detection or are in melee range with him. That means you can walk his unit stack directly onto an enemy army's flank or rear without triggering a battle. You then unload spells and wait for them to realize something is wrong. By the time they do, you are already fading back into the woods. His weapon is a magical staff that deals poison damage. The damage number itself is not high, but the poison tick compounds nicely against high-willing models like chariots and monstrous infantry. Your real value is in the spell list he has access to, which skews heavily toward concealment and debuff rather than outright nuking.
My unit composition around him usually runs one Oxyotl lord, one Warlock Engineer battery for supporting fire, and a mix of Rat Ogre bodies to absorb hits. You need bodies because when your stealth gets spotted, you do not want to be standing alone in the open. A couple of Skirmisher squads fill the recon role and clean up low armor targets while Oxyotl stays back casting. Here is a practical issue I ran into on my first dozen campaigns with him. The invisibility has a cooldown on re-cloaking after you become visible, and on higher difficulties the AI learns to patrol its army perimeter more aggressively. I kept losing Oxyotl to a single Stalker unit that happened to be camping on a forest ridge above my position. The detection from that Stalker broke my cloak every time I tried to phase through that chokepoint. The workaround was trivial but not obvious: I stopped trying to cross that ridge entirely and instead used a different route through the map, letting my Skirmishers draw the Stalker away first. Oxyotl moved in empty. It cost me two extra turns of movement, but it saved the lord repeatedly. Talent choices matter more than most players give them credit for. The early game tree branches toward either survivability or spell potency. I pick the path that increases his magic resistance and reduces cooldown times on his cloaking ability. Magic resistance is not flashy, but Oxyotl dies in one shot from a single enemy spell if you stack him poorly. A level 5 Fireball or Storm Globe removal will delete him before he casts a single spell of his own. Cooldown reduction is the better long-term investment. Every time his cloak resets faster, you get another window to reposition safely. That extra window compounds across a full campaign.
On the campaign map, Oxyotl excels at hit-and-run raids rather than siege. His movement is average, so chasing down armies is slow, but his ability to bypass forward scouting lines means you can appear behind enemy lines and torch a settlement before the AI even registers the threat. Pair him with a fast character like a Deathmaster or a Warlock Enginseer for maximum map pressure. The Deathmaster pulls enemies out of position; Oxyotl punishes the resulting chaos. The biggest weakness of this lord is his fragility once detected. He has low health pool and no armor save that matters at higher levels. A single well-placed arrow volley from a Crossfire Cadre or a charged charge from a Chaos Warrior block will end him in seconds. Do not keep him in melee past one turn. If a fight drags on that long, you have already lost the advantage of surprise. Re-cloak and disengage. There is no shame in it, and the lord will survive to do it again next turn. For spells, prioritize any ability that extends his cloak duration or adds a bonus to his first strike. The standard damage-dealing spells like Warpstone Bolt are fine for finishing wounded units, but they are secondary. Your main job is to stay invisible as long as possible, wear down the enemy, and disappear before they can react. The damage numbers you deal while cloaked are mostly incidental.
Get the Full Details
If you are playing on Very Hard difficulty or above, the AI will place more detection units on the map and their stacking will make Oxyotl harder to use as a pure infiltration tool. In those cases, shift your playstyle slightly toward a support role. Use Oxyotl to break enemy morale with early spell bursts, then pull him back behind your front line to apply debuffs from safety. He still contributes meaningfully; you just stop pretending you can walk him right onto the enemy general's head without consequence. Build order summary for a typical opening turn stack: Oxyotl as your primary lord, a Warlock Engineer battery as secondary, two Skirmisher squads, and a small Rat Ogre body unit for screening. Fill the rest of your army with fast movers and ranged support. Keep Oxyotl out of the first three battles if possible, letting your bodies absorb the initial damage while he softens targets from range. After that, he becomes the central piece of your offensive rhythm. One more thing that catches people off guard: Oxyotl's cloak does not prevent him from being targeted by area-of-effect spells from distance. An enemy casting a spell that covers a large zone can hit him even while he is invisible, especially if the spell originates from a unit that already has line of sight. I learned this the hard way when a Cursed Land warlock dropped a poison cloud directly on my positioned Oxyotl and he took enough damage to force an emergency retreat. Always check for enemy spellcasters with AoE options before committing to a cloaked approach. It costs nothing to look and saves a lot of lords.