74. Use identifier names such as "class1" and "var2" so that the source code burglars can't read your code. 75. I'm too scared for code reviews.

76. Using Clickteam's deafult platform engine ALWAYS works! Obviously if you're not doing any work, it can't fail! Right?

77. while using clickteam's default platform engine, let's make our levels way too hard! who cares if people complain, right? i can beat my own game, so it can't be that difficult.

78. It's just a free fangame, I don't have to put any effort into it.

79. Adding a minor feature? Nah, that requires me reworking the entire source code.

(hah, 79 is great!) 80. Make all variables global so you don't have to worry about scope.

Man, these clickteam jokes really hurt my feelings..... Well, since we're on that clickteam subject.... 81. Let's make a public Mario engine in MMF with 500+ lines of events and only a few comments that pretty much explain nothing about what you did and why you did it, but a brief description of what 100+ lines of events are SUPPOSED to do. 82. Make all alterable values with the default "Alterable Value A, B, etc." name so no one can figure out what the hell each value is supposed to do. Sigh...

83. Let's call our variable names like "waa" or "woo" or "yahoo"! That way, we can make it easier for others to modify the engine! :laugh:

84. Let's use an object for every single tile! 85. I love making games with the Hello Engine! I'll be lazy and use this just like an editor to make my fangame! Wheeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee!

Triple post, sorry, but... 86. Put ridiculous comments everywhere in the code.