The game is pretty simple- poke fun at how MFGGers code or just joke about coding in general. 1) When you're having trouble with a lot of if-statements, change to a switch-statement instead. 2) Math? Who cares. You can't handle that much power. With great power comes great responsibility. 3) Just throw code at the source until it works. Continue!

4) Variables take up valuable space in your project that you need to reserve for large MP3 files. Instead, try hardcoding every value. 5) Flexibility is a luxury you can't afford. But it's okay - the game will be scrapped before you need to rework aspects of the game, anyways. 6) The one method your heart truly desires: public void MakeGame(GameObject hero, GameObject[] enemies, GameObject collectible, Font hudFont, float lengthOfGame, ... ) + 2147 overloads

7) Manually initialising variables? Pah! Just go into Global Game Settings and tick "Treat uninitialised variables as 0". 8) Don't ever change the "loading, please wait" box. That red on blue design with yellow font is sleek as heck. 9) Why use "x += 1" when "x = x+1" will suffice?

10) why actually finish your game when you can just trap yourself in a vicious cycle of engine re-writes even though you're a novice?

11) Even though you understand everything, you must comment your code. You MUST. 12) Why use random() when you can use choose()? 13) Use a default icon! Those green-and-black PacMen look good!

14) sprite145 is better than spr_bunny or sBunny 15) Optimizing is for n00bs.

16. Who cares about coding style? After all, I don't have to worry about it until I get a job. 17. Break, continue, goto, multiple return statements? Oh no, those are evil to my computer science teacher. 18. Oh, my professor told me not to use friend classes because they break object-oriented design. Speaking of that, I think the amount of friend classes I use is limited by the number of friends I have. I don't have many friends. 19. Who cares about efficient code? My professor told me to use good object oriented design, even if I have to dynamically allocate particles.

[quote="Qwerty Triple6"]11) Even though you understand everything, you must comment your code. You MUST.[/quote] -11) Never use comments, especially when you understand everything! You can't possibly forget any code you write! [i]Never![/i]

20) Uninitialized variable errors never happened back in Game Maker 8, because that program truly was ahead of its time! 21) Game Maker: Studio is worse than Game Maker 8, because it has a dark skin and it corrupts my projects twice an hour ): 22) Datatypes? What's that? 23) I am a professional programmer, but how do I make enemies face the other direction again?

24) Make like Luigi and do absolutely nothing. Instead, have people do everything for you. You can't possibly fail!

25) why go to the trouble of making functional code when you can have people fix your [i]broken[/i] code?

26) The most important aspect about game development is having an idea. Once you have that, you'll easily find a team to take care of everything for you.

27. I randomly name variables because it's cute. 28. Ugh! I hate queues; it's [i]so[/i] hard to understand. I love computer science though :> 29. Programming is so hard! Simple if statements, nested if statements, compound if statements, else if. So hard! 30. Getters and setters? I just use public fields because I'm lazy. 31. I don't know how to use for loops, so I'll just write 480 lines of if statements.

[s]32) Using for loops can get really confusing. You can get the same results by using a bunch of if statements, and even keep track of your specific variables![/s] ninja'd 33) Uncompressed audio = better quality!

34) Always remember to give your variables distinct names! Name it "ready" and clearly everyone knows what it does! 35) There is a 102% chance loops will crash your game. Always use code duplication and do everything by hand! It also helps make specific cases easier to customize! 36) I managed to fix the bug in my code - I don't know how though :) 37) The bug is back ): Please take a look at my code that consists to 75% of hard-coded numbers

38. Aw, my code has a boo-boo. Band-Aid variables should fix the problem.

39. If you're a GM user, [b]ALWAYS[/b] do everything using Drag & Drop. Do not use GML.

40. Exclamation marks in coding??? That doesn't even follow conventional English! Instead, use a "if then else exit" string.

41. If you're making an engine, add as many features as possible. Remember: by definition, it's not an engine unless it's a completed SMW:ASE-scale-featured game with only three levels.

[quote="DarkBlueYoshi"]38. Aw, my code has a boo-boo. Band-Aid variables should fix the problem.[/quote] Is this a game for poking fun at how MFGGers code, or is this a contest to be as condescending as possible?