This repository contains two distinct Unity projects: the Unity Playground, an educational framework for teaching 2D physics game development through modular scripts and example scenes (Adventure, Defender, Maze, Lander, etc.), and the com.unity.asset-store-tools, an Editor extension for publishing packages to the Unity Asset Store. The Playground provides atomic movement, condition, action, and attribute components that can be combined visually in the Editor, with custom inspectors to guide beginners. The Asset Store Tools implement a full publishing workflow including package validation (30+ automated tests), preview generation (native and custom), package exporting, and upload with authentication and analytics. Both projects are well-structured with clear separation of concerns, but the Asset Store Tools show signs of version-specific conditional compilation and reliance on internal Unity APIs, indicating medium technical drift. The Playground examples are simple but functional, while the tools demonstrate more advanced patterns like service providers and interface-based validation frameworks.
Blobby Volley 2 is a complete, cross-platform 2D multiplayer volleyball game implemented in C++ with Lua scripting for AI bots and game rules. It features local and networked multiplayer (client-server via a bundled, modified RakNet stack), a dedicated server for online matchmaking, replay recording/playback, and a custom immediate-mode GUI built on SDL2. The architecture uses a state machine pattern (State base class with derived menu, game, and replay states), abstracted rendering backends (OpenGL, SDL, Null), and a custom physics engine with integrated Lua-driven rule logic. The project is built with CMake and targets Windows, Linux, macOS, Android, and Nintendo Switch, with GitHub Actions CI for multiple compilers and platforms. The game's core loop processes player input (keyboard, mouse, joystick, touch, or Lua script) through an InputManager, feeds it into DuelMatch (which combines GameLogic and PhysicWorld for physics and rules), and renders via RenderManager. Network games use RakNet for reliable UDP communication with prioritized packet handling; the dedicated server manages lobbies, matchmaking, and state broadcasting. Replays are recorded as binary state snapshots (using GenericIO serialization) and can be played back in-game. The Lua API provides bot developers with real-time game state queries, physics prediction functions, and callbacks for serve and bounce events, along with older legacy scripts in data/scripts/old. While the codebase demonstrates solid engineering (template-based serialization, abstracted file I/O with PhysFS, cross-platform build systems), it carries technical debt from aging dependencies (RakNet, Lua 5.3, SDL2, TinyXML2) and heavy use of platform-specific ifdefs. Some components, like the custom IMGUI and RakNet integration, are tightly coupled and not easily extractable, but the GenericIO serialization layer and FileSystem wrapper are self-contained and could be reused in other C++ projects needing binary I/O or virtual file system access.