Roco Kingdom Jiny Classes Explained: An 18-Class Planning Framework

Roco Kingdom confirms 18 elemental classes for its creatures, called Jinies. That number is useful, but it is not a ready-made combat manual. Class names, interactions, selection limits, and detailed battle rules are to be discovered in the Quack Quack Test. Last verified: 2026-10-22.

This article provides a planning framework rather than a matchup chart. Every recommendation about comparing options is explicitly analysis or general genre advice, not a confirmed Roco Kingdom rule. For the creature terminology and broader setting, start with the Jinies guide. Keeping that foundation separate from speculation makes later findings easier to evaluate.

What the Number 18 Establishes

Eighteen elemental classes establish that the game has a defined classification framework. They do not establish that all classes are available immediately, that every creature belongs to exactly one, or that each class follows a familiar set of advantages. Those questions are to be discovered in the Quack Quack Test.

It is tempting to fill gaps using knowledge from another creature game. Resist that shortcut. Even when two games use similar language, their rules may differ in consequential ways. A remembered chart is an outside reference, not evidence about Roco Kingdom. Write down what the test explains before trying to optimize around it.

A careful class reference should eventually contain the label, the source of its definition, and the effect that definition actually supports. Until those details are available, a blank field is more accurate than an attractive but unsupported chart. That is why this snapshot includes no class-name list.

Analysis: Define the Decision Before Comparing Creatures

A useful team-building question begins with a specific decision. “Which option helps with the situation I am facing?” is more practical than “Which class is strongest?” This is analytical advice about learning games; it does not confirm how Roco lets players assemble or deploy Jinies.

Start by identifying what the game explicitly asks of you. Then separate what you know from what you assume. If an explanation names a relevant attribute, record that wording. If you only suspect a connection, label it as a hypothesis. This prevents your personal planning notes from turning into accidental misinformation.

The permitted number of active Jinies and any team composition restrictions are to be discovered in the Quack Quack Test. Therefore, this framework deliberately works without a fixed team size. You can apply it to whatever choices the game actually presents, from a single selection to a broader collection decision.

Analysis: Compare Function Before Labels

A label is a starting point for asking questions, not a complete account of a creature's function. As analysis, compare the information the game provides about two candidates and ask which differences are relevant to your immediate goal. Do not assign an invented role simply because a design looks fast, sturdy, or powerful.

You may find it helpful to keep a small comparison note with three headings: displayed information, observed behavior, and unresolved questions. The headings are your note-taking structure, not Roco interface elements. They force you to distinguish a description from a result and leave space for later corrections.

Avoid numerical rankings before you understand the conditions behind them. A number without context can imply precision that the evidence does not support. If a test observation seems meaningful, preserve the circumstances and the explanation you were following. Other players can then judge whether it applies to their situation.

Analysis: Variety Is a Question to Investigate

In creature-collecting games generally, players often investigate whether varied options help them respond to different challenges. Here that is a genre-inspired question, not a confirmed benefit of mixing Roco classes. Whether variety provides specific advantages is to be discovered in the Quack Quack Test.

The practical research question is simple: what difference does the game actually demonstrate? If an official explanation or a repeatable observation connects a class to an outcome, record that connection narrowly. Do not extend it automatically to every encounter or every Jiny bearing a similar label.

Personal preference also belongs in the decision. Enjoying a creature's design or wanting to learn more about it is a valid exploration goal. That does not make it mechanically optimal, but optimization is not the only reason to play a test. State your goal so readers understand your recommendation's purpose.

Building a Reliable Class Notebook

Keep the date and context beside each finding. Test information is especially easy to detach from its original conditions when screenshots circulate. A note saying when you observed something helps distinguish a current test finding from a memory of another version or an interpretation of promotional material.

Use plain confidence labels such as “official explanation,” “observed once,” and “still unclear.” These are editorial labels for your notebook. A single observation may be useful, but it does not establish a universal rule. Revisit uncertain notes when the game provides better explanations or a clearer opportunity to compare outcomes.

For a workable first session, choose one class-related question and investigate it carefully. Trying to produce an entire competitive guide immediately encourages guessing. The general tips guide explains how to turn focused observations into useful learning habits without presenting them as confirmed mechanics.

Where the Test Fits

Roco Kingdom is a free-to-play open-world creature-collecting RPG developed by Morefun Studios, part of Tencent. Its global Quack Quack Test begins October 27, 2026, at 04:30 UTC on PC through Steam, iOS, and Android. That is a test milestone, not the announcement of a global release date.

Check the official website for pre-download and participation instructions, and use the correct Steam listing, app 4821880. An Epic Games Store listing does not confirm Epic access to this test. Follow the instructions applicable to your account; an installed client is not a guarantee of admission.

FAQ

Are there really 18 classes?

Yes. Eighteen elemental classes are part of the confirmed framework in this October 22 snapshot.

Where is the complete matchup chart?

This page does not invent one. The class names and detailed interactions are to be discovered in the Quack Quack Test.

How many Jinies should a team contain?

Team size and composition rules are to be discovered in the Quack Quack Test. This analysis does not assume a number.

Is a mixed-class collection always better?

That is not established. Variety is a useful question to investigate, while any actual mechanical benefit is to be discovered in the Quack Quack Test.