How mogu6321/bedwars_datapack works
Project type and purpose
• Type: A Minecraft “datapack” that re-implements the Hypixel BedWars minigame.
• Purpose: Provide game logic (generator spawns, shops, player tracking, maps) via Minecraft’s datapack system.
File structure
• Top-level:
– pack.mcmeta / readme.md – metadata and docs.
– spyglass.json – optional visual config
– data/ – main namespace directory.
• Under data/: three namespaces:
– minecraft/ – built-in advancement & tag overrides.
– map/ – one Function per arena map for initial setup.
– mogu/ – custom namespace with subfolders:
• dimension / dimension_type – JSON definitions for each arena “world.”
• function/ – grouped by feature: generator, item, player, reset, shop.
• predicate / tags / dialog – auxiliary data for conditions, UI, block categories.
README
• Confirms it’s a BedWars clone datapack, still in development.
Main components & interactions
a. Minecraft Server / Engine (host runtime)
b. Datapack Loader
– Reads pack.mcmeta, loads JSON definitions (dimension, tags, predicates).
– Registers functions under namespaces.
c. Namespaces and Modules
1. – one‐time or on-command map initialization routines (acropolis.mcfunction, etc.)
2. minecraft – advancement and tag “plumbing” at game start
3. mogu namespace:
• dimension & dimension_type – define custom worlds and their properties
• function/generator – logic for diamond, emerald, custom ore generators, timers
• function/shop – UI pages, item purchases, inventory tracking
• function/item – tower building, shop item distributions
• function/player – player stat tracking, item-count checks
• function/reset – game-state resets for generators, items, players
• predicate & tags – conditional checks, categorizations for items/blocks
d. Data/JSON resources
– Define behaviors, spawn rules, UI dialogs (data/mogu/dialog), block tags (data/mogu/tags), and advancement roots.
Architectural patterns & design principles
• Namespaced, modular design – each feature in its own folder under mogu/function
• Data-driven: JSON files drive configuration (dimensions, predicates, tags)
• Event-triggered flows: tick.json in minecraft/tags/function triggers main loops.
• Layering:
– Initialization (map, dimension) → Runtime loops (generator timers, shop UI) → Reset phases