How sanciro99/not-cero works
Project Type and Purpose
• This is a libGDX–based, multi-module Java game/application template generated by gdx-liftoff. It uses a “core” module for shared game logic and a “lwjgl3” module as the primary desktop launcher.
High-Level File Structure Analysis
• Root
– build.gradle, settings.gradle, Gradle wrapper files – orchestrate multi-project builds.
– assets/… – all game assets (fonts, atlases, skins) for runtime loading.
• core/
– src/main/java/io/github/Sanciro99/notcero/Main.java – extends ApplicationAdapter with game logic.
• lwjgl3/
– src/main/java/io/github/Sanciro99/notcero/lwjgl3/Lwjgl3Launcher.java – desktop entry point.
– StartupHelper.java – config helper for window, resolution, etc.
– nativeimage.gradle – for GraalVM native image tasks.
Key Insights from README
• “core” holds cross-platform application logic.
• “lwjgl3” is the desktop platform module, builds a runnable JAR or native image.
• Uses Gradle for dependency management, multi-project builds, and platform-specific tasks.
a. Core Module
– Game Loop & Logic (ApplicationAdapter subclass)
– AssetManager usage for fonts/skins/atlases
b. Platform Module (LWJGL3)
– Lwjgl3Launcher → initializes Application Configuration → invokes core.Main
c. External Frameworks & Libraries
– libGDX API (graphics, input, audio subsystems)
– LWJGL3 bindings (OpenGL, windowing, input)
d. Build & Deployment
– Gradle Wrapper & Settings.gradle
– Tasks: core:build, lwjgl3:jar/run, native image
Component Relationships & Data Flow
– Launcher → Core.Main (start game)
– Core.Main → libGDX API calls (render(), update(), input polling)
– libGDX → LWJGL3 native layer → OS/HW
– Core or Launcher → AssetManager loads assets/… → GPU/texture cache
– Developer/CI → Gradle → compiles core + lwjgl3 → jar or native image
Architectural Patterns & Principles
– Module separation: core is platform-agnostic; platform modules provide bootstrap.
– Dependency Inversion: core depends only on libGDX interfaces, not on specific backends.
– Single Responsibility: Launcher config vs. game logic vs. assets.
Technologies & Frameworks to Annotate
– Java 11+ (or configured JDK)
– Gradle (wrapper)
– libGDX (“core” API)
– LWJGL3 backend
– (Optional) GraalVM native image plugin