So it's a simple game.
You simply post the top X rules of Y. (Where X is a number and Y is software/a game/a movie genre/whatever)
An example: (I wrote for a PM)
The top 10 rules of Game Maker:
Guidelines:
Be creative, no one wants to hear all the LFE rules.
Use [list=1]
[*]Rule 1
[*]Rule 2
[/list] in your posts as they make it easier to read.
Have fun.
You simply post the top X rules of Y. (Where X is a number and Y is software/a game/a movie genre/whatever)
An example: (I wrote for a PM)
The top 10 rules of Game Maker:
- Never name a variable/resource something starting with a number, and only use a-Z, 0-9 and "_".
- Never write a string without quotes ('stringhere' and "stringhere"), or it will be treated as a variable.
- Never add real and strings together. Use string(), and real().
- A function can never alter or read from a variable by writing a variable name into it (like variable_local_exists(variable)) write it in quotes instead (like variable_local_exists('variable').
- Extra resources (like data structures, 3d models etc.) can't be created like ds_list_read(list,string). You have to create it before (ds_list_create())
- Never alter resources in use. It will only cause bugs.
- random() can also return 0.
- Never turn "Treat uninitialized variables as 0" on. It causes more problems than it hides.
- Rooms and instances has a Creation code... In rooms its settings>Creation code. For instances its CTRL+Right click>Creation Code... (in room editor)
- Instances and objects are NOT the same thing!
Guidelines:
Be creative, no one wants to hear all the LFE rules.
Use [list=1]
[*]Rule 1
[*]Rule 2
[/list] in your posts as they make it easier to read.
Have fun.
Age ratings for movies and games (and similar) have never been a good idea.
One can learn a lot from reinventing wheels.
An unsound argument is not the same as an invalid one.
volatile in C++ does not mean thread-safe.
Do not make APIs unnecessarily asynchronous.
Make C++ operator > again
Trump is an idiot.
One can learn a lot from reinventing wheels.
An unsound argument is not the same as an invalid one.
volatile in C++ does not mean thread-safe.
Do not make APIs unnecessarily asynchronous.
Make C++ operator > again
Trump is an idiot.