[bfprog] tk_punish.py and mines

[Joe]

I think you hit it on the head -- It's TOO easy now. Another solution a
clanmate of mine thought up was to have a player only granted X punishes per
a map. Keep it really small and use a variable in the server.con so it can
be changed easily. Once players realize they only have X punishments to use
all game they would probably be more likely to save them for someone that
really made them upset..And ideally, that would be a teamkiller (won't
always..). I like any of the options I've heard now, but I'm tainted because
of the current "friend is foe" nametag color bug. We had to turn off
punishments and that on our pub just because of the combo of idiots and
name-tag-bug accidents. Blarg I say!

-----Original Message-----
From: bfprog-bounces at lists.matureasskickers.net
[mailto:bfprog-bounces at lists.matureasskickers.net]On Behalf Of Einar S.
Idsø
Sent: Monday, July 18, 2005 3:35 AM
To: Battlefield Programming
Subject: Re: [bfprog] tk_punish.py and mines


This is indeed an interesting idea. However, I find it a bit annoying
that we have to think about bandaids like this to a problem that could
have been easily solved:

Let issuing a PTK be a bit more of a hassle. Console + "ptk" worked fine
in BF1942. Now it is too easy to PTK - easier than FTK, which means that
many people abuse it. At the very least, PTK shouldn't be assigned to
the closest key (pgdn) since FTK should always be the default and
simplest way. If you really want to PTK someone, then you should be
willing to do a bit of work for it. After all: You are dead, you have 15
seconds  to fiddle around :)

Einar


ScratchMonkey wrote:
> Has anyone played with changing the TK rules? What's necessary to
> convert a mine punishment to a suicide penalty? I see in the script that
> you get the player and weapon identifier. What's the format of the
> weapon? What do you code to match a mine?
>
> Is there a way to query how long a mine has been deployed? A tossed mine
> kill should still count as a TK, but that can only be done if we know
> how long it's been down.
> _______________________________________________
> BFProg mailing list
> BFProg at lists.matureasskickers.net
> http://lists.matureasskickers.net/mailman/listinfo/bfprog
>
>
_______________________________________________
BFProg mailing list
BFProg at lists.matureasskickers.net
http://lists.matureasskickers.net/mailman/listinfo/bfprog