| layout | default |
|---|---|
| title | Welcome |
| nav_order | 1 |
ClientCore is a Paper/Folia plugin for player-specific client-side gameplay: fake blocks, PacketEvents-backed vanilla block mining, personal loot chests, personal ground drops, client-owned mobs, and client-only NPCs.
The important idea is that most features are real server logic with client-specific visibility. For example, a block regen node is sent as a fake block packet to one player, while another player may see normal world terrain. Vanilla mining rules keep the server authoritative by replacing the normal break flow with a timed server-side break. Client mobs are still server entities, but ClientCore hides and protects them so only their owner can see and interact with them.
- Paper/Folia matching the plugin build target.
- PacketEvents bundled in the shaded ClientCore jar. A compatible external PacketEvents plugin may also be used.
- Java version supported by your server build.
- SQLite or MySQL JDBC driver available on the server classpath if your selected database needs it.
Optional integrations:
- PlaceholderAPI for conditions.
- WorldGuard for block regen region flags.
- MMOItems for configured item rewards.
- MythicMobs for client-owned mobs and MythicMob NPCs.
- ModelEngine for MythicMobs models.
- Citizens or FancyNpcs for NPC providers.
- Put
ClientCore-1.0-all.jarinplugins/. - Add any optional hook plugins you use.
- Start the server once.
- Edit files under
plugins/ClientCore/. - Run
/clientcore reload. - Use
/clientcore statusto confirm loaded block regen, vanilla mining, farming, mob rule counts, and hook status.
- Configuration Layout
- Main Configuration
- Conditions
- Commands
- Client Builds
- Folia Compatibility
- Changelog
- Blocks Regeneration
- Loot Chests
- Ground Drops
- Mobs
- NPCs
- Messages
- Troubleshooting
All feature folders support multiple YAML files. This is valid:
plugins/ClientCore/
config.yml
messages.yml
blocks/
coal.yml
ores/deepslate.yml
mobs/
tutorial.yml
bosses/wither.yml
drops/
tutorial.yml
Inside each feature file you can use either the full root, a rules: root, or direct rule IDs. See
Configuration Layout for the exact rules.