btw, any developers who would like to contribute, send me a PM and I will explain the situation.
Client side not recognizing a move, then player getting timed out as a result -- happens a lot in th
Sort:
@_-__-__-___-,
The reason I suspected a client side code issue is that I never experienced this bug prior to about 7 days ago (whenever it was that you guys had us agree to the new TOS and not teaming). Prior to that, I think people still had connection issues, but not this bug I described.
As to checking the console for errors, as you suggest... where exactly do we check?
@_-__-__-___-,
I'd be curious if you (or other devs) changed any of the client side JS code as part of that update, because I saw this bug immediately after that update -- but never before.
Appreciate all the work from the developers.
Unfortunately we are now in a position where many regular players like me have stopped playing out of frustration. The momentum gained the past year to get enough regular players is now at risk. Numbers will quickly fall off until resolved, and then may not recover easily.
My suggestion is to go back to the last known stable version and test the unstable version on the test server until resolved. Stability is always the number 1 issue for any development. Added features are a nice to have, but not a reason for players to stop playing like stability issues are.
Dec 30, 2018
0
#46
@mattedmonds, you didn't play after 27th of December. It is better now.
Also on our test server this version works fine. To test it properly under high load we need to have 100-200 players online on the test server. But we used 20-30 maximum. (And we were really happy to see so many players helping us test 4PC!) Do you know a way to attract more players to the test server?
riv3r wrote:
As to checking the console for errors, as you suggest... where exactly do we check?
I'm going to assume he means the JS console. To get it (in chrome) right click the page and select "Inspect" This will bring up a sidebar on the right. Click "Console" and see what is says.
@_-__-__-___-
Have you considered using JQuery's AJAX function, or does the server not use PHP?
@BabYagun I tried the test server one time. It said it wasn't working. Did I just do something wrong?
Dec 30, 2018
0
#48
Console: Ctrl (or Command)+Shift+J
> It said it wasn't working.
Maybe it was updated at that moment. We can update it several times a day.
Dec 30, 2018
0
#49
riv3r wrote:
@_-__-__-___-,
The reason I suspected a client side code issue is that I never experienced this bug prior to about 7 days ago (whenever it was that you guys had us agree to the new TOS and not teaming). Prior to that, I think people still had connection issues, but not this bug I described.
As to checking the console for errors, as you suggest... where exactly do we check?
As you wrote you've been developing for 25 years, I assumed you are familiar with the console that comes with every browser - where javascript errors are shown. rightclick->inspect->console.
as mentioned, over the xmas days there was a serious problem - constant disconnections.
fwiw i played many games yesterday and today, and did not expierence a single problem.
Dec 30, 2018
0
#50
riv3r wrote:
@_-__-__-___-,
I'd be curious if you (or other devs) changed any of the client side JS code as part of that update, because I saw this bug immediately after that update -- but never before.
with the huge amount of new features (variants, custom games and whatnot), of course the JS code was updated. it's updated every time we release, as you might expect.
That said, I haven't changed anything about how moves are sent, or received.
As i wrote in #43, when I experienced the problem you describe, the move had been played, I just didnt get any feedback (until i reloaded the window). And that means the client sent the move.
Dec 30, 2018
0
#51
@mattedmonds, as mentioned, from roughly dec 23-27 there was a serious problem - and naturally we got swamped with complaints.
Since the fix on the 27th it has gone back to normal, the occaisional disconnect (reloading the window has fixed it for me every time). Also no more complaints, so it can't be that bad.
I played many games yesterday and today, and did not expierence a single disconnect or non-registered move.
Dec 30, 2018
0
#52
@Chipster2015 4pc is built with node and vue. No php. We do use Jquery, but no ajax. It uses socket.io, which I think is the achilles' heel of 4pc, and I'm looking to replace it. It's pretty much the only thing I haven't rewritten from scratch (compared to the old, pre Aug-7th, 4pc app).
_-__-__-___- wrote:
riv3r wrote:
@_-__-__-___-,
The reason I suspected a client side code issue is that I never experienced this bug prior to about 7 days ago (whenever it was that you guys had us agree to the new TOS and not teaming). Prior to that, I think people still had connection issues, but not this bug I described.
As to checking the console for errors, as you suggest... where exactly do we check?
As you wrote you've been developing for 25 years, I assumed you are familiar with the console that comes with every browser - where javascript errors are shown. rightclick->inspect->console.
Ah, didn't realize you meant the JS console. Thought you meant some chess.com console.
To be clear, I doubt it is a JS syntax error that will register as an error in the console. Rather, my suspicion is that it is a comprehensive logic issue with how the client manages game and move state, and how that game/move state are managed between all 4 players and the server. Just a hunch.
But if it happens again, I'll tab over to the JS console.
I haven't have the bug happen in 24 hours.
Thanks, I will test it again
Its better but still having this issue. Just made my move with 8 secs left and clock just kept running 
Just refresh the page. It happens to me also.
Doesnt refresh fast enough, lose about 20+ seconds each time
Dec 31, 2018
0
#58
@mattedmonds, Do you use Wi-Fi or cable? Maybe VPN, proxy or some other similar browser (or OS) app/add-on (anonymizer maybe)? Same issue in 2 different browsers?
During 3 days I have issues with my ISP, both cable and WiFi speeds are at 7% to 10% of what they should be, and I need to restart the hub a few times a day when it just stops working. WiFi speed fluctuates noticeably every time I run speedtest.net test. So, it is a bad time to play 4PC from my computers. But I played 8 games yesterday (7 Teams, 1 AntiChess) and was not disconnected. There was 1 aborted game, however, where all 4 players including me were disconnected on the 1st move. So, there is definitely some server side glitch (otherwise why all 4 players were disconnected?).
But some players are affected more than others and this should be some client side issue. Why did I play 8 games without disconnects (even with ISP problems mentioned above), but some other players are disconnected often?
I suspect browser add-on's, VPN's and similar stuff.
Had it happen to me again. Got a clip of the JS console.
You will notice that I have moved the queen to j11 putting green in check, but the client has not responded and realized that green is in check yet. It just sits there clicking down time.
I should mention that soon after I got the shot, it came back on its own. I used to have to refresh the page to get it to come back. So, it's much better now, in my opinion anyway, but still slightly annoying. 
@riv3r "To me, it feels more like a client side code defect"
As explained above, I doubt it, but it's not impossible. When you think something has gone wrong, please check the console for errors (if you have time, before reloading the window) and post them here on in the bug thread.