Tom, read Riker9: 101, everything that is known (including my small supplemented codes) is on there.
LIT: I precicly hate long var names, can't stand them. But looking at the whole code at once, that is room for failure.
As you see more of a picture, individual aspects are lost, as you see less of a picture the meaning is lost. (Some miss-quote of some thing)
My point being that you can't take it all in, you have to go step by step. Although problem with FPSC-Game.dba is that you can't tell the beginning from end. Or where things are running. I can only tell you what the subs are doing, it is so much to go though.
But be thankful for lee's comments, the most comments you get out of me is just what the following code is for. Not how it works, not what it does to do it, just what it is for. And at that, I am very broad. ex. Script Commands (that would cover everything in the script's section). Commenting is more like separating code, If I need to get somewhere, I need a place marker, so I don't sort though the code to find it.
(Besides, I have an impeccable memory, right now, I am thinking of something I programed 3 years ago, and given the time, know excatally what the code was. I can pick up most projects that I dump and start working on them, but the biggest things I have to do is unravel the math-e-matics (including for-next [they are mathamatical routiens]))
Merranvo, The Cool One
Anti-Noob Justice League, an ANJL of Mercy.
