Goonhub
06-16-2013, 05:27 PM
I'm sure many players can attest that using a taser is really dangerous for their owner if there happens to be even a little bit of lag. If you in some way create any projectile, be it by throwing a bowling ball, throwing a butcher's knife or using an e-gun and you go just that little bit too quickly for the game to realize it, it will invariably lead to a really lame situation where you're fucked in whatever high-octane situation you were just in.
It's immersion breaking, its lame, and it needs to be fixed.
There's a simple way to fix it - every player should have a list of IDs from the projectiles that they the player owns. If you discharge a taser, the bolt should have its own ID that is checked on collision and if it ends up that bolt has hit its owner, the owner calls a proc which compares the ID of the projectile to its projectile list and since it will match it should pass through, or at the very least not effect them. There is no reason for any projectile to ever arc around and hit its owner.
The list is purged for the duration that the projectile is in transit, or maybe every 5 seconds.
Another way is to give the projectile itself an ID of who owns the projectile and ensure that it doesn't call on collision effects if it does end up colliding with its owner. I don't know how the collision procs are called, but one of these two methods should easily fix the problem.
Go ahead and add your own story of a super lame self tazing experience. I'm pretty sure everyone has one now!
It's immersion breaking, its lame, and it needs to be fixed.
There's a simple way to fix it - every player should have a list of IDs from the projectiles that they the player owns. If you discharge a taser, the bolt should have its own ID that is checked on collision and if it ends up that bolt has hit its owner, the owner calls a proc which compares the ID of the projectile to its projectile list and since it will match it should pass through, or at the very least not effect them. There is no reason for any projectile to ever arc around and hit its owner.
The list is purged for the duration that the projectile is in transit, or maybe every 5 seconds.
Another way is to give the projectile itself an ID of who owns the projectile and ensure that it doesn't call on collision effects if it does end up colliding with its owner. I don't know how the collision procs are called, but one of these two methods should easily fix the problem.
Go ahead and add your own story of a super lame self tazing experience. I'm pretty sure everyone has one now!
