Author Topic: This video is 100% accurate (average call of Duty gamer)  (Read 1811 times)





hitscan=instant hit

It isn't instant hit, nor did I even imply it was..the animation of the knife is delayed compared to the player model.

Example:
I knife

100-300 milliseconds later my player is actually doing this attack therefore making it seem like you attacked first but really they did.


Not torque engine, br0.
What?

It isn't instant hit, nor did I even imply it was..the animation of the knife is delayed compared to the player model.

Example:
I knife

100-300 milliseconds later my player is actually doing this attack therefore making it seem like you attacked first but really they did.
That's mostly caused because of lag.

its not pythons
its pylons
read chat >:|

What?
I wouldn't call them Hitscan in a non-torque setting, weren't hitscan weapons named after a command? Or am I htinking of something else?

I wouldn't call them Hitscan in a non-torque setting, weren't hitscan weapons named after a command? Or am I htinking of something else?
Hitscan attacks have been called hitscan since the Doom days.

It's because the code for the attack usually scanned to see if the attack was a hit or something of the like.

Hitscan attacks have been called hitscan since the Doom days.

It's because the code for the attack usually scanned to see if the attack was a hit or something of the like.
Ah, I was thinking of Raycast!

forget OFF IM GUNNA stuff IN YOUR loving MOUTH

'shut up you loving gorilla'