How possseidon/unbound works
Project type and purpose
• Unbound is a multiplayer, Minecraft-inspired game/engine with smooth (marching-cubes) terrain built atop the Bevy game engine.
• It follows a client–server architecture: a GUI client for players, and a headless dedicated server.
File structure
• Top-level workspace (Cargo.toml) with four Rust crates:
• unbound-client – the Bevy-based game executable (can also host local servers)
• unbound-server – a headless, dedicated-server executable
• unbound-shared – code common to client & server (network protocol, world state, message types)
• unbound-lib – pure-Rust utilities (hexagonal chunking, marching cubes, math, change tracking)
• Standard Rust tooling and CI (GitHub Actions, rustfmt, dependabot) are present.
README for extra insights
• Explicit breakdown of the four crates and their dependencies.
• Emphasis on infinite smooth terrain, marching-cubes mesh generation, and modular crate design.
Essential details
• Crate dependency graph at top level.
• Drill into critical sub-modules in unbound-lib (hex_div, marching_cubes).
• Network boundary between client & server.
• Bevy ECS domain on the client.