I'm putting this here so all aspiring modders notice it. It seems to be fairly common practice around here to release a mod in such a state that it runs in a current release (or 'r', or regular) build, but throws numerous errors and possibly even crashes outright in a debug (or 'd') build. Many people, mostly the non-coder inclined, simply don't understand why this is a problem and release it anyway, either they're in a rush to meet some self imposed release deadline or they just don't want to spend any more time on it, for fear that sweating those kinds of details would kill their momentum, etc. However, as both a coder and modder, let me say that these errors are typically not something you should be ignoring, and I'll say why as best I can. Many debug errors that may seem innocent enough, can cause unpredictable behavior while testing your mod even with a regular build. You could spend countless hours tracking down a bug that is simply caused by a problem the game was already alerting you to, yet you chose to ignore because normally no one would notice.
If that's not a good enough reason, here's another. Everyone around here works as a volunteer. Coders, modders, everyone. When there's something wrong and you think it's a problem with the code, a coder is going to have to look at a lot of things to try to fix it. Coders value their time highly, just as you do. They also have to run a debug build to hunt down the majority of their problems. If they have to click through countless warning messages, they're a) thinking you don't care about their time and b) thinking the problem is probably directly related to those warning message. So, they're likely to be much more responsive to your requests for help when you make it easy for them to help you, by investing that time.
Taking a little bit of time to clean up your tables and really understand what's going on benefits everyone in the long run. It may be necessary to enlist more outside help. Just as not everyone is technically inclined enough to fully grasp every little detail about table editing, not everyone is artistically inclined enough to model, texture, design a GUI, etc. Unless you're truly gifted, typically you'll either be on one of the spectrum or the other, and need a little help to get a good looking and stable mod out the door. There's nothing wrong with that.
Another thing about debug warnings, they're not your enemy. The coders put them in to help you in your development, giving pretty straightforward messages as often as possible when problems arise. That's the reason that more messages show up as development continues, a coder decided it was necessary to include another safety check in an area of the code in order to make your lives easier. So please, stop hating debug so much and try to appreciate all that it can do for you.
