For me here are some that I can think of:
- I NEVER EVER use comments in my games;
- I use while() procs to tell users to input something else;
- I like to keep all insides of a proc bunched up, then slightly space apart between types on the first tab;
- I filter through lists very finely to get rid of wrong stuff, instead of telling the player, "You can't do that." afterward.
- On graphics, now, anyways, I can't release a game if I think one of it's graphics aren't very good.
- I lose interest in making a game if I can't be playing the alpha version of it by 2 days. I also lose interest in a game if I get too many bugs in the beginning (I guess this would account for all bugs, BYOND and code bugs, but I seem to get alot of BYOND bugs when I first start a game.).
[EDIT]
- I, like Foomer, never ever keep things that deserve spacing, scrunched together.
- I also like to have a different coding file for different things:
Admin.dm
Attacks.dm
ChoosingHTML.dm
Communication.dm
Computers.dm
Computers 2.dm
Custom Level.dm
Custom Level 2.dm
Custom.dm
D Attacks.dm
Dementophobia.dm (The game name .dm file always includes login proc, and anything that has to do with character selection, stating, and contains all the main vars.)
Filter.dm (Every single one of my games contain this file. It is the Filter() proc and uses deadron's dd_replace_text() to replace cuss words with friendly gibberish.)
Instructions.dm (All my recently made games contain this one.)
Items.dm
Levels.dm
Major Attacks.dm
Meters.dm
Movement.dm
Projectiles.dm
- I also like to do as many icons as I can think of that the game will need to be started off, before any coding.
- I never keep multiple strings on one line if it would require a ";" to do so. Otherwise the only time I put multiple strings on one line if it is a) Only 1 other string, and b) The first string is an if() statement.
In the words of the host of Hollywood Squares when someone makes a dumb move: Maybe that'll work out for you...