How corruptedark/open-chaos-chess works
Project type and purpose
• This is a native Android application (“open-chaos-chess”) that delivers a single-player and Bluetooth-based multiplayer variant of Chaos Chess.
File structure
• Top-level modules:
– app/: Android Studio Gradle module with source code, resources, manifest.
– fastlane/: metadata and screenshots for Google Play/F-Droid releases.
– .github/workflows: CI triggers for issue responses.
• In app/src/main/java/dev/corruptedark/openchaoschess:
– UI controllers: Activities (MainActivity, AchievementsActivity, SinglePlayerBoardActivity, MultiPlayerBoardActivity, SettingsActivity, AboutActivity, SecretActivity, StartHostActivity, StartClientActivity), Fragments, Adapters.
– Domain model & game logic: Piece, Square, Mover, MoveThread, SingleGame, MultiGame, ColorManager, GameplaySettingsManager, Achievement, AchievementHandler.
– Communication layer: MultiPlayerService, GameConnectionHandler, StartHostThread, StartClientThread, PairedDeviceAdapter.
• Resources (res/): drawables, layouts, menus, string/locale values, styles, dimensions.
• Build & release: Gradle scripts (build.gradle, settings.gradle), gradlew wrapper, fastlane metadata, publish-release.sh.
README insights
• No server-side component: all data is local.
• Bluetooth API used for multiplayer—ACCESS_FINE_LOCATION permission is a prerequisite.
• Persistence via READ/WRITE_EXTERNAL_STORAGE for import/export and local storage for achievements/settings.
Main components and their interactions
a. UI Layer
– Android Activities & Fragments render the board, menus, dialogs; bind layouts from res/layout.
– Adapters populate RecyclerViews (Achievements, PairedDevices).
b. Domain/Logic Layer
– Game engines (SingleGame, MultiGame) encapsulate rules & random move selection.
– Controllers (Mover, MoveThread) drive piece animations & turn management.
– ColorManager and GameplaySettingsManager handle user preferences.
– AchievementHandler tracks and persists achievement state.
c. Service/Communication Layer
– MultiPlayerService runs in background; GameConnectionHandler + Host/Client threads manage Bluetooth sockets and data streams.
d. Data Layer
– SharedPreferences and File I/O via SettingsManager/AchievementHandler for persisting preferences and achievements.
– Import/Export uses external storage (files).
e. External & OS
– Android BluetoothManager & OS permissions drive peer-to-peer connectivity.
f. CI/CD & Release
– GitHub Actions (issue_response.yml) for automation.
– fastlane pipeline for metadata & screenshot management.
Architectural patterns & principles
• MVC-style separation: Activities/Fragments = Controllers + Views (XML) + Model (game state classes).
• Single Responsibility: each Activity/Service/Thread has a focused role.
• Asynchronous I/O: Threads handle network (Bluetooth) and UI updates via Handlers.
[UI Layer] → [Domain Logic] → [Service & Threads] → [Android OS & Bluetooth API]
Parallel to these, show [Data Layer] interacting with UI & Domain.
– Under UI: MainActivity, SinglePlayerBoardActivity, MultiPlayerBoardActivity, Achievement screens, SettingsActivity.
– Under Logic: SingleGame, MultiGame, MoveThread, Mover, ColorManager, AchievementHandler.
– Under Service: MultiPlayerService, GameConnectionHandler, StartHostThread/StartClientThread.
– Logic in another;
– Services/threads in a third;
– External/OS components as clouds.