blackhornet's Recent Forum Activity

  • Here's a couple of ways to use the Timer behaviour.

  • I can't post an update right this minute, but you can fix this manually. Just open the behaviour's runtime.js file and replace:

    var all = this.behavior.my_instances.values();

    with

    var all = this.behavior.my_instances.valuesRef();

    I'll update as soon as I can.

  • 'On collision' is a trigger. You can not combine triggers with an AND. You could use triggers to check for the overlapping of both tires. Make the event an OR block then add the second trigger. Then add the sub-condition to check if both tires overlap an object. You may need an invisible object to test overlap, tied to your platform. See if overlapping the platform works first - I can't say for sure.

  • All of the concerns you mention are valid - each device/OS deals with fonts differently. This has nothing to do with C2. Fonts are always managed by the device. The only guaranteed mechanism for all cases is to use SpriteFonts.

  • In that case, you need the opposite. If you want to know who shot which bullet, you store the Enemies UID on the bullet.

  • Just store the UID when you spawn it. Use an instance variable on the Enemy, if that makes sense. This is only if there is one bullet at a time. Otherwise, you'll have to provide more details on what you are trying to do.

    Enemy.StoredBulletUID = Bullet.UID

  • You need to try a few more tutorials. C2 is a repeating script - your event sheet runs every tick, so your event is being repeated constantly. For now add 'On start of layout' and drag your event as a sub-event of it. It will then just run once.

  • You are a victim for the old "can't create an object and pick it until the next top event" issue. Your LogoTrigridPiece objects can't be picked in event 15. This is a known artifact of C2's architecture. You just need to make a second "On start layout" immediately after the first and move event 15 under it. I still don't think it is doing what you want, but this will get you closer.

  • System:Compare two values

    First value: Variable >= 50 & Variable <= 60 | Variable >= 70 & Variable <= 80

    Comparison: Equal to

    Second value: 1

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • I've been going round in circles trying to figure out the minimal steps to leaving a room (a lobby I've set up in one app), so that I can then join a new room for a paired-separate game with a host and client, that have nothing to do with the lobby, which is a controlled host. I've tried using Signalling:Leave room, and On signalling left room do a new Join, but the join doesn't do anything. I've tried using Room:Disconnect, and On peer disconnected doing a new Join, but again, the join doesn't do anything.

    Thanks.

  • Just use two conditions:

    Make the first one:

    System:variable >= 50

    then 'Add another condition':

    System:variable <=100

blackhornet's avatar

blackhornet

Early Adopter

Member since 28 May, 2012

Twitter
blackhornet has 26 followers

Connect with blackhornet