I put waittillframeends is not a long time, so it was up to waittillframeends
I put waittillframeends is not a long time, so it was up to waittillframeends
The waittillframeend is actually needed if you respawn a client with this method (or wait 0.05 or any wait at all), but you should NEVER call the playercommand() function after a wait for the buffer in it will have been altered, resulting in undefined behaviour
As the waittillframeend is properly return;-d, i dont see much issues with it. However, as there is obviously an issue with the code (see OP), i'd advise to remove all code and just do a self clientcommand() in the callback, nothing else. See how that goes and add stuff from there, until it crashes again.
tl;dr: debug using normal methods
"Does not work" is an error report for a bug between keyboard and chair.
All hail Artie Effem
kung foo man (11th August 2015)
I rewrote the code does not once, did conceived in different ways, sometimes it turns out error, when you start card, monitor or predict its occurrence is not possible
I know the words in this sentence but i cannot, at any rate, create a good story out of this
Basically similar to this: http://funnyjunk.com/channel/4chan/U...+test/GeRBGTr/ but makes less sense even.
"Does not work" is an error report for a bug between keyboard and chair.
All hail Artie Effem