Reference · Genre structure
What a battle collection RPG actually is
Strip away the setting and every title in this genre runs the same machine: three loops that feed one another, gated by time rather than by difficulty. Recognising the machine makes the genre far easier to judge, and far easier to stop playing on purpose rather than by accident.
The short version
You collect characters, mostly at random. You spend farmed materials to raise them, which takes far longer than collecting them. You use the raised characters to farm harder content, which drops the materials needed for the next character. Progress is limited by an energy meter that refills on a clock, so the binding constraint is usually elapsed time or money, not ability.
Three loops, one machine
The genre is often described as if collecting were the point. It is not. Collecting is the fastest of the three loops and the cheapest to satisfy; development is where the hours go, and deployment is what makes development feel worthwhile. The table below separates them, because most confusion about the genre comes from treating the three as one activity.
| Loop | What it consumes | What it produces | Where it gates you |
|---|---|---|---|
| Acquisition | Shards, tickets or premium currency | New characters, at random | Rarely. Acquisition is designed to feel generous early. |
| Development | Farmed materials, gear, duplicate characters, and large amounts of elapsed time | A character that can actually be used | Constantly. This is the genre's real cost centre. |
| Deployment | Energy, and a developed roster deep enough to field several teams | The materials that feed development | At each content tier, where a single team is no longer enough. |
The asymmetry between the first two rows explains the experience most new players report: a first week that feels abundant, followed by a second week that feels stuck. Nothing changed in the game's generosity. The account simply moved from the loop the design wants to be frictionless into the loop where the friction lives.
Why roster beats skill
In most competitive games, a better player beats a worse one with equal equipment. That is not how this genre resolves. Combat is turn-based and largely deterministic once the teams are set, so the decisions that matter are made outside the battle — which characters were developed, what gear they carry, and whether the composition covers the roles an encounter demands. Inside the battle there is usually one reasonable line of play, and auto-battle can often find it.
The practical consequence is that a new account cannot compensate for a shallow roster with effort or talent. It can only compensate with time, or with money that converts to time. This is worth understanding before starting, because it sets a realistic expectation of what the first month looks like, and it explains why comparisons between accounts are really comparisons of investment.
Roster breadth matters more than roster height for the same reason. Content that locks entry by faction, or that runs several simultaneous encounters, cannot be cleared by one outstanding character. Six adequate characters usually beat two excellent ones and four empty slots.
Turn order is the real difficulty
The statistic that governs a turn-based encounter is speed, because speed decides who acts and in what sequence. A character applying a control effect one position too late contributes nothing; the same character, with a small speed increase, changes the encounter entirely. This is why experienced players talk about tuning rather than about power, and why a roster that appears strong on paper can fail content that a weaker but better-ordered roster clears.
It also explains the shape of the difficulty curve. Early content forgives any ordering. Mid content requires that control effects land before the enemy acts, which means accuracy has to be high enough to overcome resistance. Late content requires a specific repeating cycle of turns, which is a tuning problem rather than a strength problem. A player who learns to read turn order early will find the middle of the game far less mysterious than one who keeps adding raw power.
The economics of an energy bar
Energy is the mechanism that converts an open-ended game into a scheduled one. A meter holds a fixed number of units, a battle costs several of them, and the meter refills at a set rate in real time. The design intent is not to stop you playing; it is to make the quantity you can play a fixed daily allowance, so that wanting more of it becomes a purchase decision.
Worked example
Take a meter holding 120 units, refilling one unit every six minutes, and a farming stage costing 12 units. A full meter buys ten runs. The meter takes twelve hours to refill from empty, so an account that logs in twice a day captures most of what the clock produces, and an account that logs in once a day loses whatever overflowed while it was full.
Two conclusions follow, and they generalise across titles. First, the efficient pattern is short and frequent rather than long and occasional, which is exactly the habit the design is shaped to produce. Second, the value of an energy refill is not the units it grants but the overflow it prevents, which is why refill offers cluster around the times a meter is likely to be full.
When you convert refills to money, do the sum per run rather than per purchase, and do it in AUD. A refill priced as a small amount of premium currency is easy to buy repeatedly precisely because the individual figure is small; the monthly total is the number that matters. The spending page works through how to convert a currency pack to a real price.
Ceilings, and why accounts stall
Every character has a level cap tied to its current rank, and raising the rank consumes either duplicate characters or dedicated materials, at a cost that grows steeply with each step. A new account typically levels several characters to their first cap quickly, then discovers that the next step costs more than everything spent so far.
That moment is the genre's genuine decision point, and it usually arrives in the second or third week. The options at that point are to narrow focus to fewer characters, to accept a slower pace, or to spend. All three are legitimate; the failure mode is not choosing, and instead spreading resources thinly across a roster where nothing reaches a usable standard.
- Decide which three or four characters you will actually finish, and stop investing in the rest.
- Check what the next rank costs before starting it, not after.
- Treat gear as a separate project with its own farming schedule, because in most titles it contributes as much as rank does.
- Find out whether duplicates help in your title before you discard or sacrifice anything.
What the genre asks of a week
An honest account of the time commitment is rarely given by the games themselves, so here is the general shape. A daily quest list takes a few minutes. Draining an energy meter twice takes longer, and more if content is not clearable on auto-battle. Group content such as a clan boss usually expects a daily contribution at a fixed window. Events add a reward track that assumes regular attendance across its run.
None of those individually is large. Together they form a schedule, and the schedule is the product. A reader deciding whether to start a title is deciding whether to add that schedule to their week, and that is a fairer question than whether the game is good. The evaluation checklist puts it alongside the other questions worth settling first.
What to watch out for
Two patterns deserve attention rather than alarm. The first is a reward track that expires: a pass or an event that converts a missed week into a permanent loss, which makes attendance feel obligatory. The second is a limited-time offer attached to a moment of frustration, such as a summon session that ended badly. Neither is unusual in the genre, and neither is a reason to avoid it; both are easier to handle when you have noticed them in advance and set a monthly figure you are willing to lose.
Common questions
Can a free account reach the late game?
As a general rule the genre is built so that it can, over a longer period, with the difference expressed in months rather than in locked content. How much longer is a per-title question, and the honest way to answer it is to look at that title's own documentation and community rather than to accept a general claim. Where a title does place content permanently behind payment, that is a meaningful fact about it and worth finding before you start.
Why does progress slow down so sharply?
Because the first week is spent in the acquisition loop, which is designed to be frictionless, and the second is spent in the development loop, which is where the material costs sit. The slowdown is structural rather than a sign that you have played badly.
Is auto-battle worth using?
For repeatable farming it is generally the point of the feature, and how much content a title clears reliably on auto is a fair proxy for its real time cost. For tuned encounters such as a clan boss, automatic decision logic often mistimes the skills that matter, so manual play or a carefully arranged team tends to outperform it.
Related reading
The glossary defines every term used above. The randomised rewards page covers the acquisition loop's probability in detail. If you are running a title on a desktop computer, desktop and system basics covers clients, storage and requirements.