Documentation Index
Fetch the complete documentation index at: https://docs.minestorecms.com/llms.txt
Use this file to discover all available pages before exploring further.
Introduction
The Game Type setting controls which avatar service the webstore uses when rendering player heads, bodies and helmets. It is purely visual — package delivery, RCON / plugin commands, and any Minecraft-specific behaviour stay untouched.Set this once during initial setup. The choice is cached for 5 minutes after changes — a fresh switch may take a moment to propagate.
Choosing a Game Type
To configure the game type:Available Options
| Game Type | Avatar Services Used |
|---|---|
| Minecraft | mc-heads.net (head, body) and minotar.net (helm, armor bust). Default for fresh installs. |
| Hytale | hyvatar.io for every avatar kind (head, body, helm, bust, guest placeholder). |
Where the Setting Affects Rendering
The selected service is used everywhere the platform renders a player avatar:- Header / user bar — the user’s head icon in the top-right corner.
- Admin Customers list — head icon next to each customer row.
- Customer detail page — large body render at the top of the profile.
- Statistics dashboards — head icons in top-spender / top-player tables.
- Checkout — recipient avatar when buying a gift.
- Default frontend store pages — wherever a username is shown.
The same setting drives both server-rendered Blade avatars and the frontend’s
<Avatar /> / <ServerAvatar /> components — switching it in one place updates the entire site.For Theme Developers
If you are building a custom theme or template, render avatars using the helper rather than hard-codingmc-heads.net URLs.
Frontend components
The default Next.js frontend exposes two components in@/components/base/avatar/:
<Avatar />— client-side, reads the current game type from the settings store via theuseGameType()hook.<ServerAvatar />— server-rendered, takes the game type as a prop.
buildAvatarUrl() helper in @/lib/avatar.ts, which mirrors the backend AvatarHelper exactly.

