Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Godot 4 TileSet one-way collision is not one-way only #64362

Open
svprdga opened this issue Aug 13, 2022 · 4 comments
Open

Godot 4 TileSet one-way collision is not one-way only #64362

svprdga opened this issue Aug 13, 2022 · 4 comments

Comments

@svprdga
Copy link

svprdga commented Aug 13, 2022

Godot version

v4.0.alpha.14.official

System information

Linux Mint, Vulkan

Issue description

When setting the collisions of a tile in a TileSet as one-way, the engine does not apply it correctly. Normally, a character should be able to jump to a higher platform from below "through" it, but any other type of collision should be detected and the engine should prevent the character from going through the obstacle.

In the code example that I attach you can see how the character can cross the area on his right. In this case, the character should hit that raised area and be stopped.

Steps to reproduce

  1. Create a Godot 4 project
  2. Create a map with a TileMap, and use a Tile with the one-way collision enabled
  3. Add a CharacterBody2D node as the player, set its movement and collisions
  4. Try to hit a tile from the side

Minimal reproduction project

https://github.com/svprdga/Godot-4-One-way-collision-error

@KoBeWi
Copy link
Member

KoBeWi commented Aug 13, 2022

This is not a bug. One way collision, as name implies, works only one way - from top. All other directions aren't detected; that's consistent with literally every platformer.

@Calinou Calinou added documentation and removed bug labels Aug 13, 2022
@Calinou
Copy link
Member

Calinou commented Aug 13, 2022

This is not a bug. One way collision, as name implies, works only one way - from top. All other directions aren't detected; that's consistent with literally every platformer.

I suppose documentation should be modified to make this more explicit.

@KoBeWi
Copy link
Member

KoBeWi commented Aug 13, 2022

idk, I think the OP just confused it with "one way passage".

@svprdga
Copy link
Author

svprdga commented Aug 14, 2022

This is not a bug. One way collision, as name implies, works only one way - from top. All other directions aren't detected; that's consistent with literally every platformer.

Right, I was confused about that. Thanks for the clarification.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

3 participants