How's the work going, Toadofsky?
#41 They aren't since I don't know jack about JavaScript:
Uncaught TypeError: Cannot read property 'socketReceive' of undefined
at Object.receive (main.js?v=1536:1053)
at handle (socket.js?v=1536:168)
at WebSocket.ws.onmessage (socket.js?v=1536:63)
Uncaught TypeError: Cannot read property 'socketReceive' of undefined
at Object.receive (main.js?v=1536:1053)
at handle (socket.js?v=1536:168)
at WebSocket.ws.onmessage (socket.js?v=1536:63)
You're giving it up?!
Looks like it.
😱!😭😭😭😭😭😭😭😭😭😭😭😭😭😭😭😭😭😭😭😭😭.
I know, it's sad. Maybe if @Toadofsky tried one more time...
In case anyone has time, making this possible & not buggy requires:
1) Server-side move validation & game end detection
2) Synchronizing client and server displays (server, players, and spectators need to be in sync)
3) Game storage & replay?
4) Non-Stockfish engine analysis?
I can't guarantee Lichess would accept a code submission.
1) Server-side move validation & game end detection
2) Synchronizing client and server displays (server, players, and spectators need to be in sync)
3) Game storage & replay?
4) Non-Stockfish engine analysis?
I can't guarantee Lichess would accept a code submission.
Need Programmers!
Anyone willing to implement this? I'll give you 100 _____!
I could probably add server-side simulation and game storage components to this if I get some free in the near future. Engine analysis for this would be a very interesting project!
This topic has been archived and can no longer be replied to.