Thread: Mo Payload, Mo Problems (9/18/2011; 5:30 PM PST)

I was on as well later at night and it ran FINE. Near as I can tell, It stopped after the latest Patch. My theory is this has more to do with a certain vulnerability in Steam or Source/plugins either being closed, or the memory address Offsets changed for it. We'll know for certain if it starts back up again and nothing else is added to the server by FFN itself. IE: If 1 individual was responsible for it, his cover will have been blown if the 10s cyclical spikes return (which DON'T show up on netgraph properly; Just a FYI to people SS'ing them)**....



**-yeah it took me a while to figure this out after taking over roughly a half hour in video caps of it all this time, Doh!

Originally Posted by iller

I was on as well later at night and it ran FINE. Near as I can tell, It stopped after the latest Patch. My theory is this has more to do with a certain vulnerability in Steam or Source/plugins either being closed, or the memory address Offsets changed for it. We'll know for certain if it starts back up again and nothing else is added to the server by FFN itself. IE: If 1 individual was responsible for it, his cover will have been blown if the 10s cyclical spikes return (which DON'T show up on netgraph properly; Just a FYI to people SS'ing them)**....

From the update notes:

- An exploit with non-printable characters causing lag on Windows servers has been fixed