Link to .capx file (required!):
Steps to reproduce:
Just look at the events for mouse fire. According to the logic a bullet should fire when:
1, The mouse button is held
2, There isn't one on the screen already (inverted on-screen logic)
But nothing fires.
ramones came up with an alternate method using an "else" which works and I'm using for now, see:
I suspect negative logic for "on-screen" isn't working as intended.
No bullets are fired.
Mouse fires bullets, only one can be on screen at a time, thus fire rate is quick for close targets, slow for far targets.
Operating system & service pack:
Win7 64bit SP1
Construct 2 version: