Well some of the errors I get, make no sense at all, let me explain.

Well I can obviously read if it says can't open tag name due to not having a file linked to the tag, but what about when you get exceptions in your debug.txt, and have nothing saying about any file names and it doesn't make any sense what so ever? Or when you have maxed out your memory space in your tags folder.

I really want to know how to read those errors, so I don't have to post about it here. Can someone please explain how you can figure it out?

Some simple minded folk cant read text when it is in front of them.

Post them here and there's plenty of people who would be willing to help you out.

(But it goes in Technical BTW)

Google search the error, and see what people said about it. The most common one is 3157, which means that something is corrupted. The next string after that says what it is, like animations, or bitmaps, or sounds.

I know how to read debug -_-. I am wanting to know how people read the error, for like when your scorpion tags are corrupted. It makes no sense, and I don't have any errors,yet atleast lol.

Read above.

You look at the error, then think of the last thing you did to your map. Whatever you did last is causing the error. This is elemenatary stuff here :\
Edited by UnevenElefant5 on Jul 30, 2009 at 07:50 PM

I believe what he's asking is not the 'how do i tell whats wrong' but rather how do i read whats wrong....

Heres how error code works. It is very basic and direct. When you have an error that shows in the command lines(normally they appear when you compile something) it will say specifically whats wrong and why for example
error: haloce/tag file/weapone name: MAC Canon/collision geometry error/max parameter not set

Its saying that the MAC canon has no proper collision geometry. Most code reads like this but often times its less complicated and shorter.

Aren't those the same things?