missile(type,start,end)
Problem description:
Is it possible to make the obj shot out using the 'missile proc' not have an ending? Like when the obj goes past the end, it just keeps going. Or how does the missile proc work?
Code:
Problem description: Is it possible to make the obj shot out using the 'missile proc' not have an ending? Like when the obj goes past the end, it just keeps going. Or how does the missile proc work? | |
Jun 3 2012, 10:14 am
|
|
NNAAAAHH
 |
The missile proc simply sends the type from the start to the end, then vanishes.
|
NNAAAAHH wrote:
The missile proc simply sends the type from the start to the end, then vanishes. Yes. I'm saying how does it do that | |
It draws a line between the start and the end, then vanishes. This is just a visual effect really.
| |
NNAAAAHH wrote:
It draws a line between the start and the end, then vanishes. This is just a visual effect really. You just repeated what you said in different words then added "this is just a visual effect really." ... I'm saying if you wanted to code the 'missile proc' how would you do it? | |
It's a purely graphical effect, handled entirely on the client's end. There's no way to soft-code an equivalent that operates on the client. There is no actual object attached to it, just an appearance. However, if you update the location of the 'end' atom, the client-side affect will readjust to go to the new location (assuming it hasn't already reached the end and deleted itself). I used this trick in a GIAD entry once.
If you don't need a client-side effect, I would suggest checking out Shadowdarke's Pixel Projectiles or some of the other projectile libraries. Basically you calculate an x-speed and y-speed, and move the projectile via pixel_x/y or step_x/y each tick. | |
If you wanted a missile to endlessly fly, I would instantiate it as an object (don't use missile()), create a new object, then add to its coordinates in the direction you want it to go. Once it has gone say, 100 tiles, delete it.
| |