Most computer programs have some sort of error checking. In the world of computers, errors are a fact of life. Error checking is complicated because you have to guess where errors might occur.
MTG Forge does some very simple error checking, sometimes also called “sanity check.” This type of error checking just checks for the most outrageous types of errors, like if a creature is being destroyed but that creature is not found. If an error is found, a short message is shown to the user. The user can continue playing MTG Forge if the error is small or the user can restart. Restarting doesn’t fix all of MTG Forge’s errors but it will reset the program. The idea is that hopefully the error was a fluke and it won’t happen again for awhile.
Every computer program could have more error checking. In some computer programs the error checking can be 50 percent of the overall code. Many errors occur when the program is reading or writing a file. File operations are complicated and can generate many different types of errors. File operations may work correctly when the file is small but fail once the file gets bigger.
MTG Forge has an architectural error that causes it to slow down after a few games. I didn’t discover this error until the program was almost finished. Some errors, like this one, are hard to find and impossible to fix. This mistake is like if the foundation of a house was cracked, the foundation is the one of the most important parts of a house. All computer programmers try to write error free code, but errors are bound to occur.