You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've made a few changes to the way I work with the y-level on levels from 2 and above.
Previously, it worked a bit like:
treat everything like if we're on y=0, but both {LEVEL_NAME}.draw() and detect_collision() (and related functions) have to make adjustments to work as expected
Honestly, making this has become a little tricky, so I adopted a new focus:
Notify the Player and mob classes which is the top y value on this level (and then, the bottom value is y + 120 instead of just 120), and act normally ignoring that y != 0.
First pointed in #3, this is a critical issue that must be addressed as soon as possible.
The text was updated successfully, but these errors were encountered: