Construct 3 suggestions & ideas

Suggest and vote on ideas for Construct 3! Please note this is only one aspect of planning. We do not guarantee any features here will be implemented, even if they are top-voted ideas. The aim is just to collect feedback. Remember to search for existing submissions before adding an idea, describe your ideas as comprehensively as possible, and vote for plausible ideas that are well thought out. Please see our full guidelines on suggesting features.

83 VOTE

Ignore Selected Solids

In Construct Classic the platform behavior has ignore list actions that you can use to select which solids you want to have collisions with and which solids to ignore collisions with, but this feature is not in Construct 2 or 3.

I'm suggesting this feature should be added for all movements. (platform, bullet, car, 8 direction) and for all objects with collisions.

To clarify, I'm talking about the feature used in this example for a staircase that the player can walk on, but enemies can't walk on:

(requires construct classic to open)

Link: https://www.dropbox.com/s/qsni3wea4nj8dla/steps%20in%20construct%20classic.cap?dl=0

and used in this screenshot:

Link: https://www.dropbox.com/s/qk4n8mhrniwvnvy/ignore%20list%20in%20construct%20classic%20pic.png?dl=0

  • Jackie Chan
  • Apr 5 2017
  • Shipped
  • Oct 29, 2018

    Admin Response

    A feature for filtering collisions with solids using tags shipped in r123.

  • Attach files
  • Alex HW commented
    April 05, 2017 17:40

    This should be implemented for all objects with collisions, not just for behaviors.

  • Jackie Chan commented
    April 05, 2017 17:43
     @Alex HW
    Agreed.
  • Jackie Chan commented
    April 05, 2017 17:45

    @Alex HW

    I just updated the suggestion to reflect this.

  • Alex HW commented
    April 05, 2017 18:53

    thanks, you have my vote!

  • Pixel Metal commented
    April 05, 2017 23:00

    Rather than ignoring selected solids, maybe being able to define tags on an object that you WANT to collide with, and checking for those tags, would be more powerful?

  • Animmaniac commented
    April 05, 2017 23:52

     Perhaps add a "Collision Tag" property to the Solid behavior, and for each movement behavior add a dropdown property "Solid Collision" with the options "None, All, Inclusive, Exclusive", and below another property "Collision Tags" that accept a comma separated list of tags. "None" and "All" ignore any listed tags and just set enable/disable collision with solids, and "Inclusive" or "Exclusive" use the list of tags to filter collisions in a "none + listed" or "all - listed" way.

  • Pixel Metal commented
    April 06, 2017 01:04

    Sounds good to me!

  • Everade commented
    April 06, 2017 19:45

    We should have full control over collisions with solids.
    I'm still having the issue within online multiplayer environments that i can not let specific sprites (players) colide with specific solids while other sprites (players) shouldn't.

     

    Really looking forward to this.

  • Daniel Scofano commented
    May 18, 2017 21:42

    Animmaniac's idea seems to be the best one.

  • Jackie Chan commented
    May 25, 2017 23:32

    I suggested collision tags here: https://construct3.ideas.aha.io/ideas/C3-I-203

  • Admin
    Ashley Gullen commented
    October 26, 2018 12:39

    Filtering collisions by tag seems to be a more powerful mechanism that also covers this - instead of setting an object to ignore collisions with an object, you could give the object's solid behaviors a tag and set the object to filter collisions by excluding that tag. Then you also get further options for filtering per-instance using tags in other ways. So I think the tags system covers both this and the separate collision tags suggestion.

  • Tacker Tacker commented
    October 28, 2018 09:25

    Yeah in development :D

    Just want to add that it is important that we have control over collision on runtime, and on a per object basis. It can't be just something you setup once in the editor and it can't be something that you switch for all instances at once.
    I attached an image with an example that shows why that's important.
    The player should be able to go through or up the ramp, same for the enemies.
    If there are 2 enemies, 1 should be able to go up and 1 through the ramp at the same time.