Don't do this, people. It helps no one and if anything pushes people away from our community.
Don't do this, people. It helps no one and if anything pushes people away from our community.
@DearFox In the dev community in general, I like Godot, and I encourage people to try it out, but when someone has an issue, telling them to switch to another tool is totally horrible.
It usually comes from young devs who are very enthusiastic over the engine they use, but I've also seen this pattern in older people, really terrible behavior, it only damages everyone.
Thats different. Packages should be tested in a clean build environment. If they work in there, it's a problem with users configuration.
@godotengine "Hey guys I've been working on this Unity project for 5 years now and it's almost ready to launch..."
"pOrT iT tO gOdoT"
I like how there's something named "Godot" that has actually been *released* and is available.
(3rd panel really ought to be "Wait for Godot...")
@godotengine now, to be fair, (and this is coming from someone who spent the better part of a decade doing Unity gamedev professionally) most Unity Answers answers that don't do this are equally as unhelpful.
Every time I hit a non-trivial Unity issue and researched it, all the answers online are either:
So while I agree this isn't helpful, so precious little revolving around Unity is ๐
@shi @godotengine best part is the literal warcrime is likely the only thing that actually works.
For about ten minutes. It will then irrevocably break itself and magically break other working code through its cursed nature.