Quick Start Guide
This guide will help you get fCavEX up and running on your Nintendo Wii or PC. Choose your platform below.Prerequisites
Before building fCavEX, you’ll need to download several dependencies manually. These libraries are required for all platforms.
Required Dependencies
Download and place the following libraries in your source directory:Building for Wii
Install devkitPro
Install the devkitPro Wii/Gamecube development environment.
Configure Video Settings (Optional)
Edit
source/graphics/gfx_settings.h to adjust graphics settings for optimal Wii performance:Build the Game
Load the cross-compiler environment and run make:
If you use fish shell instead of bash, you’ll need to source the environment file first.
Prepare SD Card
A
boot.dol file will be created in the root directory. Set up your SD card’s apps/ folder with this structure:Building for PC (GNU/Linux)
The PC version runs on any system with OpenGL 2.0 support and can be played with keyboard and mouse.Configure Video Settings (Optional)
Edit
source/graphics/gfx_settings.h to set your preferred resolution and graphics options:Prepare Assets
Copy the shader files from
resources/ directory next to your assets/ directory.Ensure your game directory has:assets/folder with texture filessaves/folder for world savesconfig.json(useconfig.jsonorconfig_pc.json)- Shader files from
resources/
PC Controls
The default PC keyboard and mouse controls are defined inconfig.json:
Wii Controls
fCavEX supports multiple Wii controller types:Wiimote
D-pad for movement, A/B for actions, +/- for menu navigation, Home button for pause
Nunchuk
Joystick for movement, Z/C buttons for actions and camera control
Classic Controller
Full controller support with dual joysticks and multiple action buttons
Guitar Hero 3
Yes, you can play with a guitar controller! Fret buttons and strum bar supported.
For detailed controller mapping, see the
controls.md file in the source repository.Setting Up World Saves
Create a Beta 1.7.3 World
fCavEX can load world saves created in Minecraft Beta 1.7.3. Use the original game or a world generator to create a world.
Copy World to Saves Folder
Place your world folder in the
saves/ directory. Your world should contain:level.dat- Region files in the
region/folder
Health Adjustment (Optional)
fCavEX uses 160 max health (10 hearts × 16 HP) instead of the original 20 health.
Performance Tips
For Wii Users
To maximize performance on Wii hardware:- Disable clouds: Comment out
#define GFX_CLOUDSingfx_settings.h - Use fast liquids: Comment out
#define GFX_FANCY_LIQUIDS - Keep render distance at 5 chunks (default)
- Use GUI scale 2 for 480p output
For PC Users
If you experience low FPS on PC:- Lower resolution: Reduce
GFX_PC_WINDOW_WIDTHandGFX_PC_WINDOW_HEIGHT - Disable fancy liquids: Comment out
#define GFX_FANCY_LIQUIDS - Adjust GUI scale: Lower values for lower resolutions (320x240 = 1, 640x480 = 2)
- Ensure OpenGL 2.0+ support: Check your graphics drivers
Troubleshooting
Game Won’t Build
- Verify all dependencies are installed in the correct directories
- Check that you’ve sourced the devkitPro environment (Wii builds)
- Ensure you have the required system libraries (PC builds)
Low FPS on Wii
- Disable clouds and fancy liquids in video settings
- Recompile after changing
gfx_settings.h - Ensure you’re using
config_wii.jsonasconfig.json
World Won’t Load
- Verify the world is from Minecraft Beta 1.7.3 or earlier
- Check that
level.datexists in the world folder - Ensure the
saves/path is correctly configured inconfig.json
Chests/Signs from CavEX Not Working
To fix:- Break and replace chests to enable storage
- Break and replace signs to edit their text
- Your items will be lost from CavEX chests; remove valuable items before converting
Next Steps
Video Settings
Learn about all available video settings and how to optimize performance
Gameplay Guide
Discover fCavEX-specific gameplay mechanics and features
Controller Configuration
Customize controls for your preferred input device
Contributing
Help improve fCavEX by contributing to the project
Getting Help
If you encounter issues not covered in this guide:- Check the CHANGES.md for known differences from CavEX
- Visit the CavEX GitHub repository for the original project
- Review build logs for specific error messages