@ftxcommando said in New Player Councilor Discussion + Removal Announcements:
Sadly none of that experience matters for answering these questions (and half of it doesn’t even matter for the position, like who cares that you make map props?)
I was saying that to answer RandomWheelchair's question:
@randomwheelchair said in New Player Councilor Discussion + Removal Announcements:
why didn't you actually try to make this a better place before you set your sights at becoming the PC?
My answer basically equated to; I did actually do things to make FAF a better place before I set my sights on PC... Heck, trying to make FAF better is the reason I'm running for PC...
@ftxcommando said in New Player Councilor Discussion + Removal Announcements:
I shoot down ideas because I know they won’t get considered (through exposure with the people on the balance team) and decide I might as well as give people a rationale for why that won’t happen. You can try to hide it with “oh this would need x and y and maybe it might get considered” but it doesn’t change any of the realities here. You are definitely on the right track though, there’s no point at all in you responding to these posts when you have no experience or frame of reference with the balance team.
This condescending and dismissive attitude is part of the problem... You make many people not even try anymore to suggest or improve things out of negative thoughts/feelings resulting from the way you so often respond.
Perhaps an idea is extremely unlikely to ever be implemented into base FAF; that doesn't mean you need to rudely shoot the person down and discourage them from participating.
By comparison, doing something like mentioning that the person could make their ideas into a mod (and then linking some modding resources) is not condescending and is potentially constructive (and probably doesn't leave the person feeling so badly). Further, I have found many successes in life in trying where others say I can't do X. Your word is not law. Just because you think something will never ever be implemented, does not automatically guarantee that it is so. I think you shouldn't strive to stifle potential innovation.