Chat
Discord
07-26-2008, 10:06 AM
Yes thats right and it works well i cant find any bugs with it but i will use this code:
<frame> 397 telestart
next: 398 dvx: 200 dvy: 0 wait: 0 etc
<frame_end>
<frame> 398 telend
next: 999 dvx: 550 dvy: 0
<frame_end>
instead of this code:
<frame> 397 telestart
next: 398 dvx: 200 dvy: 0 wait: 0
<frame_end>
<frame> 398 telend
next: 999 dvx: -1 dvy: 100
<frame_end>
Becouse that dv?: 550 stops all movement in that direction and if you want it to go to the crouch frame after the teleport just use next:
<frame> 397 telestart
next: 398 dvx: 200 dvy: 0 wait: 0 etc
<frame_end>
<frame> 398 telend
next: 999 dvx: 550 dvy: 0
<frame_end>
instead of this code:
<frame> 397 telestart
next: 398 dvx: 200 dvy: 0 wait: 0
<frame_end>
<frame> 398 telend
next: 999 dvx: -1 dvy: 100
<frame_end>
Becouse that dv?: 550 stops all movement in that direction and if you want it to go to the crouch frame after the teleport just use next:
Age ratings for movies and games (and similar) have never been a good idea.
One can learn a lot from reinventing wheels.
An unsound argument is not the same as an invalid one.
volatile in C++ does not mean thread-safe.
Do not make APIs unnecessarily asynchronous.
Make C++ operator > again
Trump is an idiot.
One can learn a lot from reinventing wheels.
An unsound argument is not the same as an invalid one.
volatile in C++ does not mean thread-safe.
Do not make APIs unnecessarily asynchronous.
Make C++ operator > again
Trump is an idiot.