This repository was archived by the owner on Jul 7, 2023. It is now read-only.
Fix Max-Relation bug #100
Merged
Fix Max-Relation bug #100
Conversation
This file contains 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
added 2 commits
February 17, 2019 11:29
|
Thanks for all the help. Ive been sick so I havent had time to work on extra projects like factions. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What type of PR is this? (Feature, Bug fix, Formatting etc.)
Bug Fix
Link to relevant issue number(s), if any:
#91
Explain your change(s):
an equal was missing in the if sentence of function "hasMaxRelationship"
Why did you make these change(s)?
cause otherwise people can abuse this bug to get an extra Relation
Is there anything we need to know for compatability? (variable names, placeholders etc.)
no, it's all fine