So er, was going to look more into adding this into my server until a whole big argument exploded out.
I have finally got around to updating the script.
[URL="http://facepunch.com/showthread.php?t=1376557&p=44257064&viewfull=1#post44257064"][IMG]http://facepunch.com/fp/posticons/forums/66/addon-wip.png[/IMG] - Back to top[/URL]
I have added a warning that looks like this when you turn on the damage returning...
[CODE]WARNING: This may be abused. Players may launch other peoples props at them selves thus killing innocents.
Please watch this video about how one may abuse this. ( http://youtu.be/PHiDushdnpo )[/CODE]
I have also changed the prop damage logs to say this...
[CODE]A prop belonging to James[STEAM_0:0:87654321] has hit Henry[STEAM_0:1:12345678]![/CODE]
I have not updated the workshop version yet, because I currently do not have time to test it, so consider this the experimental version.
Update Link: [url]https://github.com/LuaTenshi/GLua/commit/b29124347ff1fe3367c903a1adc610a8f14034a6[/url]
Simple GitHub Link: [url]https://github.com/LuaTenshi/GLua/tree/master/APAnti[/url]
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[B][U]Update April-05-14 (UNTESTED)[/U][/B]
The messages are now cleaned and sent using user messages.
Damage returning can now be turned off and is off by default. A warning
has been added due to the argument that happened over @ facepunch.
Added the ability to alert admins when a prop hits a player. (Please
note that the owner of the prop that is doing damage is not always a
prop killer.)
Changed the way variables are handled, and fixed a glitch with auto
blocking not turning off.
Note: I forgot to take into account the latest Gmod update when updating this script, I will fix any problems that may happen, after I have tested.
I find the idea of opening another thread utmost ridiculous. "off topic" means talking about a different subject. The discussion about how your anti prop kill punishes innocent people is [b]not[/b] a different topic. It's your script and the problems it will cause on servers that run it.
I am still of opinion that it is best to at least leave the detection out. That really is better than blaming someone for a prop kill with the message "oh but I might be wrong!"
I want to see how admins respond to this. I don't think many will listen to the message.
[QUOTE=FPtje;44457832]I find the idea of opening another thread utmost ridiculous. "off topic" means talking about a different subject. The discussion about how your anti prop kill punishes innocent people is [b]not[/b] a different topic. It's your script and the problems it will cause on servers that run it.
I am still of opinion that it is best to at least leave the detection out. That really is better than blaming someone for a prop kill with the message "oh but I might be wrong!"
I want to see how admins respond to this. I don't think many will listen to the message.[/QUOTE]
I hope people will listen to the warning, however if server owners start having huge problems with the option being there I will then be forced to remove it.
-snip-
I have ran a server with this before and found the messages to be very useful to find most prop killers, seeing that most prop killers would just spawn a prop, grab it and fling it at some one. So the damage returning may get removed in the future, but the message will remain as it only states whose prop hit who, and that will always be correct. Do note that this does not always involve prop killing.
Thanks for making me aware about this FPtje, and I hope that we can be friends.
I have finally tested this and I can confirm that it works under the default settings, I will continue testing later and try to find any other bugs that may come up, please try this out for your self and tell me what you think.
[url]https://github.com/LuaTenshi/GLua/commit/44add9d3a43fb13e5ab951a3dbc48a35c7bd09d6[/url]
Sorry, you need to Log In to post a reply to this thread.