Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix #443 - Fix for default duty not working if set to false #450

Merged
merged 1 commit into from
Apr 20, 2024

Conversation

Scullyy
Copy link
Contributor

@Scullyy Scullyy commented Apr 20, 2024

Description

Fix for default duty not working if set to false

Checklist

  • I have personally loaded this code into an updated Qbox project and checked all of its functionality.
  • My pull request fits the contribution guidelines & code conventions.

Copy link
Member

@Manason Manason left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This logic looks the same, what am I missing?

@Scullyy
Copy link
Contributor Author

Scullyy commented Apr 20, 2024

This logic looks the same, what am I missing?

in the current logic if job.defaultDuty was set to false then it would move onto playerData.job?.onduty, I tested this with prints and found that these changes resolved it.

@Scullyy Scullyy requested a review from Manason April 20, 2024 03:24
@Manason Manason merged commit 73f52fb into Qbox-project:main Apr 20, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants