Haven't been killed by a troll yet, only by people who accidentally hit the kill bind or missed the one person being far away and still alive in super big teams.
mind
Haven't been killed by a troll yet, only by people who accidentally hit the kill bind or missed the one person being far away and still alive in super big teams.
There even already is a time based kill protection, maybe there was some logic reason why this already is implemented. And to some people there are simple logic reasones why it should be more expanded.
07:29
But keep talking about only trolls hitting kill or that me unbinding kill will fix this.(edited)
mind
There even already is a time based kill protection, maybe there was some logic reason why this already is implemented. And to some people there are simple logic reasones why it should be more expanded.
This has nothing to do with big ego... most of the requests are not worth
07:47
Developing features is time consuming, but before you can start develop a new feature you have to find solutions for bottlenecks or any other problems that might appear
07:48
Fixing them during usage is not user friendly nor economic
This is one more thing of negative impact you guys have.. You're proposing a feature & you're not thinking about future problems nor bottlenecks. Feature proposals in general are nice to have, but they wont be implemented if its for less than < 20% of our userbase ( no time for that right now ). The next big thing is impatience... before we gonna start implement new features we have to think about this feature in detail. What are some cavecats... in this case following questions are open:
Who is the owner of a team? - The creator? ( Okay well)
What happens if the team owner leaves the server?
What happens if the team owner gets a timeout?
How can the team owner transfer the ownership to another user?
What happens if the team owner itself presses the kill bind?
Do you have to write /kill in chat? - Some users will bind that too then
Infinitely flexible. Incredibly productive for teams of all sizes. Trello manages everything, from big project details to micro tasks. Collaborate anywhere, even on mobile.
2
08:06
But ofc without exposing new secret features
08:07
Or shall we expose secret features? no more secrets then
I think Avo has the right point here, if you accidentally press kill its definitely your fault and it would be wasted time developing just because of your comfort. (I have killed many times far on an insane map so i definitely understand your pain) I recommend to bind your kill key far away from your WASD so you will most likely not press it by accident. Why develop such feature if the user can fix it for himself and there are other features which have way more impact than this. Im not denying it completely, maybe in the future it can be developed when we gain more players facing this issue.
5
Noke
/lockkill looks like a huge feature, should take some months to be developped
It's not your own fault if someone else hit the kill button.
09:23
And there is a big difference between a statment like "this is not high priority atm" and final statements like "this doesn't solve a problem" (when it actually obviously does...) or "It's pointless".(edited)
Yes, and you know what already happend to me after unlocking the team. Someone wanted to play in t0, he missed that the team was unlocked at the start. He hit his unlock key (to savely kill) before hitting kill.
You are completley missing my point. I'm not talking about me wanting to go back to t0. I'm talking about getting killed by someone else in larger teams.
Avolicious
This is one more thing of negative impact you guys have.. You're proposing a feature & you're not thinking about future problems nor bottlenecks. Feature proposals in general are nice to have, but they wont be implemented if its for less than < 20% of our userbase ( no time for that right now ). The next big thing is impatience... before we gonna start implement new features we have to think about this feature in detail. What are some cavecats... in this case following questions are open:
Who is the owner of a team? - The creator? ( Okay well)
What happens if the team owner leaves the server?
What happens if the team owner gets a timeout?
How can the team owner transfer the ownership to another user?
What happens if the team owner itself presses the kill bind?
Do you have to write /kill in chat? - Some users will bind that too then
well, sorry avo if my topic made other people do the same mistake as I did
18:55
but they were more agressive towards their argument which isn't ideal for a feature request. might as well respect the moderators or above staff for it to be a viable conversation
18:55
♂️
18:56
(even qshar would have told us the same thing, it would be less usable if only a certain percentage of the community uses it)(edited)
Why are ppl complaining about a free to play game .. especially when you see that avo is obviously trying hard in the background to give us a better gaming experience. you should remember that he sacrifices a large part of his free time for this community. and as a thank you he gets stupid comments and reproaches