Skip to content

Commit cca2a48

Browse files
authored
Client Brand Changes (#27)
* chore: client brand changes * chore: include a date
1 parent 7d4001a commit cca2a48

File tree

1 file changed

+28
-23
lines changed

1 file changed

+28
-23
lines changed

client-brand.mdx

Lines changed: 28 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,28 @@
1-
import { Callout, Tab, Tabs } from 'nextra-theme-docs';
2-
3-
# Client Brand
4-
5-
Lunar Client can be detected by checking the Minecraft client brand sent to the server. This allows you to detect and track Lunar Client players, if you're unable to use the full
6-
[Apollo](/apollo/introduction) integration.
7-
8-
<Callout type="warning" emoji="⚠️">
9-
This is not a cryptographically secure detection method. Malicious clients can spoof the client brand sent to the server.
10-
</Callout>
11-
12-
## Brand Format
13-
14-
The client brand will always be in the format `lunarclient:<VERSION>`. `<VERSION>` is the Lunar Client build that the user is running. See the next section for info about the
15-
version format.
16-
17-
## Version Format
18-
19-
We do not provide any guarantees about the exact format of the version, and it may change without notice. An unexpected version format does not mean that a user is running an
20-
unofficial build of Lunar Client. The version will be visible on the Minecraft F3 menu, and in the window title, in addition to being present in the client brand.
21-
22-
Most, but not all, users will have a version in the format of `v<MAJOR>.<MINOR>.<PATCH>-<RELEASE YEAR><RELEASE WEEK>`. For example, `v2.12.0-2349` is version `v2.12.0`, which
23-
was built in the 49th week of 2023.
1+
import { Callout, Tab, Tabs } from 'nextra-theme-docs';
2+
3+
# Client Brand
4+
5+
Lunar Client can be detected by checking the Minecraft client brand sent to the server. This allows you to detect and track Lunar Client players, if you're unable to use the full
6+
[Apollo](/apollo/introduction) integration.
7+
8+
<Callout type="warning" emoji="⚠️">
9+
This is not a cryptographically secure detection method. Malicious clients can spoof the client brand sent to the server.
10+
</Callout>
11+
12+
## Brand Format
13+
14+
The client brand is sent as a comma-delimited list of identifiers. For example: `lunarclient:<VERSION>,fabric`
15+
16+
The first identifier is always `lunarclient:<VERSION>`, where `<VERSION>` is the Lunar Client build that the user is running. Additional identifiers may be appended to indicate other mod loaders or relevant context. See the next section for info about the version format.
17+
18+
<Callout type="info" emoji="ℹ️">
19+
**Format Change:** As of 1st December 2025, the client brand was sent as a single string (`lunarclient:<VERSION>`). This change aligns the Lunar Client brand format with other modern mod loaders such as Fabric and Forge, improving compatibility with mods and plugins that rely on client branding to detect mod loaders.
20+
</Callout>
21+
22+
## Version Format
23+
24+
We do not provide any guarantees about the exact format of the version, and it may change without notice. An unexpected version format does not mean that a user is running an
25+
unofficial build of Lunar Client. The version will be visible on the Minecraft F3 menu, and in the window title, in addition to being present in the client brand.
26+
27+
Most, but not all, users will have a version in the format of `v<MAJOR>.<MINOR>.<PATCH>-<RELEASE YEAR><RELEASE WEEK>`. For example, `v2.12.0-2349` is version `v2.12.0`, which
28+
was built in the 49th week of 2023.

0 commit comments

Comments
 (0)