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 maxViewportY to the correct value #652

Merged
merged 1 commit into from Dec 1, 2022
Merged

Fix maxViewportY to the correct value #652

merged 1 commit into from Dec 1, 2022

Conversation

dudantas
Copy link
Contributor

@dudantas dudantas commented Nov 30, 2022

Description

Complement of the pr #640
Commit: 785f26f
Some monsters didn't attack in certain scenario

Behaviour

Actual

Some monsters didn't attack in certain scenario

Expected

All monsters attacking player

Type of change

  • Bug fix (non-breaking change which fixes an issue)

@sonarcloud
Copy link

sonarcloud bot commented Nov 30, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@dudantas dudantas merged commit 9e4b9ec into main Dec 1, 2022
@dudantas dudantas deleted the fix-maxViewportY branch December 1, 2022 18:43
luan pushed a commit that referenced this pull request Jul 11, 2023
Complement of the pr: #640
Commit: 2c4fefe
Some monsters didn't attack in certain scenario
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants