any silly sounding error messages were made that way because they represent a critical error, ie an error that most likely will cause a crash, ie an error that should never happen (and the user should never see). any and all aoob errors should be found and dealt with before they reach that point in the code (once we get that far there is not much we can do but crash, but earlier the error could have been detected and corrective action taken). for example 'graphics error of doom' is because we used something that wasn't available to us, we should have been able to see it wasn't available and not used it. the reason they are given silly messages is because they are errors that mean there is going to be a lot of testing involved for the user to see if we have resolved the issue, some levity seemed like it might help take the edge off the inevitable frustration, also there is absolutely nothing the user can do to fix the problem so it might as well be a bizar error.
now to answer the question of what the aoob error means, well it means an array is out of bounds
an array is basically a contiguous list, and if you try to access something that is more than the number of items in the list past it's beginning you are outside the list and going to cause huge problems (for example if there was code right after the list, you might overwrite the code with data, and then later try to execute that data thinking it was code, executing data is (unless you are doing some VERY freaky ****) what is known as "bad", like 'crossing the beams' bad). the error has no specific cause, and it is, in fact, not a bug per se, it is a symptom of another bug. if you get this error you are pretty much GOING to crash, so I wouldn't worry too much about rebuilding things, considering it is a harbinger of complete destruction.
