Making things the hard way

[kyonides]

The problem with said safeguards is that it doesn't teach the game developer or the scripter what kind of errors they are currently making. What would they get from displaying an invalid month? Nothing plus they wouldn't know where the error is being hidden by the safeguard.

If we were talking about stuff like a disposed bitmap in RGSS that will be soon recreated, safeguards wouldn't be a bad idea for it would skip something that's become unnecessary in that specific case. Passing wrong arguments is a serious mistake and should be treated "harshly" by calling raise. When you add safeguards in let's say C-like code is because you know there will be times where you don't expect the code to find a value worth processing. It's be like and else statement for cases when an actor did not pick a special skill listed in a series of if or case when statements. Then a safeguard would be justified for they should exist too many other skills that don't trigger any special handling like extra animations or attacks.

One of the problems of developing RGSS scripts is that we aren't used to making test units to "programmatically" define if our scripts work as expected without abusing of the overheaded payload of our code while executing. We could say we're still coding empirically sadly.