I used the pretty-parse thing of chrome to make the code easier readable
Error itself:
Uncaught RangeError: Invalid string length
at _8j2 (MedievalleyTest.js?ver=202012231101:formatted:120585)
at _S52 (MedievalleyTest.js?ver=202012231101:formatted:120281)
at _U91 (MedievalleyTest.js?ver=202012231101:formatted:127302)
at _k5 (MedievalleyTest.js?ver=202012231101:formatted:83942)
at gml_Script_gmcallback_gotPlayerData (MedievalleyTest.js?ver=202012231101:formatted:76959)
at gm_call (?challenge=1:137)
at Socket.<anonymous> (?challenge=1:503)
at Socket.Emitter.emit (socket.io.min.js:formatted:3528)
at Socket.onevent (socket.io.min.js:formatted:3269)
at Socket.onpacket (socket.io.min.js:formatted:3241)
from gml_Script_gmcallback_gotPlayerData, the line defining _Cc1:
https://puu.sh/H2emu/80997b59e8.png
from gml_Script_gmcallback_gotPlayerData, the line calling _k5:
https://puu.sh/H2em7/88b62f7297.png (_mW and _nW are null)
_k5, yellow line in which error gets thrown:
https://puu.sh/H2el4/918f677fc4.png Notice in line 83922 the logga call, which is printing the content of a_userstats to the console, is also the last thing in the console before the freeze and following Uncaught Range error occur (see
http://puu.sh/H2fbS/6838fe4263.png)
_U91, yellow line in which error gets thrown:
https://puu.sh/H2ekR/b4295df964.png
_S52, yellow line in which error gets thrown:
http://puu.sh/H2eqm/e5ae89cefb.png
_8j2, yellow line in which error gets thrown:
https://puu.sh/H2ejX/855907e3c3.png