Launch or Create Object actually creates two of the object, not just one.

[LemonyLime]

So, I have a spaceship that fires bullets. Whether I use create or launch object, it creates two of them at a time, and I see no reason for it to do that. They're created right on top of each other so you can't visually tell, but this causes them to do twice the damage they're supposed to, animations only play on one of them, and obviously this adds to object count, which I'd like to keep to a minimum.

Here's my code: (As far as I can tell, no code outside of this should have any effect on it at all.)

[Spike]

Try swapping the order of your last event, Launch the bullet after you set the value of fireweapon to 0 not before.

[LemonyLime]

Doesn't change anything.

[LemonyLime]

That's exactly what I'm doing... except I used launch object in this case (makes no difference in the effect). The get value statements are essentially just alterable values, which control how quickly the weapon fires and which weapon is being fired(there are 5).

[RhysD]

Have you tried adding the condition, "Only one action when event loops" from the limit conditions menu?

[ChrisBurrows]

Add a "Run this event only once" condition and see if it still fires two bullets. If it only fires one, it means your launch event is being executed twice which I suspect is the case. Possibly you have another event somewhere interfering with the PLAYERfireweapon variable?

[LemonyLime]

^ It still fires two. No difference whatsoever... except that it only fires them one time with that.

[Spike]

I am still looking at this and thinking it's an event order issue..

The event 'repeat while A is down' is constantly checking, which means as long as the PlayerReload is greater than the value it needs to be, it will keep triggering the event.

In other words I think this happens -
- PlayerFire becomes 1
- You Fire
- You set PlayerFire to 0, but you are still holding down A (remember this is constant, not done per loop iteration), and reload is above the required value so fire is set back to 1
- You set reload to 0
- Yet PlayerFire is still 1, so the event runs again
- You Fire
- This time you set fire to 0, and reload hasn't yet reached 200 again (or whatever value), so you don't get PlayerFire set to 1 again.
- You set reload to 0

Done..
This is how I read the event? Could be wrong

[ethanjubjubi1]

I am having the exact same problem. Can someone help?