Change:
You should have a boolean expression that checks if the player's `y` position plus the player's height is greater than or equal to the platform's `y` position. ```js <del> assert.match(code, /consts+platformDetectionRuless*=s*[s*player.position.xs*>=s*platform.position.xs*-s*player.widths*/s*2s*,s*player.position.xs*<=s*platform.position.xs*+s*platform.widths*-s*player.widths*/s*3s*,s*player.position.ys*+s*player.heights*>=s*platform.position.ys*,s*.*s*]s*;?/) </del> <ins> assert.match(code, /consts+platformDetectionRuless*=s*[s*player.position.xs*>=s*platform.position.xs*-s*player.widths*/s*2s*,s*player.position.xs*<=s*platform.position.xs*+s*platform.widths*-s*player.widths*/s*3s*,s*(?:player.position.ys*+s*player.height|player.heights*+s*player.position.y)s*>=s*platform.position.ys*,s*.*s*]s*;?/) </ins> ``` You should have a boolean expression that checks if the player's `y` position is less than or equal to the sum of the platform's `y` position plus the platform's height. ```js <del> assert.match(code, /consts+platformDetectionRuless*=s*[s*player.position.xs*>=s*platform.position.xs*-s*player.widths*/s*2s*,s*player.position.xs*<=s*platform.position.xs*+s*platform.widths*-s*player.widths*/s*3s*,s*player.position.ys*+s*player.heights*>=s*platform.position.ys*,s*player.position.ys*<=s*platform.position.ys*+s*platform.heights*,?s*]s*;?/) </del> <ins> assert.match(code, /consts+platformDetectionRuless*=s*[s*player.position.xs*>=s*platform.position.xs*-s*player.widths*/s*2s*,s*player.position.xs*<=s*platform.position.xs*+s*platform.widths*-s*player.widths*/s*3s*,s*(?:player.position.ys*+s*player.height|player.heights*+s*player.position.y)s*>=s*platform.position.ys*,s*(?:player.position.ys*<=s*platform.position.ys*+s*platform.height|player.position.ys*<=s*platform.heights*+s*platform.position.y)s*,?s*]s*;?/) </ins> ```

Discussion:
There is an error in the code provided in Step 90 regarding the collision detection logic for platforms. The problem is: The fourth condition contains a syntax error (the unnecessary before ) and will not correctly evaluate the player's vertical position relative to the platform. Recommendation: Please update the course materials to reflect the correct condition in the collision detection logic. Thank you! ! ! Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] No response
Hey can u assign this issue to me!
Hello there This is the starting (seed) code: The third and fourth conditions are by YOU. So, if there is an unnecessary , only you can remove it. Also, your issue description and screenshot do not match. So, I am unsure what problem you are referring to. As such, I am going to close this issue. If you can explain where the problem in the content is, then we will reopen this issue. Thank you.
Hi , The test seems to fail because the expected order isn't being followed, even though both are equivalent. 1+2 = 3 2+1 != 3 ?
Ah. Ok, I understand what you mean now. Thank you for explaining further. The current tests are too strict with the expected input: The solution should probably be to test the value of with mocked data.
Opening for contribution, the test should be updated to at least accept both orders Optional the part of testing with mocked data instead of regex, but it would make the test more robust for sure