Sign in to follow this  
Followers 0
NedFox

[SOLVED] GLITCH-CHECK-THREAD-BROKEN, why and what does it mean?

4 posts in this topic

Quote

14:50:26 "<infiSTAR.de>ConnectLog| #0 Connected: xxxxx(yyyyyyyyyyy) ID: 44 SteamName: zzzz   [UpTime: 1h 49min 50s |  - ServerFPS: 47.9042] (v0024A)"
14:50:26 "ExileServer - Playerxxxxx (UID yyyyyyyyyyyyy) connected!"
14:50:26 Error: Object(22 : 2702) not found
14:50:27 Server: Object 2:7275 not found (message Type_91)
14:50:27 Server: Object 2:7274 not found (message Type_91)
14:50:28 Server: Object 2:4363 not found (message Type_119)
14:50:29 Server: Object 2:2913 not found (message Type_119)
14:50:29 "<infiSTAR.de FNC_AH_KICKLOGSPAWN> ["d1drh1n5kj5ff3p",["xxxx","yyyyyyyyyyyyyy","CLIENT_PING","3:5632",[12502,12521,12531,12463]],"3:5632"]"
14:50:29 "<infiSTAR.de FNC_AH_KICKLOGSPAWN> xxxxx(yyyyyyy) Token d1drh1n5kj5ff3p - objByNetID R Alpha 1-2:2 (levy!) REMOTE"
14:50:29 "<infiSTAR.de>ConnectLog| #1 Connected:xxxx(yyyyyy) ID: 44 SteamName: zzzz   [UpTime: 1h 49min 53s |  - ServerFPS: 47.9042] (v0024A)"
14:50:31 "<infiSTAR.de FNC_AH_KICKLOGSPAWN> ["d1drh1n5kj5ff3p",["xxxx","yyyyyy","HLOG_SKICK",[71,76,73,84,67,72,45,67,72,69,67,75,45,84,72,82,69,65,68,45,66,82,79,75,69,78,58,32,108,97,115,116,32,117,112,100,97,116,101,32,54,54,48,49,46,52,53,115,32,97,103,111,46,32,108,97,115,116,32,117,112,100,97,116,101,32,48,46,57,53]],"3:5632"]"
14:50:31 "<infiSTAR.de FNC_AH_KICKLOGSPAWN> xxxx(yyyyyyy) Token d1drh1n5kj5ff3p - objByNetID R Alpha 1-2:2 (xxxxx) REMOTE"
14:50:31 "<infiSTAR.de>HL| 1h 49min 55s |xxxx(yyyyyyy) | GLITCH-CHECK-THREAD-BROKEN: last update 6601.45s ago. last update 0.95 (v0024A)"
 

etc etc

 

Since latest version (last night) some players suffer from this.

Can someone explain what it means and how to sort it?

Share this post


Link to post
Share on other sites

I have same problem but i change to false and no one on my server getting kick disable this till infistar fix this

_wall_look = false;	
_wall_glitch_object = false;
_wall_glitch_vehicle = false;

 

1 person likes this

Share this post


Link to post
Share on other sites
Advertisement

Hey

yes that workaround disabled the check(s) but I've pushed an update/fix for this  online a few hours after your post :)

Share this post


Link to post
Share on other sites
Advertisement
Guest
This topic is now closed to further replies.
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.