Peaceful
Towns, communities, shared homes, banks, cosmetics, and protected claims without wars unless explicitly enabled.
Mythical Races Premium System
A premium modular organization layer for Mythical Races servers. Internally the feature is always a Group, while server owners can display it as factions, guilds, clans, towns, kingdoms, orders, or any other community style.
Towns, communities, shared homes, banks, cosmetics, and protected claims without wars unless explicitly enabled.
Progress groups through mob kills, bosses, quests, playtime, dungeons, events, and cooperative rewards.
Enable alliances, rivalries, wars, wagers, leaderboards, scoring, and optional territory conflict.
Combine claims, peaceful opt-outs, PvE progression, diplomacy, and competitive wars in one configurable module.
The first version is planned as a full single-server groups platform. It does not imply proxy-wide network support just because MySQL is available.
Code, storage tables, repositories, services, hooks, and events should use Group terminology. Display names are configurable and can be changed by the server owner.
GroupGroupMemberGroupRoleGroupClaimGroupRelationshipGroupWarGroupWarKillGroupStatsGroupBankTransactionGroupStorageThe premium module should ship a documented groups.yml for configuration only. Live YAML data belongs in groups-data.yml so comments are not destroyed during saves.
# ============================================================
# Groups / Factions / Guilds Configuration
# ============================================================
# This system is internally called "Groups", but you can rename
# the display term to Factions, Guilds, Clans, Towns, Kingdoms,
# Houses, Orders, or anything else.
#
# IMPORTANT:
# MySQL storage does not automatically mean network/proxy
# support. Real network support requires cache synchronization.
# ============================================================
groups:
enabled: true
display:
singular: "Group"
plural: "Groups"
commandAlias: "group"
tagFormat: "[{tag}]"
mode: "HYBRID"
gameplayStyle: "HYBRID"
storage:
type: "YAML"
yaml:
dataFile: "groups-data.yml"
backupBeforeSave: true
autosaveIntervalSeconds: 300
mysql:
host: "localhost"
port: 3306
database: "minecraft"
tablePrefix: "mr_groups_"
network:
enabled: false
mode: "SINGLE_SERVER"
syncProvider: "NONE"Groups should use repository abstractions for YAML and MySQL/MariaDB. MySQL tables need schema migration, transactions for bank and war actions, async-safe writes, and claim caches to avoid database lookups on every block event.
Chunk claims should support safezones, warzones, ghost cleanup, edge-case protection for projectiles, potions, explosions, pistons, hoppers, vehicles, and configurable peaceful, PvE, competitive, or hybrid behavior.
/group create <name>/group invite <player>/group join <group>/group apply <group>/group roles/group dashboard/group claim/group bank history/group war declare <group> [wager]/group top <level|balance|kills|wins|claims|power>/admin group create <name>/admin group setowner <group> <player>/admin group storage migrate yaml mysql/admin group claim safezone/admin group claims purgeexpired/admin group war start <groupA> <groupB>/admin group import preview <plugin>/admin group menuInventory GUI dashboards with chat fallback for Bedrock/Geyser-friendly navigation.
PlaceholderAPI placeholders and internal events for abilities, quests, rewards, economy, and external plugins.
Startup validation that disables only the Groups module when possible and warns about unsupported network settings.