Documentation

Getting Started

This Website showcases the Content from ModMC and Other creator Accounts. Currently it's limited to showcasing projects (which are also accessible through Curseforge and MCPEDL), Documentation to help new players understand Modding and detailed tutorials actually install the mods and addons.

How to use the site

1. Pick an edition: choose Java or Bedrock with the theme switcher.
2. Browse projects: head to Browse, then search, filter by category, and sort.
3. Open a project: read the summary, scan the changelog, and review files before downloading.
4. Stay updated: revisit projects after updates—good notes make upgrades painless.

Choosing an edition (fast)

Edition Guide — Java

Java Edition is where Minecraft modding culture matured: rich APIs, diverse loaders, and a massive ecosystem. The key is choosing the right type of project for what you want to change.

Java project types

1) Mods

A mod changes gameplay by adding code-driven features—new mechanics, items, blocks, UIs, automation, worldgen, and more.

• Best when: you need new behavior, systems, or complex interactions.
• Expectations: version compatibility matters; dependencies should be clear.

Mod loaders Available

Before installing mods, you need to pick a mod loader—the framework that loads and runs mods in your game. The three main options:

Key considerations:

• Mod availability: Check if the mods you want support your chosen loader. Most mods target one loader specifically.
• Version timing: Fabric typically updates faster after new Minecraft releases. Forge/NeoForge may take longer but offer broader mod selection.
• Mixing loaders: You cannot mix Forge and Fabric mods. Pick one and stick with it for your instance.
• Performance: Fabric with Sodium/Lithium often outperforms Forge with OptiFine, but both can run well when configured properly.

2) Plugins

A plugin extends server-side functionality without modifying the client. Players connect with a vanilla (unmodded) client while the server handles custom logic—perfect for multiplayer networks.

• Key difference from mods: Plugins run server-side only. Mods typically require both client and server installation.

Plugin platforms

Common plugin use cases:

• Economy systems, shops, and trading
• Permission management and ranks
• Minigames and custom game modes
• Anti-cheat and moderation tools
• World protection and land claiming

3) Modpacks

A modpack is a curated experience: a set of mods (plus configs) designed to work together. Great packs feel intentional—difficulty, progression, performance, and aesthetics all align.

• Best when: your goal is a complete playstyle, not a single feature.

Modpack launchers

Installing modpacks manually is painful. Launchers handle dependencies, updates, and instance management for you:

Key considerations:

• RAM allocation: Most modpacks need 6–10 GB allocated. Check pack recommendations before launching.
• Version lock: Modpacks often lock to a specific Minecraft version. Don't expect updates to jump major versions.
• Config tweaks: Many packs include custom configs. Replacing mod JARs without updating configs can break progression.
• Server parity: If hosting a server, use the exact server pack version—client and server must match.

4) Resource packs

A resource pack reshapes the game's presentation: textures, models, sounds, fonts, and UI styling. It doesn't change game logic, but it can completely change vibe.

• Best when: you want a visual overhaul without altering mechanics.

Key considerations:

• Resolution performance: Higher resolutions (128x, 256x, 512x) drastically increase VRAM usage. Most players run 32x–64x comfortably.
• Stacking packs: You can layer multiple resource packs—higher packs override lower ones for conflicting assets.
• OptiFine features: Some packs require OptiFine for connected textures, custom skies, or emissive lighting.

5) Shaders

A shader transforms Minecraft's rendering pipeline—adding dynamic lighting, shadows, reflections, volumetric fog, and realistic water. Shaders make the game look cinematic but demand serious GPU power.

• Best when: you want visual immersion beyond what resource packs offer.
• Core requirement: OptiFine or Iris (Fabric) to load shader packs.

Shader loaders

Popular shaders

Key considerations:

• GPU requirements: Realistic shaders can drop FPS by 50–80%. Test before committing to a survival world.
• Shader + pack combos: Pair shaders with PBR resource packs for maximum visual impact.
• Compatibility: Not all shaders work with all mods. Mods adding custom blocks/entities may render incorrectly.

6) Datapacks

A datapack changes gameplay using vanilla systems—functions, loot tables, recipes, advancements, and worldgen rules—without adding new Java code.

• Best when: you want gameplay tweaks without installing mods or running a modded server.

Key considerations:

• World-specific: Datapacks live in your world's datapacks folder. They don't apply globally.
• Vanilla servers: Datapacks work on vanilla servers—no plugins or mods required.
• Reload command: Use /reload to apply datapack changes without restarting.

Edition Guide — Bedrock

