Conversation
… when I want to make level out of a lot of block/lava in sequence, basically it treats the whole pool as 1 object to check collision, instead of looking at 20 lava blocks separatly, marginal although in my testing noticable improvement in performance
…ump from a block, had to make a generous buffer so it doesnt do that
…ialy over a minute, tested how much i could, Im pretty sure there is unintended path under the stair up, but it is more difficult than following the intended path so Im okay with it, could make #define NUM_STAIR_STEPS 12 be up to 30, and i < 7 on line 120 up to 30 as well if you just want to make it longer, dont forget to change value on line 175
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.