Tile collision direction flags about phaser-arcade-slopes HOT 6 CLOSED

Awesome, I'm glad it's helpful for you.

Actually, the plugin doesn't properly support this yet and probably should in some way.

I'll add this to the roadmap for v0.2.0. It's a compatibility feature I initially left out because the meaning of these directions changes a little once you introduce 45 degree angles. I'm sure I can work something out though, and this will be useful in my own games too.

from phaser-arcade-slopes.

Hopefully I'm right in thinking that all it will take is changing these lines:

https://github.com/hexus/phaser-arcade-slopes/blob/v0.2.0-alpha2/src/ArcadeSlopes/SatSolver.js#L611-L626

For example, this part of a condition:

tile.slope.edges.top === Phaser.Plugin.ArcadeSlopes.TileSlope.EMPTY && ...

becomes:

(!tile.collideUp || tile.slope.edges.top === Phaser.Plugin.ArcadeSlopes.TileSlope.EMPTY) && ...

The same would need to be done for bottom, left, right, etc.

I'd probably do this more formally for the actual implementation.

from phaser-arcade-slopes.

Are there any work-arounds I can try in the meantime? I wouldn't mind hacking around your plugin a little, but I'm still not sure how to go about one way collisions with it.

from phaser-arcade-slopes.

@hexus
Just confirmed that what you suggested works for me! Thank you for your help!

from phaser-arcade-slopes.

Awesome.

Your Mario project looks cool too, I'm glad the plugin helps you to build it.

from phaser-arcade-slopes.

Fixed above. Thanks for bringing this up. 👍

from phaser-arcade-slopes.