[SCRIPT] Splitting cycles - best scripting habits.

[Your Computer]

Yes, well, say we have an object like a key. If I use an interact callback (with SetEntityPlayerInteractCallback()) and every object already comes with empty CallbackFunc properties, then I would be going against DRY by creating a whole new function without using the one already there.
I've decided to go with interact callbacks, and tie them all together into a single function later, but if this method is somehow deprecated in HPL3 because it wasn't how the developers figured it would be, then I'd have a hard time converting to the next engine.

In the background the game would simply be calling the same functions available to scripts for the CallbackFunc property. I personally recommend doing it all through scripts (for practical reasons), but there's technically little to no difference between how you setup an interaction callback. Nevertheless, the principles i stated apply more for when you're designing something from the ground up. In Amnesia scripting, you're pretty much starting from the middle. However, this is not to say that what one can learn by the DRY and KISS principles can't be applied to Amnesia scripting (e.g. one of the very purposes of functions is to not repeat yourself).