Bedrock Edition is built for breadth: phones, consoles, Windows, and cross-platform play. Its creation ecosystem is different—less about Java code, more about packs, behavior, and scripting.

Bedrock project types

1) Add-ons

An add-on is typically a combination of a behavior pack and a resource pack. Together, they let you define gameplay behavior and the assets that represent it.

• Best when: you want to add new mobs, items, blocks, or change existing game mechanics.

Add-on sources

Key considerations:

• Achievements disabled: Add-ons with behavior packs disable achievements. Resource-only packs keep achievements enabled.
• Experimental toggles: Many add-ons require enabling Experimental Features in world settings.
• Stacking add-ons: Multiple add-ons can conflict. Load order matters—packs higher in the list override lower ones.
• Subpacks: Some add-ons include subpack options—check the pack settings gear icon for resolution or feature variants.

2) Resource packs

Bedrock resource packs focus on textures, sounds, UI, particles, models, and presentation.

• Best when: you want to change how the game looks or sounds without affecting gameplay.

What resource packs can change

Key considerations:

• Achievements safe: Resource packs never disable achievements—they only change visuals.
• Global resources: Enable packs in Settings → Global Resources to apply them to all worlds.
• Resolution limits: Bedrock handles high-res textures (256x+) less gracefully than Java—expect performance drops on mobile.
• Subpacks: Many resource packs offer customization options—check the gear icon in pack settings.

3) Behavior packs

A behavior pack defines how entities and systems act—loot, trading, mobs, items, and rule sets.

• Best when: you want to change game logic, mob AI, spawning, or add new entities.

What behavior packs can change

Key considerations:

• Achievements disabled: Any world with a behavior pack applied will have achievements turned off.
• Entity components: Bedrock uses a component system—mix and match behaviors like minecraft:behavior.tempt or minecraft:attack.
• Vanilla overrides: Modifying vanilla entities requires matching their identifier exactly.
• Subpacks: Behavior packs can offer difficulty variants or feature toggles—check the gear icon before applying.

4) Scripts

Scripts let you build dynamic features: custom logic, interactions, UI behaviors, and live systems. Use scripts when you need runtime control that pack definitions alone can't express.

• Best when: JSON components aren't flexible enough for your idea.

Scripting APIs

Key considerations:

• Achievements disabled: Scripts require experimental toggles, which always disable achievements.
• Beta APIs: Most advanced features require "Beta APIs" experimental toggle.
• Performance: Scripts run every tick—optimize loops and avoid heavy operations.
• Debugging: Use console.log() and watch the content log in settings.
• TypeScript recommended: Type definitions make the API much easier to use.

5) Shaders

Shaders enhance Bedrock's visuals with improved lighting, shadows, reflections, and atmospheric effects. Unlike Java Edition's shader ecosystem, Bedrock shaders work through a different pipeline—and now include an official option.

• Best when: you want better visuals without affecting gameplay or achievements.

Vibrant Visuals (Official)

Mojang introduced Vibrant Visuals as Bedrock's official graphics upgrade. It uses deferred rendering and Physically Based Rendering (PBR) to deliver:

• Directional lighting with realistic shadows
• Volumetric fog and atmospheric effects
• Enhanced water reflections
• Improved ambient occlusion

How to enable: Settings → Video → Graphics Mode → select Vibrant Visuals

Device requirements:

• PC: DirectX 12 Feature Level 11 compatible GPU
• Mobile: Adreno 640+ (Snapdragon 855) or Mali (Mediatek Dimensity 1000+)
• Console: Xbox Series X|S, Xbox One, PlayStation 4/5

Third-Party Shaders

The community has created shader packs that work with Bedrock's RenderDragon engine:

Lunac Shaders is one of the most popular RenderDragon-compatible shader packs, delivering natural sunlight, dynamic shadows, animated water surfaces, and ambient sky colors that shift throughout the day—all optimized to run smoothly on mobile, console, and PC.

Key considerations:

• Mobile limitations: High-end shaders drain battery and generate heat. Test before extended sessions.
• No loader required: Unlike Java, Bedrock shaders are applied as resource packs—no separate loader installation.
• Performance varies wildly: The same shader performs very differently across devices. Always test on your specific hardware.

FAQ

Does Minecraft Bedrock REALLY support modding?

Not really—at least not in the way Java Edition does. Bedrock has an add-on system that lets you create resource packs and behavior packs, and there's official JavaScript/TypeScript scripting support. You can add new mobs, items, blocks, and tweak mechanics. But here's the truth: you can't modify the game engine, can't add truly new dimensions with custom physics, can't create the deep system overhauls that Java mods like Create or Twilight Forest achieve. The add-on system is sandboxed by design—great for safety and cross-platform consistency, limiting for ambitious modders. Think of Bedrock add-ons as "officially supported customization" rather than true modding. It's getting better with each update, but if deep modding is your priority, Java Edition remains the platform of choice.

How do I install Forge/Fabric on my Minecraft?

We've got you covered! Head to our Tutorials page where you'll find step-by-step installation guides for both Forge and Fabric. The guides walk you through downloading the installer, running it correctly, and verifying everything works. Whether you're setting up for the first time or switching loaders, the tutorials cover common pitfalls and troubleshooting tips.

Why does my game crash after installing a mod?

Crashes usually stem from a few common causes:

1. Version mismatch — The mod requires a different Minecraft version than you're running. Check the mod's compatibility info.
2. Missing dependencies — Many mods require library mods (like Fabric API, GeckoLib, or Architectury). Read the mod description for required dependencies.
3. Loader conflict — You installed a Forge mod on Fabric (or vice versa). Mods are loader-specific.
4. Mod conflicts — Two mods modify the same game systems incompatibly. Try removing mods one by one to isolate the culprit.
5. Outdated Java — Newer Minecraft versions need Java 17+. Update your Java installation.

How do I allocate more RAM to Minecraft for modded play?

Most launchers have RAM settings in their profile or instance options:

• CurseForge App: Settings → Minecraft → Allocated Memory slider
• Prism Launcher: Edit Instance → Settings → Java → Maximum memory allocation
• Official Launcher: Installations → Edit → More Options → JVM Arguments → change -Xmx2G to -Xmx6G (or your desired amount)

Guidelines:

• Vanilla: 2–4 GB is plenty
• Light modpacks (50–100 mods): 4–6 GB
• Heavy modpacks (200+ mods): 8–12 GB

What is a mod dependency and why do I need it?

A dependency is a mod that another mod requires to function. Think of it like building blocks—instead of every mod recreating common features (like config systems, rendering helpers, or entity frameworks), they share a library mod that handles it.

Common examples:

• Fabric API — Required by almost every Fabric mod
• GeckoLib — Animation library for mods with complex creature animations
• Architectury — Lets mods work on both Forge and Fabric
• Cloth Config — Unified config screen system

When you download a mod, always check its page for "Dependencies" or "Requires." Missing a dependency causes instant crashes—the mod literally can't load without its foundation.

How do I update a modpack without losing my world?

Updating modpacks requires care, but it's usually safe:

1. Back up first — Copy your entire instance folder or use your launcher's backup feature. Non-negotiable.
2. Read the changelog — Pack authors often note breaking changes, removed mods, or world-reset requirements.
3. Update through your launcher — Let CurseForge, Prism, or Modrinth handle the update. Manual file swapping risks config mismatches.
4. Check for removed mods — If a mod was removed that added blocks to your world, those blocks become "missing" and may vanish or cause errors.

Safe update signs: Minor version bumps (1.2.0 → 1.2.1) are usually safe. Major bumps (1.x → 2.0) often require new worlds.

Why is my modded Minecraft laggy?

Performance problems usually trace back to specific causes:

Quick fixes:

• Lower render distance — Modded Minecraft is harder on chunk loading. Try 8–12 instead of 16+.
• Install performance mods — Sodium (Fabric) or Embeddium (Forge) massively improve FPS. Add Lithium for server tick optimization.
• Allocate appropriate RAM — Too little causes stuttering; too much causes garbage collection pauses.
• Disable fancy shader packs — Shaders are beautiful but expensive. Test without them first.

Deeper issues:

• Too many entity mods — Mods adding lots of mobs strain tick rate. Reduce mob spawn rates in configs.
• Worldgen mods — Complex terrain generation slows chunk loading. Pre-generate chunks with a tool like Chunky.
• Mod conflicts — Some mods just don't play nice. Check mod discords for known incompatibilities.

What's the difference between client-side and server-side mods?

This distinction matters for multiplayer:

Client-side mods run only on your game. The server doesn't need them, and they don't affect other players.

• Examples: minimaps (JourneyMap), shaders (Iris), HUD improvements (AppleSkin), performance mods (Sodium)
• You can join vanilla servers with client-side mods installed

Server-side mods run on the server and affect all players. Clients don't need them installed.

• Examples: backup plugins, server utilities, some anti-cheat mods
• Common on plugin-based servers (Paper, Spigot)

Both-side mods require matching installation on client AND server. Most gameplay mods fall here.

• Examples: content mods (new items, blocks, mobs), tech mods, magic mods
• Mismatched versions cause connection failures