Since 0.3 Headless client keep getting kicked

[R4ziel]

Hey Guys, I hope someone here can help me, as the title suggests in the latest 0.3 update, my headless client keeps getting kicked as soon as it connects to the server.

 

Are there any changes that needs to be made in terms of the headlessclient config or server config?

 

Ive made the same changes that I did when installing the HC as per Horbin's guide. 

 

Ive checked logs and .rpt files and cant really find anything useful there.

 

 

[DirtySanchez]

you might have removed your Headless profile in the mission.sqm with the new updated files........

• *****Silver and Gold Spawn/Gear Select

[R4ziel]

you might have removed your Headless profile in the mission.sqm with the new updated files........

 

I checked my mission SQM and all is still there like it should be, I tested with my 2.5.2 mission.sqm as well and getting the same result. 

[Tango2k13]

Are you using Fums?

 

If yes remove this and it will work again Promise ;)

[SevenVII]

hi,

I got the same problem, as soon as the headless clients connect to the server, it is kicked from it.

It's a infinite loop trying to connect and being kicked. It worked fine in 0.2.5.2 but not with 0.3.

 

@Tango2k13

I have done what you did (I suppose you say to remove Fums.pbo) but it doesn't work.

[stonXer]

which anithack ?

[R4ziel]

I sorted out my problem.

 

I didnt have the Battleyelicense = 1 line in my file, could have been a crappy copy and paste. 

 

Removing FUMS is not an option as that is one of the best mission systems available that I know of, so that is a shitty workaround.

[Metalfoundry]

If you use I***star, I***star is kicking the HC client.

[second_coming]

If you use I***star, I***star is kicking the HC client.

 

I have infiSTAR running with FuMS and have no issues

[Metalfoundry]

hm, what to deactivate here: (perhaps its the same issue like R4ziel). The client is connected until i log in and Infistar is starting..

 

Infistar is kicking my headless client:

23:40:51 "<infiSTAR.de FNC_AH51_KICKLOGSPAWN> ["",["HC_HAL","HC10232","TMPBAN",[80,108,97,121,101,114,32,99,104,97,110,103,101,100,32,83,116,101,97,109,32,65,99,99,111,117,110,116,32,40,104,97,99,107,101,114,63,41,32,45,32,111,108,100,32,85,73,68,115,58,32,91,34,72,67,54,55,55,50,34,44,34,72,67,56,52,55,54,34,44,34,72,67,56,50,56,48,34,44,34,72,67,49,49,52,52,48,34,44,34,72,67,49,49,51,53,54,34,44,34,72,67,49,48,50,51,50,34,93,32,40,84,69,77,80,66,65,78,78,69,68,32,85,78,84,73,76,32,78,69,88,84,32,82,69,83,84,65,82,84,41]]]"
23:40:51 "<infiSTAR.de>SL| 0h 01min | HC_HAL(HC10232) | BadToken () (v0137)"
23:40:51 "<infiSTAR.de> Kicked Player with UID HC10232.. (v0137)"
23:42:10 "<infiSTAR.de> 164.726 - Thread #3: Server #3 waited 120s"
23:42:21 "<infiSTAR.de> ---PlayerDisconnected: headlessclient(HC10232)"

 

[second_coming]

I'm only on v129 of infiSTAR so possibly the new version is causing an issue:

 

You could check the time allowed for clients to connect, that BadToken kick is related to infiSTAR not loading on the client quick enough I think

 

/*  Use Loaded Check(s)  */ _AHL = true; /* true or false */ /* "AH NOT LOADED ON PLAYER" - Recommended strongly to use but might kick gameboy players. */
/*  _timedif for _AHL    */ _TDI =  120; /*   45 - 300   */ /* only used if "_AHL = true;" -> takes longer to detect if the AH is loaded on a player or not. */

[stonXer]

Had the problem with v136 causing the kick, speak to Chris for the updated version.

[Metalfoundry]

ok, i wrote him this morning.. i didnt get the update, some other admins did.. ok, hope for the latest verison-..

[Darth_Rogue]

Don't feel bad. I haven't gotten the update either.

[second_coming]

Me neither

[lowrey]

If you have got the update you have not read the forum correctly!

 

go to "General Help" and it's one of the top ones: HOW TO REQUEST AN UPDATE - DO NOT USE THE FORUM TO REQUEST

 

follow that he says! I had my update quickly!

 

Note .0136/138 breaks headless 100%. I am sticking with 0129 until the next update.

 

Any question on this PM me on the InfiStar forums.

 

Mike

[Darth_Rogue]

I've followed the update procedure every other day for the past week, sending all my email info and even Paypal transaction ID from the original purchase.  Still no response.