3 replies to this topic

[eddythedreamer]

Hey All,
I am just trying to get my top down game to work correctly. I am sending enemies to the main to fire on him, which works fine for the first instance only, not any other (then when i kill him, he regenerates and he shoots again).
I am using the Alarm 0 to shoot (create enemy bullet @ enemy.x/enemy.y), then to set Alarm 1, which shoots and resets Alarm 0. Works great for continuous fire for 1, but not for any others. Please help. Code or D&D is good.
Thank you.

[TechnoGeek4681]

If your code or D&D actually uses enemy.x or enemy.y, that's your problem. enemy.x will pick a certain instance of the enemy object on the screen (lowest instance number i believe). What you actually want is to use the variables self.x, self.y or even just x,y (which works the same way). This is all assuming your code is in the enemy object, which I assume it is.

[lukew23]

Hey All,
I am just trying to get my top down game to work correctly. I am sending enemies to the main to fire on him, which works fine for the first instance only, not any other (then when i kill him, he regenerates and he shoots again).
I am using the Alarm 0 to shoot (create enemy bullet @ enemy.x/enemy.y), then to set Alarm 1, which shoots and resets Alarm 0. Works great for continuous fire for 1, but not for any others. Please help. Code or D&D is good.
Thank you.

rather than create bullet at enemy,x/enemy.y, create it at to 0/0 and tick the relative box. This will create it at that enemy's place, rather than at enemy.x/enemy.y, which is the loction of the first enemy created.

EDIT: ninja'd

Edited by lukew23, 10 March 2012 - 02:47 AM.

[eddythedreamer]

FANTABULOUS!!
Both options worked! I was thinking a step or two too far. I forgot to think of the "enemy" object as itself! So, setting to 0,0, relative worked, and/or setting to x,y,not-relative worked.
Thank you both!