Hundreds of features to explore
Games made in Construct
Your questions answered
Trusted by schools and universities worldwide
Free education resources to use in the classroom
Students do not need accounts with us
What we believe
We are in this together
World class complete documentation
Official and community submitted guides
Learn and share with other game developers
Upload and play games from the Construct community
Game development stories & opinions
<img src="http://img14.imageshack.us/img14/5845/c2problem.png" border="0" />
on my laptop this works fine but on pc (bettter performance) ghostDead number increasing unexpectedly.
here is capx too.
how can i make a better scoring system?
Move 'trigger once' up to the can<=0, and move Add 1 to ghostDead to after the destroy. Also, you can avoid the Wait actions here by using the built in 'Wait time' for the fade behaviour. Even the ghost can have a fade with a wait of 1 and a fade of 0.001. Also you can move your destroy code to a 'On destroyed' event.
thanks a lot blackhornet :)
But in your capx we can only destroy the first ghost (because of the trigger once). And also i need them to spawn coins. I think i need another solution.
I added another "ghost...can<=0" condition near the trigger once. Maybe this can work.
Ah, you need a ForEach: barbarossa_tweek2.capx
Develop games in your browser. Powerful, performant & highly capable.
Thanks again. But mine too started to work properly. For now at least.