| What I learned | Uses in my 2D game* | Importance to me** | Gamestudio limitations workaround effect*** |
| Basic syntax style and format | Everything | 1 - very low | Things are considerably more confusing |
| printf() | On-screen text and menus | 5 - moderately high | I don't have to use several ifs to add variations, just a number or string |
| scanf() | Custom inputs as for setting the scaling | 3 - moderately low | None known |
| if, else if, and else | Faster processing of my numerous conditions | 5 - moderately high | Gamestudio has just if and else and excessive use of else causes missing or extra }'s and 20+ levels of indentation making the code messy. The "else if" instruction is of greatest use. |
| variables | Allowing for pitched gliding, slopes, obstacles, more realistic movement, and much more‡ | 7 - very high | The var frequently gets in my due to its low range and accuracy and it adds frustration and great complexity†. I also have to remember to add a ".0" at the end of integers to get floating-point precision, of which I'm no where near used to. |
| for, while, do-while | While and for loops seem to be the most commonly used of the three, do-while with very few uses | 5 - high | for loops are one main thing that could be of use |
| switch-case | My menus, ability usage, some special effects (puff sizes), and some other things. | 6 - high | Just a whole bunch of if statements |
| functions | Everything | 4 - moderate | I have to remember not to use "function" to define one, but what the variable type returned is (void if no returns are used) |
| includes and defines | including headers and defining common things | 4 - moderate | Gamestudio supports both, but I have to remember to add the "#" before it, unlike Gamestudio |
| - - - - - - - - - - - - - - - - - - - - - - |
| What I have yet to learn | Uses in my 2D game | Importance to me | Gamestudio limitations workaround effect |
| Creating waits | Processing functions one per frame | 4 - moderate | Perhaps getting the frame rate set to the monitor's refresh rate for very smooth motion, but otherwise none that I know of. |
| Getting actual program windows in Windows | An open/save dialog (to allow multiple save files) as well as fully customizable resolutions | 5 - moderately high | Gamestudio does not support this at all unless you manage to make your own file system, the closest possible to it, but you still can't get the Windows-like atmosphere. |
| Strings | Displaying text that manipulated by the user | X - unknown | Gamestudio supports it, but, since I don't know what C has to offer, the certainty is very low. |
| Reading and writing files | The save/load system | X - unknown | I have no idea what C offers, so I have no idea |
| Displaying graphics | The scenery and graphical interface, possibly allowing for ultra smooth movement from anti-aliasing effects | 6 - high | It's easy with Gamestudio, but I don't know how C compares. |
| Press a key, something happens, without scanf() | Jumping, gliding, selecting menu commands, and the other game controls | X - unknown | I don't know what C offers. |
| Pointers | Referring to the various graphic elements and possibly other things | 4 - moderate | Gamestudio supports it, but I don't know what C offers. |
| Structs | Unknown (panels and text objects are structs) | X - unknown | Gamestudio has them, but custom ones cannot be made. |
| - - - - - - - - - - - - - - - - - - - - - - |
| Other limitations and annoyances | Uses in my 2D game | Importance to me | Gamestudio limitations workaround effect |
| 3D hardware requirements | Even old computers without 3D hardware can run my 2D game. | 6 - high | 3D hardware is always required and cannot be disabled. |
| DirectX requirements | Even old computers barely with DirectX 6 could run my 2D game - I don't need DX. | 6 - high | DirectX 9.0c or it will not run and there's no way around it. |
| Operating system requirements | Backward compatibility to Windows 98 is useful†† | 5 - moderately high | Gamestudio supports 98, Me, 2000, and XP |
| Hardware requirements | Could work on old budget systems running Windows 98 (300 MHz processor, 32 MB memory, 400 MB hard drive, etc.) allowing for a broad range of audiences | 5 - moderately high | Gamestudio requires higher end hardware shrinking the audience. |
| Load times | Just double-click the EXE and you're already viewing the only logo | 6 - high | You don't have to wait for the "loading SOLYMPICSV24.WDL" notice to draw 2 1/3 lines' worth of dots before the game loads and you need to wait for two logos - this cuts the load time by 4 to 12 seconds, depending on the speed of your computer and whether or not you previously loaded it and have the full edition. |
| File names | I may be able to stick with my usual file naming system for everything. | 6 - high | Only 15 characters and spaces and other otherwise accepted characters are not allowed - annoying in that its so few! |
| Use of Molebox or other file packers | The problems Molebox poses should not pose any problems | 7 - very high | A file packer is required because, without it, the WDL script can easily be read by anyone. |