How lang010/cloudict works
Cloudict is a Connect6 engine with a command-driven play loop. A user sends board updates or requests a move; the engine updates game state, tries VCF tactical search when enabled, then falls back to alpha-beta search and returns a move. The search uses generated candidate moves and board evaluation; VCF uses pattern matching initialized from the documented patterns.in file. The excerpts show these main calls, but not the implementation details of situation.cc or vcf_search.cc, so those internals are represented conservatively.
Main entry points: game_engine.cc Game Engine · vcf_search.cc VCF Search · search_engine.cc Alpha-Beta Search · main.cc Program Entry
Components 12
Command Interface
- Program Entry
src/main.cc - Game Engine
src/game_engine.cc
Game State
- Board and I/O Utilities
src/tools.cc - Situation Logic
src/situation.cc - Game Types and Constants
src/defines.h
Move Search
- VCF Search
src/vcf_search.cc - Alpha-Beta Search
src/search_engine.cc
Board Analysis
- Move Generator
src/move_generator.cc - Board Evaluation
src/evaluation.cc - Pattern DFA
src/pattern.cc
Other components
- Game Client
- VCF Patterns
patterns.in
Connections 11
- Game Client → Program Entry: starts engine
README.txt - Program Entry → Game Engine: initializes and runs
src/main.cc - Game Client → Game Engine: sends commands
README.txt - Game Engine → Board and I/O Utilities: reads and updates board
src/game_engine.cc - Game Engine → VCF Search: tries tactical search
src/game_engine.cc - Game Engine → Alpha-Beta Search: runs fallback search
src/game_engine.cc - Alpha-Beta Search → Move Generator: requests moves
src/search_engine.cc - Alpha-Beta Search → Board Evaluation: evaluates leaves
src/search_engine.cc - VCF Search → Pattern DFA: uses DFA
- VCF Search → VCF Patterns: loads patterns
README.txt - Game Engine → Game Client: returns move
src/game_engine.cc