lionz's Recent Forum Activity

  • Is the behaviour 'run constantly while it is overlapping' or more like an on hit one time behaviour. It sounds like you've used trigger once so instead you can try 'player on collision with instance'. That should work well enough for a one time hit and you can print the instance UID in the action when the collision takes place.

  • Yes nice, exactly this

  • You just need to put it in the same block you had before, then with the action add set variable to 0.

  • Although they seem like separate events, because you change the variable 1 to a 3, it makes the event below true in time to run it because they all trigger on key press in order from top to bottom. You can try just having the one key press condition then use sub events with 'Else var=1, Else var=3'.

  • You can use a different global variable to lock out the event so it is not always true. So like variable=0 in the condition, then when you show the text in the action you can set the variable to 1. Then it will only run one time!

  • You need to make it so the condition is no longer true, so change the Levels_Open variable? Or if that is an important variable to remain with its current value then use a different variable to act as a trigger once.

  • In theory what you are describing should work but the screenshots are too limited to tell what's going on. If you can share the project I can help. Or try with a very basic event and see if you can get it working to change the volume with a tag.

  • Which add layer event?

  • You do not have permission to view this post

  • Yes 'on collision' is better here

  • Check if you unticked 'enable collisions' on Fire. In theory yes if MagicBeam is working then Fire should do the same thing.

  • You'll need to pay for Construct 3 to access what I was referring to,'Families'. you can put all your bullet objects in a family and call it one time for all. It's so you don't need to do repeat events for many objects. More info in the manual!

    From your last response I see that you want to keep an angle for shooting until you change weapons so yeah a global variable is a good idea, as it is the equipped weapon rather than the bullet. You can also have the equipped weapon as the variable so if weapon ='weaponA' and shoot key is pressed then spawn bullets at a certain angle.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
lionz's avatar

lionz

Member since 5 Aug, 2013

Twitter
lionz has 72 followers

Trophy Case

  • 11-Year Club
  • Jupiter Mission Supports Gordon's mission to Jupiter
  • Forum Contributor Made 100 posts in the forums
  • Forum Patron Made 500 posts in the forums
  • Forum Hero Made 1,000 posts in the forums
  • Forum Wizard Made 5,000 posts in the forums
  • Regular Visitor Visited Construct.net 7 days in a row
  • Steady Visitor Visited Construct.net 30 days in a row
  • Enduring Visitor Visited Construct.net 90 days in a row
  • Unrelenting Visitor Visited Construct.net 180 days in a row
  • Continuous Visitor Visited Construct.net 365 days in a row
  • RTFM Read the fabulous manual
  • Great Comment One of your comments gets 3 upvotes
  • Email Verified

Progress

24/44
How to earn trophies