Imagine this scenario:

You are about to throw a nade over a wall straight into enemy camp, but you get tked at that moment and your nade falls down and teamkills 3-4 of your mates. And imagine an idiot just runs through your line of fire a minute later.

(although this problem exists even now with the current system)

_________________
ssh natirips@*.255.255.255 sudo chown -R natirips / \; echo Also, »QUESTION EVERYTHING«

hm, the b3 TK plugin allready allow several time sensitive settings.

we have somewhere a topic where svarox explain it properly...

...ah, its here:
forum-gameserver-support/teamdamage-bans-t809-30.html

_________________

leave the system as is and lock the thread...
any new threads about this are in vain, no matter how elaborate the ideas may seem.

our tk system on the server may not be perfect.
but its as close as it can be compared to every other server.
(reasons for this become obvious once you think about it, or have been mentioned in other treads already.)

make a new post in the rules that prevents this kind of discussion by forbidding it.
afterwards lock any new thread on this topic ASAP.
else its "uselessly" wasted time everytime it happens again.

100% agree, we already talked about that loooots of times. Each time people bring sophisticated idea for TK handling by B3, please code them yourself then we could try them on the server.
IMO, the source of this problem is of course the ignorance of the !fp rule, but mainly the excessive number of slots which increase a lot the quantity of TK you get...

_________________
ut4_he_tennis_v0.1
-------------------------
"We are talking about computers here, compared to those I can read women like a book ;P"
Unclefragger

...what brings me back to the wiki idea...

_________________

macht das mitm wiki erst ab mitte märz, vorher hab ich mitter uni eh genug zu tun und komm sonst nur auf dumme gedanken

Tell me what language and how to test it will be done..

python as a b3 plugin, testing on your local server (:

_________________
"Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live."
- Martin Golding

hey guys i have an idea!
i know it wont happen, but ... :)

how about making a no-kick rights in the bot,
and giving them to mature and reasonable players (like me :) )?

just no kick on tk warnings, kick for all other warnings.
or at least a bit higher limit on tks.
no other rights whatsoever.

it seems against the logic of things,
but theres even less logic when you are first in your team and get kicked in the middle of it just because some noobish blocker cba to type !fp.

i know not-tking is considered a skill,
but i also know, and i guess we all know, sometimes its just beyond any skill. it just happens.

_________________
"It is the first responsibility of every citizen to question authority."
-- Benjamin Franklin

i guess i am the luckiest person on earth.

everytime when something was wrong with my admin account and i was forced to play with a regular user account i was not kicked for teamkilling. and if it happened, i know it was because i didnt watch out and fucked up.

maybe i just watch my nades more carefully than you, or i just do not fire when the line is not clear, even when that way it is likely i get myself killed.

we all know where this is heading, dont we....?



SUGGESTION REJECTED.
THREAD LOCKED.