How llr104/slgclient works
This is a Cocos Creator 3.4 strategy-game client demo. Its main player-facing loop is logging in, managing a city and generals, then using the world map to move armies and contest territory; other documented features include draws, skills, battle reports, alliances, and chat. The tree exposes scenes, prefabs, and game data, but no client scripts. Accordingly, the graph maps documented capabilities to those assets and avoids asserting unverified screen wiring or runtime call sequences.
Main entry points: basic.json Game configuration · login.prefab Login · MainScene.scene Main scene · MapToolScene.scene Map scene
Components 18
Client entry
- Login
assets/prefab/login.prefab - Main scene
assets/MainScene.scene
World strategy
- Map scene
assets/MapToolScene.scene - Map interactions
assets/prefab/map/MapClickUI.prefab - Army movement
assets/prefab/map/ArmyArrow.prefab
City and generals
- City facilities
assets/prefab/CityFacilityItem.prefab - Army recruitment
assets/prefab/CityArmySetting.prefab - General roster
assets/prefab/GeneralRoster.prefab - Skills
assets/prefab/Skill.prefab - General draw
assets/prefab/Draw.prefab
Social and reports
- Battle reports
assets/prefab/WarReport.prefab - Alliance
assets/prefab/Union.prefab - Chat
assets/prefab/Chat.prefab
Game data
- Game configuration
assets/resources/config/basic.json - Game data
assets/resources/config/json
Other components
- Player
- Game server
- Gate server
Connections 15
- Player → Login: uses
- Player → Main scene: plays
- Player → Map scene: plays
- Player → City facilities: manages
- Player → Army recruitment: recruits
- Player → General roster: manages
- Player → Skills: views
- Player → General draw: draws
- Player → Map interactions: interacts
- Player → Army movement: commands
- Player → Battle reports: reviews
- Player → Alliance: joins
- Player → Chat: chats
- Game configuration → Game server: configures endpoint
- Game configuration → Gate server: configures endpoint