Phaser 3 is currently using Matter.js v0.13.1, which is roughly a year old. The latest release is 0.14.2, which was released in June of this year. Is there any reason not to update this in Phaser?
goldfire
All 7 comments
I'd like to see it updated too. I'd also prefer Matter to be brought in via NPM, and simply aliased to the Phaser namespace.
hexus
on 17 Aug 2018
Yes, I definitely agree with the point about npm. I'm still not sure why it was done that way considering there are some other external libraries in the package.json.
goldfire
on 17 Aug 2018
Because we include a load of optimization fixes that the current Matter version has not merged yet.
I'll see about merging the changes from 0.13.1 to 0.14.2 in, but I'm sure we've got most of them covered already.
photonstorm
on 18 Aug 2018
@photonstorm Thanks for the clarification, I wasn't sure if that was the case or not.
goldfire
on 18 Aug 2018
may i know if the new matter.js integration will include Body.setParts() ?
vicksonzero
on 18 Aug 2018
just to clarify: including Body.setParts() means it will attach Phaser.Physics.Matter.Sprite to another Phaser.Physics.Matter.Sprite, making them move together
vicksonzero
on 18 Aug 2018
Matter has now been updated to 0.14.2.
photonstorm
on 22 Aug 2018
Related issues
samme
路
3Comments
SKEPDIMI
路
4Comments
MarkSky
路
3Comments
rootasjey
路
3Comments
halilcakar
路
4Comments
Most helpful comment
Matter has now been updated to 0.14.2.