Resolve traverser stone bug #9893#10195
Open
lefneer311 wants to merge 1 commit into
Open
Conversation
- Updates traverser_start default value to null from 0 - Addresses bug LandSandBoat#9893
39f8831 to
896bbf6
Compare
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
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.
I affirm:
What does this pull request do?
Traverser stone calculation is currently bugged due to the default value of this table being 0 rather than null.
Converts default values to null, which allows timestamps to be properly written when the necessary in-game event is triggered.
Resolves #9893
Steps to test these changes
Satisfy requirements to enter Abyssea zones. Check database table char_unlocks for traverser_start value. It should be a properly formed timestamp rather than 0.