[Hawk552]

I'll fix this up in a few days.

[DataMatrix]

Titanium has never been used for bulletproofing, Kevlar is used for bulletproofing.

Why not call it Bulletproof Armour v1.0?

[Voi]

hehe, mb bulletproof vest

[slmclarengt]

@ Hawk552 - please update this plugin to be more accurate and precise because this sounds very appealing but in order for me to use it, it must be stable and accurate (or else my players moan).

Slmclarengt

[MultiShot]

Thanks you Hawk552, i've tested this on my server and havn't found any bugs yet so keep the updates coming and good job.

[Hawk552]

Download added since uploading is now fixed.

[VEN]

new Origin[3] get_user_origin(EntToSkip,Origin,3)

Originally Posted by VEN here Most of a "shot/bullet/shell/fire/trace/particle/projectile/etc" plugin authors instead of fired particle trace vector is use player's aim vector. FYI: the angle difference between such vectors may reach even more than 30 degrees [!] because of the fired particle spreading/gun recoil.

Basically you have to use trace vecEndPos, not player aim position.

[Hawk552]

Originally Posted by VEN Basically you have to use trace vecEndPos, not player aim position.

I actually tried doing that first, but it picks up the point after the first target. So if I shot at you (which I really want to do right now), instead of picking up where it hit you, it would return the wall behind you, or wherever the it was stopped by a/the brush ent/world. I'm really not concerned with it being slightly off in this way, as the sparks aren't really important for anything other than visuals.

[VEN]

it picks up the point after the first target

This can't happen. Parts of your code:

new Ent = get_tr(TR_pHit) // ... // ... if(is_user_alive(Ent) // ...

So basically you hit an alive player and, hence, your hit point (i.e. vecEndPos) should lie on that player.

"bulled end vector" and "trace end vector" are two different terms. Bullet imaginary trail may consist of multiple traces. So if your bullet is hit two players sequentially (they obviously stay in one line) you will have two line traces. Each line is hit different player, hit point vector is equal to vecEndPos traceresult member of the current trace.

I'm really not concerned with it being slightly off in this way, as the sparks aren't really important for anything other than visuals.

If you are not emulate sparks in a correct position, at least do a favor for other plugins, do not "show" your sparks to them (emessages). I do not believe that such "mispalced" sparks will be usefull for other plugins (not to mention that it may even mess some functionality in rare cases).

Summary: emulate sparks correctly or use default message system.

[biglittle007]

I think player's speed should reduce due to the weight of the titanium.. Just an opinion! xD