as far as i remember, there are functions defined in the engine code (i remember them being called legacy functions) that you can't package because when looking for the 'code', it finds the engine-defined one before the torquescript packages and whatnot, so it doesn't even attempt to allow for packages.
could be wrong on that, but i remember someone saying that in the past
When the engine looks for a function, if it's defined as a
ConsoleMethod from the engine, it will use that. Otherwise, it will look at TorqueScript defined functions.
Now, when you're packaging it, it's trying to package an unexistant function named "echo", thus just creating a new one.
However, it will never be used because it will just always use the engine defined variant.
