How yut-nori/yutnori_be works
Project type and purpose
• It is not a full-stack web app or microservices ecosystem, but rather a monolithic game engine/library that could be invoked from a UI layer or CLI.
File structure
• Top-level src/Main.java acts as the application entry point.
• src/controller package contains classes orchestrating game flow (Starter, PlayManager, BoardManager, UnitManager, YutManager, End).
• src/model holds domain entities (Player, Unit) and subpackages:
• src/model/Yut for the dice-like stick toss logic (Yut.java, YutResult.java)
• src/model/board for board representation (Board.java, Position.java)
• No persistence or external service configs, so this is pure in-memory logic.
Key insights from README
• The title “Yutnori_BE” implies only backend logic.
• No additional architecture notes provided, so we infer a simple layered design: entry → controller → domain model.