Compatibility

Compatibility

Applies to all six Info TAB branches.

Loaders

Loader	Supported
NeoForge	Yes
Fabric	No
Quilt	No
Forge	No

Dependencies

None. Info TAB depends only on NeoForge itself. There are no optional integrations and nothing to install alongside it.

Client and server

The client is required, in both directions. Three independent reasons:

1. The mod registers its network channel info_tab:activity_ping as required on both peers, so a client without the mod is refused at connection time with "This channel is missing on the client side, but required on the server!"
2. The [AFK] name tag above a player's head is rendered by client-side code.
3. Input-based activity detection — mouse look, clicks, key presses — only exists on the client. Without it, only movement and clicks on blocks reset the timer.

The mod sets displayTest = IGNORE_SERVER_VERSION, which relaxes the loader's version screen but does not bypass channel negotiation. There is no way to run it server-only or client-only.

Dedicated servers are supported. A crash on player join was fixed in the 0.0.0-beta.3 of the 26.1.2 and 26.2 lines.

Multiplayer

Because the config is a common config, the server's values are authoritative and synced to clients. Change them on the server.

And because every /infotab sub-command is available to any player with no permission nodes, any player can change the shared colours, aliases, format and placement for everyone.

Minecraft version ranges differ by branch

This is the one compatibility difference that can bite you:

Branch	Accepted Minecraft versions
1.21.1	[1.21.1,1.22) — any 1.21.x
26.1.2	[26.1.2] — exactly 26.1.2
26.2 and the three betas	[26.2] — exactly 26.2

The 1.21.1 branch accepts any 1.21.x release. The 26.x branches pin an exact version and will refuse to load on any other.

The six branches compared

Behaviourally there are only three variants, not six. The three beta branches have byte-identical source trees to each other and to the 26.2 branch; they exist purely so you can stay on an older NeoForge build.

Everything below is identical on all six branches: the config schema, defaults and ranges; the whole /infotab tree and its permission behaviour; the four format tokens and the parser; colour resolution and the accepted colour values; AFK detection; the network payload; the absence of keybinds; and the dependency list.

The real differences:

	1.21.1	26.1.2	26.2 and the betas
Java	21	25	25
Accepted Minecraft versions	any 1.21.x	exactly 26.1.2	exactly 26.2
Spanish es_es translation	yes	no	no

The Spanish translation is only on 1.21.1

Of the six branches, only the 1.21.1 one ships an es_es translation — a complete one-to-one Spanish translation of all 21 configuration-screen labels. On 26.1.2 and 26.2 a Spanish client sees the config screen in English.

That is the single most noticeable difference between the branches for a Spanish-speaking player.

Differences that do not change behaviour

The branches also differ in ways that are purely internal, and are listed here only so nobody rediscovers them:

• The 26.1.2 branch parses colours with a different API call than the other five. It accepts exactly the same values and falls back to gold in the same cases.
• API renames between Minecraft versions: the screen accessor, the packet-send helper, the name-tag event split, and the resource-location class all differ per version. Same behaviour.
• pack.mcmeta declares pack format 34 on 1.21.1 and 8 on the 26.x branches. Resource metadata only.
• JAR naming differs, and the 26.2.0.32-beta branch packs without the loader version in the filename. None of this affects the installed mod.

Known limitations

• The client is mandatory (above).
• AFK is not reset by melee attacks on entities — see AFK Detection.
• /infotab reload does not reload the file.
• /infotab refresh ignores the player list you pass it.
• The moddedDimensions config option does nothing.
• Input-based activity detection is disabled while any screen is open.
• The mod adds no gameplay content of any kind.