99Instances2Go's Forum Posts

• • 99Instances2Go
  • 
  • • Joined 12 Feb, 2016
    • 
    • 8 topics • 2,454 posts
  • 1

  • 23 Jun, 2017
  • Quote

  Perhaps you have 'Wrapping' set on Character with a box that is 2 small ?

• • 99Instances2Go
  • 
  • • Joined 12 Feb, 2016
    • 
    • 8 topics • 2,454 posts
  • 1

  • 23 Jun, 2017
  • Quote

  Dont matter that much.

  When spawn ... it is the spawner that provides the coordinates

  System create needs coordinates.

  The most important key in there is pairing the Fade behavior with the scaling, and use the global loop to add a value to the scaling.

• • 99Instances2Go
  • 
  • • Joined 12 Feb, 2016
    • 
    • 8 topics • 2,454 posts
  • 1

  • 22 Jun, 2017
  • Quote

  Just so you know.

  Most movement behaviours have a build in 'clamp' system.

  Meaning, they have a 'max speed'. Or, speed is clamped to that maximum.

  Just calculate/experiment the acceleration to your needs.

  The acceleration is a natural log. Not linear as in 'speed+1'

  https://www.dropbox.com/s/nnbjt6fupz580 ... .capx?dl=0

• • 99Instances2Go
  • 
  • • Joined 12 Feb, 2016
    • 
    • 8 topics • 2,454 posts
  • 1

  • 22 Jun, 2017
  • Quote

  All together, and in a loop.

  https://www.dropbox.com/s/wufajac41g3tx ... .capx?dl=0

• • 99Instances2Go
  • 
  • • Joined 12 Feb, 2016
    • 
    • 8 topics • 2,454 posts
  • 1

  • 22 Jun, 2017
  • Quote

  https://www.dropbox.com/s/8dabfxdftge85 ... .capx?dl=0

• Try Construct 3

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

  Try Now Construct 3 users don't see these ads
• • 99Instances2Go
  • 
  • • Joined 12 Feb, 2016
    • 
    • 8 topics • 2,454 posts
  • 1

  • 22 Jun, 2017
  • Quote

  On (arrow) collision with (Wall) <--- picks the correct arrow, and does it only once, i assume that you know how to stop it

  System > Pick by comparison ... Trail .. Trail.UID = Arrow.PinnedUID <-- picks the pinned trail (if only 1 pinned)

  ____________actions .... whatever you wanna do with those 2 picked objects

• • 99Instances2Go
  • 
  • • Joined 12 Feb, 2016
    • 
    • 8 topics • 2,454 posts
  • 1

  • 22 Jun, 2017
  • Quote

  https://www.dropbox.com/s/y1is3vuqolfic ... .capx?dl=0

• • 99Instances2Go
  • 
  • • Joined 12 Feb, 2016
    • 
    • 8 topics • 2,454 posts
  • 1

  • 20 Jun, 2017
  • Quote

  Event 99 is a 'on creation' trigger that runs 'in place' (of the creation action) and tries to pick before the next root event. The wait in there tried to fix that in a wrong way. Use opacity and kill the (wrongly placed) wait to understand that event.

• • 99Instances2Go
  • 
  • • Joined 12 Feb, 2016
    • 
    • 8 topics • 2,454 posts
  • 1

  • 20 Jun, 2017
  • Quote

  Example.

  https://www.dropbox.com/s/4unsx00ks998i ... .capx?dl=0

• • 99Instances2Go
  • 
  • • Joined 12 Feb, 2016
    • 
    • 8 topics • 2,454 posts
  • 1

  • 20 Jun, 2017
  • Quote

  The concrete problem is this. I was reading the events in the project in this post.

  I wanted to explain that the logic for the events with parent event 99 is broken because of that "you cant pick a newly created object before the next root event ". But, then it struck me that all the key press events work with no flaws.

  So, now, what i used to say "you cant pick a newly created object before the next root event" makes no sense anymore. It does not include 'situation 2' in openings post in a non brain wrecking way.

  So what i need is a rephrase of "you cant pick a newly created object before the next root event" so it includes both situations.

• • 99Instances2Go
  • 
  • • Joined 12 Feb, 2016
    • 
    • 8 topics • 2,454 posts
  • 1

  • 20 Jun, 2017
  • Quote

  So each 'level' (parent-sub-sub-sub ....) has its personal 'level' picklist ?

• • 99Instances2Go
  • 
  • • Joined 12 Feb, 2016
    • 
    • 8 topics • 2,454 posts
  • 1

  • 20 Jun, 2017
  • Quote

  AllanR

  I know all that. If you ever read my comments, you know i do.

  It should not matter that it stays 'picked' as you call it. Or, that it stays in the current picklist.

  Because it is 'repicked', and that condition should not work.

  As you word it "If ... pick All Sprite2, (then all other existing instances will be picked except the new one - because it does not officially exist yet)."

• • 99Instances2Go
  • 
  • • Joined 12 Feb, 2016
    • 
    • 8 topics • 2,454 posts
  • 1

  • 20 Jun, 2017
  • Quote

  Schrodinger's Sprite.

  It both exists, and does not exist inside of the box/event/tick.

  Keep in mind, objects created are picked, until the next higher tier event.

  Yeah, but you cant peek in the box until the next root. Unless you entangle it with UID.

  Yet, that is what happens in the second version.

• • 99Instances2Go
  • 
  • • Joined 12 Feb, 2016
    • 
    • 8 topics • 2,454 posts
  • 1

  • 19 Jun, 2017
  • Quote

  Situation 1. This is obvious not working. I do not need an explanation about this one:

  https://www.dropbox.com/s/yz3ux9s33mne4 ... .capx?dl=0

  Situation 2. This is working:

  https://www.dropbox.com/s/h5s4xq6q5hk5o ... .capx?dl=0

  I feel like it should not. So why is it working ? Because this creates possibilities and opens a world of new options. But why ? And can i trust that it will work after the next update ?

• • 99Instances2Go
  • 
  • • Joined 12 Feb, 2016
    • 
    • 8 topics • 2,454 posts
  • 2

  • 19 Jun, 2017
  • Quote

  Bring them into a family. Add an instance variable representing Y.

  + (no conditions)

  -> family: Set Y_Order to Self.?Y

  -> System: Sort family Z order by Y_Order

  And its done. Think they need to be on the same layer.

  Additional, if the player is the only moving thing, start with (player) Is overlapping (Family), update for family and player (player is not in the family picklist). Now you can execute this 1000 times in one tick, dont matter.