I think there are a few critical realization here, that might be missing, and are important to actually speaking about Torque -- or any software development tool -- in a meaningful way, that isn't just, "Well, I like the engine, but add this, that, and the other thing, and I'll consider using it." Torque3D fulfills a different function, for a different set of people, than many other engines (i.e. Unity, Unreal, etc.). If there's any triple-A engine it could be somewhat -- but not very -- reasonably compared to, setting aside budgets, staffing, adoption, and other similar concerns, then it would be Unreal Engine. Even then, only in the sense of why someone would adopt T3D instead of Unreal Engine, and it probably applied more before the current iteration. And, yes, there are very good reasons. They just probably aren't the reasons most of the people making demands or offering vague suggestions have ever thought about in a clear and meaningful way.
The reality is, most novice developers don't even know where to start asking the right questions, and the problem is that they start offering vague, and offensively worded solutions in the face of that. Do those making such claims, in similar situations, perhaps see why that makes people angry, and may not be entirely appropriate?
More realistically, T3D might be compared to other open source engines such as Godot, Urho, Quake, etc, and then only along the vectors that matter. These engines also don't solve the same problems for the same sets of people. That's a good thing. They are options that exist for different groups with different needs.
What are appropriate questions to ask?
For starters, let's try: given options x, y, and z, all tools that seem to me like they will contribute to the completion of my goals, which will help me reach those goals while possibly also, as a bonus, meeting my secondary and tertiary requirements? As opposed to: tool x has good features, but it's missing other good features from tool y -- why aren't the people behind tool x implementing the features from tool y, so that I don't have to think about this problem?
Other important questions, that I'm not sure enough people ask themselves, might be: what am I doing; why am I doing it; what do I see as the best and worst case outcomes; am I trying to maximize one side, or minimize the other? It might be useful to start there, and iterate until the right path shows itself.
Another, possibly unrecognized realization, is that unlike other parties offering "free" tools, the reason for this one are very different. Az has done a good job of pointing out what some of those are. But is it clear why other companies are offering free solutions, for those that seem to think "consumers" are powerful, driving entities in this domain? This engine has no need to harvest vast amounts of personal data from users; or foster adoption from a truly mind-boggling number of people to recoup losses or drive sales; or to establish dominance in terms of mind and market share with the hope of creating a monopoly in the industry.
Anyway, that's all just a brief attempt at offering perspective, from one hobbyist to others that seem to need it, and genuinely not intended to be offensive. If it did offend anyone, I'm glad, and I hope you take that pain and doing something positive with it.