Tile.tileset incorrectly holds an array

[jbpuryear]

Version

Phaser Version: 3.14.0

Description

Tile.tileset now incorrectly holds an array of tilesets instead of a tileset object. This breaks Tile.getCollisionGroup and Tile.getTileData.

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[jorbascrumps]

Tilemap layers now support multiple Tilesets as of 3.14. This is intentional. The real issue is getCollisionGroup and getTileData not supporting this new feature.

[jbpuryear]

Tilemaps have multiple tilesets, but shouldn't a tile only need to reference the tileset it's actually using?

If tiles are supposed to hold an array we should change the docs to reflect this. @Iamchristopher

[mgrubinger]

Any news on this issue?

I am trying to get collision to work with a Tilemap from Tiled.
myLayer.setCollisionFromCollisionGroup() works with Phaser v3.13, but I need Phaser v3.15+ because of other improvements (webgl performance on iOS). Any alternatives to setCollisionFromCollisionGroup() in v3.15+ ?

Thanks!

[photonstorm]

Thank you for submitting this issue. We have fixed this and the fix has been pushed to the master branch. It will be part of the next release. If you get time to build and test it for yourself we would appreciate that.

[Corey255A1]

Can confirm it is working. Just ran into the problem on 3.15.1 and after messing around with different Tiled versions and different Phaser versions, building from source was the only thing that I could do to get around this issue and actually see the collision boxes correctly using Matter physics

[marwan38]

Thank you for submitting this issue. We have fixed this and the fix has been pushed to the master branch. It will be part of the next release. If you get time to build and test it for yourself we would appreciate that.

Can confirm it is working. Just ran into the problem on 3.15.1 and after messing around with different Tiled versions and different Phaser versions, building from source was the only thing that I could do to get around this issue and actually see the collision boxes correctly using Matter physics

I can confirm it works too.
By the way, not sure if it's been mentioned already, some of the matter examples have the same problem.

[fant0m]

Is it fixed or not? Matter examples are not working
https://labs.phaser.io/edit.html?src=src%5Cgame%20objects%5Ctilemap%5Ccollision%5Cmatter%20platformer%20with%20wall%20jumping.js

[photonstorm]

As it says above, fixed in master, will be part of the next release. There hasn’t been a release yet.