How to reproduce:
1. Set up two monitors
2. Open the “ScreenManagerWindowPositionBug.zip“ project
3. In the Build Profiles, build the project
4. Run the built Player
5. Set the Player to fullscreen and switch the Player to display on a different monitor (can be changed in the running Player)
6. Click anywhere on the other monitor for the Player to minimize itself
7. Close the Player through the Taskbar
8. Run the Player again
9. Observe the Player

Expected result: The Player opens on the same monitor it was before closing it
Actual result: The Player opens on the default monitor

Reproducible in: 2022.3.0f1, 2022.3.60f1, 6000.0.44f1, 6000.1.0b12, 6000.2.0a7

Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: macOS 15.3.2, No other environment tested

Notes:
- After changing the Player settings, the Player might need to be restarted
- When testing on three monitors, the Player by default opened and yielded the actual results on the third monitor and not the first, as expected
- As shown by the reporter, the “Screenmanager Window Position X“ (and Y) are set to, what looks like, an int underflow when the application gets unfocused
- In version 6000.0.44f1 and later, after the PlayerPrefs get corrupted, the window also returns to being windowed
- On Macs, when a fullscreen Player gets unfocused, the Player does not minimize, thus making the issue not reproducible there
- Could not test in most <2022.3.0f1 versions, as the project just did not open