After the holiday break, I'm back at it. Although I've already confirmed it works via CLI, the visual layer is still missing, and GPT and I are stuck in a bottleneck. The order used by WinBoard or XBoard (if on Linux) is: 1. TLCS (server.ini configured with the correct paths, we'll dive into this later) 2. WireGuard configured correctly 3. Run TLCS. 4. Launch the tournament from the framework (the TLCS console receives the tournament data; in the case of WinBoard, it's a debug file that feeds the data) 5. From the VPS, launch node-tlcv, and then we have TLCS and Node connected. After that, the web viewer broadcasts the tournament in real time. In our framework, we've taken this idea, but we created the app using the ChessGUI framework (ccrl.live broadcasts using this framework and the same system), and it's not a .debug file but a .txt file. The issue is that the tournaments do work, but we can't get the TLCS client to update the board, even though the .txt file does capture the moves and node-tlcv from the VPS connects to TLCS just like it does with WinBoard. Since, even though it's the Plus version, it's still GPT—the greatest plagiarism ever created in history—it makes mistakes and can leave a space, add a wrong character in the code, and we have to keep debugging and debugging, but without managing to broadcast like we did with WinBoard. Why didn't I use WinBoard? Because it only allows launching a single game between two chess engines, not a tournament. In any case, I take this opportunity to wish everyone a Happy New Year again, and we'll get back to programming matters once the holidays are over. Warm regards, everyone.