This is a bug that at some point was unfixed/rebroken and is now in the latest versions of both the website launcher and the MS store launcher
This occurs with both currently updated versions of the launcher (from the website and from the MS store).
Everything is up-to-date.
PS: I've updated the description to be more accurate to the current bug.
PPS: I'm not considering it a bug that when you snap the window to the left edge of the left monitor that when you relaunch, it's not snapped to the left edge; it's on the left side where you would expect it, but only with the left monitor.
PPPS: I've tested with other programs and they open as expected: in the same spot you closed them, even if straddling across two monitors.
In the current version of the launcher (and for some unknown amount of time since this issue was previously fixed), the order of the games listed is no longer listed alphabetically in the Play screen (only the Installations). As this was properly fixed previously, and is once again broken, I'm assuming this is not as intended.
Let me emphasize: this was previously fixed to work with the list sorted alphabetically in the Play menu AND Installations menu, with the option appearing in the Installations menu
This comment is to elaborate on the issue from my POV, but is not critical for the description of the issue.
This severely impacts my base area as I now have to re-outline the area, dig up some grass and place others, and hope and pray that it doesn't overlap with any existing builds I've done. Rolling back is not a viable option as this is a server and this issue isn't game-breaking. It's just an extreme annoyance/inconvenience and raises a HUGE concern that something like this may happen again in the future.
This bug appears to be fixed with the latest launcher release
Bug is 95% fixed. Game Output Log closed on monitor 3, appears on primary monitor next launch, if too close (within apx 10 pixels of) to edge of monitor (including snapped to side). DOES keep custom size now.
My setup: monitor 1 on left, launcher loads here; monitor 2 in middle, set as primary, game launches here; monitor 3 on right, game output meant to load here.
I realize this is likely a very niche case, but it is technically still a bug. Will edit bug for clarity and include screenshot of my setup and the result from game launch as well
Thank you for splitting into two bug reports (wasn't 100% sure if it was the same bug or two different ones)
Changes for clarity I'd recommend:
Title, "bug" & Step 5 - "game output log window"
I would, please, for being the reporter.
I would probably say "Game Output Log window" in the bug section to avoid confusion with the game window itself?*
By previous versions, I mean previous launcher versions with both the old and new launcher. I think the previous version of 2.1.932x it worked (I got the version history off the wikipedia). It definitely did work within the last month.
*edit - I realized I can edit this one, so I made the change
This is also an issue on Java Realms
Next time this happens, I’ll check the log files before logging in
Want to note that kruthers is incorrect (tested on Realms) - spawn chunks and player loaded chunks do not render when in spectator with gamerule spectatorsgeneratechunks false
also, update - still an issue in 1.14.1 prerelease 2
you kind of answered your own bug report here: 6 weeks before the reported version of this report, phantoms no longer spawn in the end
slightly off topic of this bug report:
Main reason I'm bringing anything up is: how do you artificially change how long it's been since you slept. I'm testing to see if Phantom spawning is broken in 1.14 or if I've just been unlucky.
I remember reading about that being fixed (the insane high health not being intended)
That said, I agree the heath is too low for new underwater and should, imho, be increased to the same as a player (since you can’t equip armor on skeleton horses). For this, I recommend posting a feature request where appropriate.
I get this problem too. It started happening about 1-2 weeks ago when the launcher downloaded new files for itself or something? Closing any* instance of the game crashes the launcher (I have a camera account I may only need briefly, so I launch a seperate profile set up to not interfere with the main profile and I close that one sooner because it's no longer needed and the launcher crashes (but the other game window does NOT crash)).
(Partial) debug crash menu: An unhandled win32 exception occurred in Minecraft_staging.exe [76132].
(the rest of that error just says I don't have anything that can debug it)
My PC specs:
Windows 10 Home
Intel i5-3570K CPU
32 GB Ram
2TB HD (1.28TB free/1.99TB usable)
Nvidia GeForce GTX 750 Ti Graphics Card
*I can run 1 instance of the game or 2 and it crashes as soon as any instance is closed
snapshot 17w49b
video evidence: https://www.youtube.com/watch?v=7pbNNKgnrJ4
no crash report/log
No opaque blocks is implied by "The effects still apply"
Still present in 16w05b.
Easiest way to verify:
Run Minecraft, create new world (Creative), switch to Spectator mode
Run Amidst (v4 beta6), load newly created world, locate strongholds beyond ring 1 (get coords, 2 very close strongholds is best)
In Minecraft, tp to coords and look for strongholds (end portal room is best to locate as 1 per stronghold)
Note: while you may be able to load Amidst with the latest snapshot, for what I can tell, it currently can't recognize any snapshot past 16w02a, thus requiring visual verification.
edit: after looking through Amidst some more, it's not every ring, and it's not even the same rings every time; it varies per seed. Either way, adding a screenshot now.
I was looking for where someone already posted the strongholds not generating as intended. Still present in 16w02a. (edited to remove redundancy 😛)
The Moonlight map is one that DOES support UUID's.
The OTHER map I posted was from before to after.
Again, Moonlight map was downloaded and has UUID's and the 2nd bit was a similar issue I had had.
The first paragraph is my problem now. The second is another UUID problem I had had and posted because I figured there was something wrong with the UUID system having similar problems again.
Going to add that, rarely, the location and size fully resets and it opens in the top-left corner of the left most monitor to the default size