Am I the only modder in existence that doesn't care about the lack of documentation?
There's a loving trace() function that tells you the parameters of every function and the functions it then calls from there. If you can't interpret how a function like miniGameCanDamage works from the name, then you might need to reconsider how you use your time. For Torque functions, every single last one has an explanation of how it works if you just call it with the incorrect number of parameters. Need a complete list of all Blockland functions? dumpConsoleFunctions();.
There is nothing that Badspot would document that would be any more helpful than a combination of these methods of figuring out how stuff works. It might make it easier because all you have to do is open up your web browser and search for a function, but it's not like documentation is necessary.
And you know what? We even have an absolutely massive unofficial documentation of the Torque language and Blockland functions in particular. You might have heard of it: it's called the Coding Help board. It's literally the single largest TorqueScript reference on the entire internet. If you google your TorqueScript problems, there's a 9/10 chance you're gonna find the answer on the Blockland Forums and if not you'll find it nowhere. And the best part is, it's not even a static documentation. You can ask questions whenever you want and dozens of qualified coders will come to help you. So next time you're thinking, "Wow, I really wish there was documentation for GameConnection::Kill()." just go to the Coding Help board and post a topic saying, "Hey! Can somebody explain to me how to use GameConnection::Kill()? Thanks!"
