How 4tkbytes/dropbear works
Project type and purpose
• This is a Rust-based game engine workspace (“dropbear”) that consists of three main crates:
• dropbear-engine – the core game engine library
• eucalyptus – a visual editor for authoring games, inspired by Unity/Roblox Studio
• redback-runtime – a lightweight runtime for loading and executing packaged games (.eupak files)
• The overall purpose is to let developers design scenes visually (eucalyptus), write game logic in TypeScript (via Deno), compile and package the game assets and scripts into a bundle, and then deploy/run the game using redback-runtime.
File structure
Top-level
• Cargo.toml – workspace manifest referencing the three crates
• .github/workflows – CI pipelines (build, docs)
• resources/ & scripts/ – shared assets and helper scripts
• ts/ – documentation source for TypeScript API
dropbear-engine/
• src/ – Rust modules for attenuation, camera, rendering (egui), lighting, input, scene graph, etc.
eucalyptus/
• src/main.rs – entry point for the editor application
• src/editor/ – UI components, docks, scene view, input handling
• src/scripting/ – TypeScript integration modules (entity, input, math)
• build.rs / dropbear.ts / template.ts – asset pipeline & packaging scripts
redback-runtime/
• (Likely a binary crate for loading .eupak and invoking dropbear-engine at runtime)
README for additional insights
• dropbear-engine is not yet a standalone framework but is consumed primarily by eucalyptus.
• Eucalyptus uses Deno to run TypeScript scripts to ensure type safety.
• The packaging format is “.eupak” (handled by eucalyptus’s build.rs) and consumed by redback-runtime.