[bfprog] Disabling C4 near flag for CTF

[Brigham Stevens]

Andreas Fredriksson wrote:

>On 2/7/06, Brigham Stevens <brs at vikingmind.com> wrote:
>  
>
>>I've done a lot of research on this and almost have my code ready for
>>release.........
>>
>>I found out something about setPosition though, it only seems to work on
>>PlayerControlObject's and the c4 on the map (a
>>"c4_explosives_Projectile") does not seem to be one... I try to move it
>>to (1,1,1) or even just changing the Y (vertical) axis to 1, which would
>>be below the map on most maps! No Joy.... The C4 remains, and the timer
>>task that was looking for it dies when I call setPosition.
>>    
>>
>
>I don't remember the details exactly, but maybe the C4 projectile has
>an armor object, so you could perhaps try destroying it as soon as it
>is dropped within the flag radius.
>
>That way it wouldn't stay behind even if a player throws it in.
>  
>
Hi Andreas,     great to hear from you again!
 
Well I tried this too, and it also killed the task on setDamage....
Probably would work for mines, but Mines are OK near the flag since they
can be destroyed, or removed, and they don't have an unlimited range
detonator that can be pulled as soon as the game announces the flag has
been taken.

So the other thing that would be a joy is to somehow tell which player
threw the c4 into the no-c4 radius. I have seen nothing in the Python
Object API that exposes this... Have I missed something? Is there some
hidden propery..?

If I could tell who dropped the C4, that would be funny, because they
would get slain over and over until the c4 vanished from the map! I
think that happens after 2 deaths tho...

Jeeze if they gave the c4 detonator a max range of 20 meters then none
of this would be necessary!

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.matureasskickers.net/pipermail/bfprog/attachments/20060207/ffddd18e/attachment.html