Nice codes
But let's go back to our subject...
Finally I made the scoring system:
Usual scores:
9 points for graphic
9 points for useability (Keyboard handling, mouse ect)
9 points for sound and music
9 points for story and gameplay (Is interesting?)
5 points for challenge (How hard is the game or how can it be set)
9 points for replay (Will people play it again, or delete)
100% QB scores:
25 points for complexity
25 points for speed
Complexity:
Maximum if only using what is documented in QB
-1 if using up a memory location (like A000), or a built-in fileformat (for each one)
-1 for each port group (For example palette changing takes place on 2 ports)
-10 if using the basic library, -5 for each used interrupt
Using FFIX: You can do it freely, but the scoring will take place on the FFIXless
version of the program.
For example if you have a program using the basic library (-10) for mouse handling
(-5) and using the A000 location (-1), and uses up that the first two byte of GET
stores the X and the Y size of the image (-1), you will get 8 points.
Speed:
The program's speed without any library or assembly speedup
30 points if it runs on the original 4MHz PC
25 points if runs on my 33Mhz computer
After: -5 points for each 33Mhz until 133Mhz
(66Mhz: 20, 100Mhz: 15, 133Mhz: 10)
5 points if needs 200Mhz
0 points if needs 300Mhz or more
This is not the final. You can tell it if You think this is wrong.
On this system an empty program would get 50 points. To prevent this the two part
will be divided, and scored independently. The final score will be the double of
the worse.
Using libs - again: I am upset because of it because they can put up good games, but I can't because I program in C :???:
This annoys me... Why they can do, but I can't ???
Of course I program in QB too... But if QB then pure QB