Wiki
Identity
This page defines the creative direction for ChonkyCraft.
Status: Planned
This page defines the creative direction for ChonkyCraft.
Project Promise
ChonkyCraft is a mounted co-op adventure overhaul for Minecraft.
It should feel like:
- A world that keeps opening
- A survival sandbox with much denser reasons to travel
- A game where mobility and boss prep are as exciting as raw damage upgrades
- A Minecraft world whose familiar creatures have gone regional, strange, and dangerous
- A world that leaves room for playful creature ideas when they are mechanically worthwhile
It should not feel like:
- Necesse with blocky graphics
- Terraria flattened into Minecraft terrain
- A kitchen-sink modpack where progression is just bigger numbers and more loot tabs
Core Pillars
Mounted Adventure
Mounts are one of the defining pillars of the project.
- Every major progression band should improve your stable
- Mounts should have utility identities
- Mounted exploration should change how you read terrain
- A few mounts can come from funny Minecraft-native side systems, not only boss ladders
- The stable should include a few iconic fantasy rides such as broomsticks, slimes, and dragons when they are properly earned
Vertical Adventure
- Caves should feel inhabited, layered, and worth revisiting
- The sky should become real playable space, not just decoration
- The Nether should be part of the adventure ladder, not an unrelated side errand
- Late progression can open new overworld-like realms, but they must still feel legible and grounded
Frontier Progression
- Every biome should have a reason to visit
- Every milestone should open new routes, materials, or events
- Old spaces should become dangerous again after Worldshift
Readable Challenge
- The game should be challenging because spaces and fights are demanding, not because the player needs a spreadsheet
- New systems should arrive one at a time
- The player should usually know what the next useful goal is
- Rewards should feel obvious and exciting when they land
Controller-First Comfort
- The whole game should be normally playable on a
PS5 DualSense - Menus, maps, and custom systems should support focus-based controller navigation
- Core loops should not require a mouse reach or keyboard detour
- The minimap and waypoint flow should feel practical in active play, not like a desktop-only tool
Familiar but Distorted Minecraft
- Keep Minecraft readable
- Rework existing mobs into biome or event variants
- Add fully new enemies only where the fantasy genuinely needs them
- Let selected friendly vanilla creatures grow into memorable side systems when the result is fun and readable
Relics over Stat Junk
- Equipment should change playstyle
- Utility is as important as DPS
- Build identity comes from combinations, not hard classes
- Gear should grant capabilities like jump, speed, glide, hover, or flight progression when the ladder supports it
Visual and Naming Direction
Preferred style:
- Regional and tactile
- Slightly mythic, never generic fantasy sludge
- Nature, weather, ruin, and frontier language
- Strong silhouettes and readable color families per biome
- Playful when it grows naturally out of Minecraft creatures or habits
- Custom textures that still feel like they belong in vanilla Minecraft
Avoid:
- Direct lifted names from Necesse or Terraria
- Boss names that sound like random AI-generated fantasy nouns
- Weapon names that explain the inspiration too directly
- Purple-everywhere void mush
- Overdesigned progression that feels like homework
- HD, painterly, or over-rendered textures that break vanilla texture-pack style
Translation Rules
When translating source inspiration into the project:
- Preserve the gameplay role
- Change the fantasy skin
- Route it through Minecraft ecology
- Tie it to local materials, mobs, and terrain
Example:
- Do not copy a desert predator boss because a source game has one
- Keep the gameplay role of a mobile desert hunt
- Translate it into a new boss with its own name, visuals, attacks, and ecology fit
Mount Priority Rule
If a design decision weakens the mount ladder, it is usually the wrong decision.
Mounts are not a bonus feature. They are one of the reasons this project should exist.