Skip to article
Play free

AneeMate elements: calculate the matchup before attacking

QORPO Studio · 20 October 2026 · 5 min read

The blue aquatic and yellow AneeMate creatures facing each other with water droplets and gentle sparks
Concept illustration created for this article, not a gameplay screenshot.

In AneeMate's element chart, read the attacker's element down the rows and the defender's element across the columns. A weakness gives a damage multiplier of 2 and a resistance gives 0.5. Against a dual-element defender, multiply the two results. Check the current guide rather than importing a chart from another creature game.

A familiar colour can be misleading. You may recognise a water-like creature and instinctively apply a rule from another game. AneeMate has its own matchups, moves and damage systems. The useful habit is to identify the actual attack and defender first, then read the relevant cells.

Open the chart for the build you are learning

The official element section includes a chart and a matchup tool. Use the guide alongside the information shown in the game. A changing Early Access build may not match an old clip or an unofficial picture saved months earlier.

This article explains the calculation, not a complete ranking of creatures. It is based on the public guide checked on 20 October 2026. We are not presenting measured battle simulations, a competitive tier list or a claim that one creature wins every encounter.

Read in the right direction

Begin with the element of the attack you are using. Find its row, then move across to the defending element's column. Reversing the lookup asks a different question. The result of Water attacking Fire does not automatically describe Fire attacking Water.

The guide's Water-versus-Fire example gives a multiplier of 2. That means the matchup contributes a damage advantage for that attack. It does not promise a one-hit victory. Level, the move, the defender's state and other combat rules can still matter.

For your first practice calculation, use one attacker and one defending element. Read the cell before considering a second type or another modifier. There is no need to memorise the whole chart before you understand what one lookup means.

Dual elements multiply the results

For a defender with two elements, look up the same attacking element against each defending element separately. Then multiply. The official guide illustrates Water attacking a Fire-and-Rock defender: the two weaknesses combine, so 2 multiplied by 2 gives 4.

Two resistances produce a different result: 0.5 multiplied by 0.5 gives 0.25. A weakness and a resistance cancel in this calculation because 2 multiplied by 0.5 equals 1. These numbers describe the element multiplier, not the final damage amount displayed in every situation.

Avoid adding the results. Two weaknesses do not make an arithmetic result of 2 plus 2 merely because that happens to reach the same number in that example. Multiplication is important when one or both values are 0.5. It is the rule that makes the resistance examples work.

Original practice example: slow the decision down

This is an invented learning exercise, not a recorded encounter. A player is about to attack a dual-element creature. They identify their move's element, write down the result against the first defending element, then check the second. They calculate the multiplier before choosing whether to continue or switch.

If one lookup gives 2 and the other 0.5, the result is 1. The player has not found a double weakness just because one of the defender's types is vulnerable. They can now compare another available attack using the same method. This exercise does not require buying a pack or changing the game's economy.

The Matebook is useful for checking a creature's elements rather than guessing from its appearance. Start with its actual card. A visually similar creature or a different evolution may not be an interchangeable reference.

Keep element damage separate from other systems

The public guide discusses elemental ammunition separately from the general element chart. It also describes combos, critical hits and reactions. Do not combine every number you see into one formula unless the guide or the current game explicitly explains that combination.

Catching is another distinct question. A damage advantage is not a capture probability. The catching guide explains weakening a target, dazing and selecting a Yipee. If your goal is to catch a creature, winning a damage calculation does not automatically tell you the right final action.

Our catching and transformation article connects those steps to the wider adventure. Use it for the loop; use the element chart for the specific attack lookup. Keeping the two questions separate makes both easier to understand.

What about secondary-only elements?

The guide currently describes Shadow and Sky as secondary elements without attacks of their own yet. That wording matters. Seeing an element as part of a creature's identity does not establish an available attacking move of that element.

Follow the current card and guide when choosing a move. This article does not announce new elemental attacks or a release date for them. If those systems change, the best reference is the updated player documentation rather than an assumption based on the names alone.

Frequently asked questions

Is a multiplier of 4 the final damage? No. It is the element multiplier described by this calculation. Other rules still affect the encounter; this article does not derive a complete damage formula.

Can I use a Pokémon or Palworld type chart? No. Familiar creature-game ideas do not establish AneeMate's specific matchups. Use AneeMate's own chart and creature information.

Does a strong matchup guarantee a catch? No. Catching and damage have separate rules. Read the catching instructions before assuming a damage advantage translates into capture odds.

Try the interactive matchup section, check your party in the Matebook and explore the game through the official Epic Games listing. Concept artwork illustrates the theme and is not a gameplay capture.