(12-03-2020, 10:07 AM)Kriegstofu Wrote: Tbh, if you wan't any dev to read this, you should keept it as compact as possible, and only if a dev responds back something on the line like: "This is interesting, please elaborate." begin to write a longer analysis
but I'm probably wrong and Devs read everything you write.
Well, look at the post that started this topic. It's not even 50 words yet we are here talking about it still.
Let's use this request as an example [Link]. If I only said 50 words on the topic what would even be those 50 words?
Some times you need to bring up move points In a request because others like It have failed or the person reading It may have personal biases. If your request seems related to other topics people will already have opinions on them. It's more work to read but you can read all full reason on why this person wants something to change. If I say on that I request you should buff Inf and Sniper people have no context on why I feel that way. The more context I have that backs up what I'm requesting the better the chance I have for it to pass.
That request may take some time to read but It's no different than this one. For that, I did my best to explain why I want this to change in 1 post and if you have a look It has a lot better chance In convincing you than this one given I go over everything. On this request, I need to say to people on why I disagree. If anything this request has more to read at this point.
probably not