Malchie Brothers Forums
Welcome, Guest. Please login or register.
September 08, 2010, 12:44:04 AM

Login with username, password and session length
Search:     Advanced search
This forum is for historic purposes only.  Please visit our new forums at http://malachiebrothers.freeforums.org/.
4116 Posts in 969 Topics by 70 Members
Latest Member: RUN TO THE HILLS
* Home Help Search Login Register
+  Malchie Brothers Forums
|-+  Games
| |-+  DoD:Source (Moderator: [MB]Sgt. Fuzzynuts)
| | |-+  tk protection		 0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] Print
Author Topic: tk protection  (Read 207 times)
[MB]Brunt
MB Member
Hero Member
*****
Offline Offline

Posts: 974
« on: January 17, 2007, 10:37:10 PM »
manies tk protection is the stupidest thing ive ever seen.fucking slay or blind your team mate for a mistake.wow yea that realy helps the team out.any for those who ask why its turned off.becuz its stupid lame and dose no good!!! ':angry:'
Logged
[MB]MRLAMEASS
MB Member
Sr. Member
****
Offline Offline

Posts: 256
« Reply #1 on: January 17, 2007, 10:49:15 PM »
LOL, I thought that was a stupid option too,who wants to slay your own team mate when your all working together. '<img'>
Logged
[MB]TheDeceiver
Administrator
Hero Member
*****
Offline Offline

Posts: 880
« Reply #2 on: January 19, 2007, 07:20:08 PM »
They used to run it on the 13th Cav server.  The thing was this.  They would leave it on so that you could punish assholes who were TKing on purpose.  They would encourage people to forgive accidental TKs and if anyone abused it they would just kick the stupid people from the server.  ':p'
Logged
ninojman
Newbie
*
Offline Offline

Posts: 36
« Reply #3 on: January 21, 2007, 02:26:54 PM »
ya we ran it so u could only slay or forgive  all the burning stuff is retarded cuz u get the fire noise stuck
Logged
Pages: [1] Print 
« previous next »
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!
Page created in 0.204 seconds with 17 queries.