Funny Changelog

* fixed a mem leak in the container cleanup functions
* fixed a mem leak in xform cleanup functions
* decided to stop smoking crack before I code cleanup functions

Real hacker in action

 * And f*ck you PHC you no talent bunch of f*cking script
 * kiddies. You’ll f*cking shit your pants when you see a real
 * hacker in action. No I dont rip code, but you bitchs cant
 * tell a piece of code from an apple pie, so shut the f*ck
 * up.


// I couldn’t find ONE F*UCKING WAY to do this in the
// initialisation directly and I’m REALLY P*SSED OFF!

Spanish inquisition

 * I confess: this is a hack. 
 * I didn’t expect the Spanish inquisition.

Not for sale

/* Really do the RPM-management! This is probably the most
 * important part of this program! Want to rent this space
 * for commercials? No, just kidding! Not for sale! ;-) */


Yadda yadda disclaimer yadda probably not perfect yadda
well it’s okay anyway yadda yadda.

OS-specific uglyness

sorry about this piece of OS-specific uglyness. These were
pause triggers before the days of utilGetPidlist(), and are
now tacked on at the end of the guard list for
compatibility’s sake. Yes, they really are needed – I’ve seen
people curse these two till they were blue in the face, not
realizing what the heck it was that so crippled their
machines. Yeah, yeah. win9x stinks. :)

Michael! What are you doing?

Michael! What are you doing? You’re messing this all up!
Who the f*ck are you?
Your conscience! You can do better! I can do this way
cleaner. I know! This is just another terrible hack. Stop it!
Shhiiiiit, who cares? It’s too goddamn late you bastard. You
should have come up with that earlier. This game is down on
its knees already. Dying from hacks spreading like cancer…

Count on crashes

like there’s ever going to be wrap around with a 32-bit
unsigned int! how long would that take? Let’s see... even if
we somehow generated 100 packets per second, we’d need to
run for over 1 year, 4 months straight. I suspect this
client, or the machine it’s running on, will crash way way
way before then. Ah, windows. Being able to COUNT on crashes
is SUCH a lovely thing. F*ck, whatever.

Fight Club

 * The first rule of fight club is:
 *   You do not include ssl/ssl.h.
 * The second rule of fight club is:
 *   You DO NOT include ssl/ssl.h.
 * The third rule of fight club is:
 *   If you include util/error.h before ssl/ssl.h,
 *   the compilation is over!
 * The fourth rule of fight club is:
 *   Only one inclusion of ssl/ssl.h at once.
 * The fifth rule of fight club is:
 *   If you include ssl/ssl.h, it comes right after elinks.h.
 * The sixth rule of fight club is:
 *   No ssl/ssl.h in other .h file, no complaints about
 *   the rules.
 * The seventh rule of fight club is:
 *   The compilation will go as long as there is still
 *   something to compile.
 * The eight, and final rule of fight club is:
 *   If this your first peek at this .h file, you
 *   (Apologies to Chuck Palahniuk.) */
Page 1 of 41234