You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The majority of the screen is filled with a yellow-tinted screen, such as the area selection map in this screenshot. That's not supposed to happen, and it makes viewing harder. Those borders on the edge are unaffected, though.
Additionally, when a turret in-game stops detecting an enemy in range, it still continuously does the attacking animation, and when a new enemy is in range, the turret is still stuck like that, making it useless for the rest of the game.
Expected behavior
The game didn't even have a yellow-tinted screen at the center, it was just clear.
When a turret doesn't detect an enemy anymore, it's supposed to stop and then attack again whenever a new enemy is in range.
Affected platform
Desktop app
Operating system
Windows 10
Browser
Google Chrome Version 108.0.5359.125
Additional information
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
This link is one of the sites that hosts the Frontline Defense: First Assault.
The majority of the screen is filled with a yellow-tinted screen, such as the area selection map in this screenshot. That's not supposed to happen, and it makes viewing harder. Those borders on the edge are unaffected, though.
Additionally, when a turret in-game stops detecting an enemy in range, it still continuously does the attacking animation, and when a new enemy is in range, the turret is still stuck like that, making it useless for the rest of the game.
Expected behavior
The game didn't even have a yellow-tinted screen at the center, it was just clear.
When a turret doesn't detect an enemy anymore, it's supposed to stop and then attack again whenever a new enemy is in range.
Affected platform
Desktop app
Operating system
Windows 10
Browser
Google Chrome Version 108.0.5359.125
Additional information
No response
The text was updated successfully, but these errors were encountered: