Introduction to Journey

Journey is a powerful Minecraft mod designed specifically for Fabric servers running Cobblemon. It transforms your server into an immersive, story-driven experience by adding comprehensive quest systems, spatial zone management, skill progression, and advanced scripting capabilities.

What Makes Journey Special?

Unlike existing quest mods, Journey aims to provide easily malleable systems that can be used for much more than their original intended purpose - this is accomplished via deep Molang integration and expansion.

Core Philosophy

Journey follows these key principles:

Server-Side Control: All configuration is handled server-side, ensuring consistency across all players
Event-Driven Architecture: React to any in-game event with custom logic and responses
Molang Integration: Leverage Cobblemon’s powerful scripting system for complex conditional logic
Modular Design: Each system works independently while integrating seamlessly with others
Performance-First: Designed to handle large servers with minimal performance impact

Key Systems Overview

Task System : Create complex quest chains with branching paths, conditional requirements, and multiple progression types (linear, sequential, randomized)

Zone Management
: Define areas with custom shapes, events, player interactions, and hook into Cobblemon’s base spawning rules to create custom spawn zones for Pokémon.

Levelable Skills : Implement RPG-style progression systems with experience, levels, unlockable content, and custom rewards

Timeline Orchestration : Sequence events and actions over time for cinematic experiences and scheduled content

Event System : Respond to 40+ different game events, from player movement to Pokémon battles

Molang Scripting : Access powerful scripting functions for NPCs, players, items, and complex conditional logic

Server Requirements

Journey requires:

Minecraft: 1.21 or higher
Fabric Loader: Latest version
Cobblemon: Compatible version (see releases)
Java: 21 or higher

Optional Dependencies

For enhanced functionality:

Impactor: Economy integration for currency rewards
Polymer: Enhanced client-side resource pack management

Architecture Overview

Journey uses a modular architecture where each system can operate independently:

Journey Core
├── Event Bus (Central event handling)
├── Configuration Manager (JSON-based configs)
├── Data Management (Player progress & state)
└── Service Registry (System coordination)

Core Systems
├── Task System (Quests & objectives)
├── Zone System (Spatial management)
├── Levelable System (Skill progression)
├── Timeline System (Scripted sequences)
└── Molang Integration (Advanced scripting)

Content Types
├── Tasks (Individual quests)
├── Zones (Defined areas)
├── Levelables (Skills & professions)
├── Timelines (Event sequences)
└── Sources (Task providers)

Configuration Philosophy

Journey uses a configuration-first approach where all content is defined in JSON files rather than requiring code changes. This means:

Hot Reloading: Changes can be applied without server restarts
Version Control: All content can be tracked and managed
Team Collaboration: Multiple people can work on content simultaneously
Extensibility: New content types can be added easily via smart use of Molang and event hooks
User-Friendly: Designed to be approachable for server admins without deep coding knowledge
Backup & Migration: Easy to backup and transfer content between servers

Next Steps

Ready to get started? Continue with:

Installation Guide - Set up Journey on your server
Configuration Overview - Understand the config structure
Your First Task - Create a simple quest

Getting Help

Documentation: Comprehensive guides and references (you’re here!)
Community: Join discussions with other server operators

Journey is designed to grow with your server’s needs, from simple task chains to complex, scripted adventures. Let’s build something amazing!