@set with variables longer than 15 chars crash the client

[Guest]

As the title says, on the previous client (2012-04-09) and packetver, this was not the case. But on 2014-04-16aRagexe and packetver 20140416 I found that using @set with variables longer than 15 chars cause a client crash.

 

Is there any solution to this? And thanks in advance!

Edited May 7, 2020 by Guest
forgot a detail

[4144 364]

what is relation between server variables and client?

Or i not understand what you mean?

 

[Guest]

Sorry, I'm not too sure myself... :< But this is what happened.

 

Doing @ set to check a player variable works fine (The variable in question was 21 characters long). After changing to packetver 20140416, I tried to check the same var and as soon as I use @ set to check it, the client crashes (stops responding then windows error, not a gravity error). I checked other random variables and don't crash if the variable is 14 or 15 characters long, though.

 

Is there a limit somewhere where I can change this? 

Edited May 7, 2020 by Guest
added a bit more details

[4144 364]

strange.

try use packetlogger2 plugin and log packets before and while client crash, and give me to look to them