Apply solid behavior on the character and not on the Tile ?

0 favourites
  • 8 posts
From the Asset Store
2D fighting template based in the game that defined the fighting games genre.
  • Hello,

    When I apply the solid behavior on the TileMap, my character doesn't fall to the infinity (doesn't pass through the TileMap).

    But I don't understand why the opposite doesn't work : when I apply the solid behavior on the character, and I delete it from the TileMap, my character pass through the TileMap:!:

    Any idea why ?

    Thanks for your answer!

  • The solid behavior is like a marker that tells other behaviors to respond to the object in a certain way. So your solid TileMap didn't do anything to the platformer character, it just told the character to act like there was a floor, wall, etc.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • calebbennetts I'm still not satisfied but however thank you!

  • Try to think about it without programming in mind from a logical standpoint...even if the character is solid, why would it interact with a non solid terrain? (Think that you could need a non solid tilemap for a decorative background, for example. You would not want your character interacting with supossedly distant stuff like background clouds or mountains)

  • Momio It's most understandable! thanks

  • As Momio said, solids of one object demands the behaviours of another object 'to here' and 'not further'. Those behaviours are :

    8 Direction, which is blocked by Solids (An object with 8 direction, another that is solid)

    Bullet, which can optionally bounce off Solids (An object as bullet, another that is solid)

    Car, which bounces off Solids (An object as car, another that is solid)

    Line-of-sight, which by default has line-of-sight obstructed by Solids (An object with LOS, another that is solid)

    Platform, which can land on Solids. (An object that is platform, another that is solid)

    Pathfinding, which by default uses solids as path obstacles. (An object with pathfinding, another that is solid)

    So, you have always a pair. Solid on one object, a behaviour on another object. You break that basic principle by not pairing a behavior in one object with a solid in another object.

    Besides that, a platform can got trough a solid with the Jump-thru behavior.

  • 99Instances2Go Thank you for your reply.

    I have posted this question because I have a big tilemap and I search to otimize the game.

  • I have no idea what you exactly want to do ? Someone will help, if its known whatcha try to do.

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)