Privacy Issue
Assigned
Reported
Comments
It's sad that he still hasn't posted his full launcher_log.txt because it may or may not have been resolved in the new launcher bootstrap (601) build which was released on October 15th (i've posted information under ticket 12229).
I can hereby confirm that the issue has been resolved in the updated Bootstrap code (601) of the Launcher build/version that was released/signed on October 15th.
PROOF:
Makes sense. Thanks for the explanation 🙂
How can this be labeled as Resolved when the Installer gives the user the choice to install the launcher/game to a different drive? This is more considered a workaround than an actual fix.
In previous launcher builds/versions there were no problems when choosing a destination other than the system/boot drive.
What does your launcher_log.txt under %APPDATA%\.minecraft\ say?
My launcher log said the following:
"Update failed for: LICENSE, Error: The system cannot move the file to a different disk drive."
workaround: Since my Minecraft launcher was installed on drive "D", i could work around the problem by moving my Minecraft installation (the folder where Minecraft(Launcher).exe is located) to my System drive "C" (in my case). The launcher then proceeded the update process without problems.
I think the problem is related to the (updated) Launcher Bootstrap,
because previously my launcher could always update without problems.
But on the other hand, it's PistonUpdate.cpp(403) that throws the error.
Hopefully a fix will be issued soon.
Also present in the 14w17a snapshot
@ [Mod] Jar_: done 😉 (also added a video with proof)
(still) present in 1.7.9 / 14w11b
https://www.youtube.com/watch?v=7ukqYNcIQlM
Why have our comments been removed and has the status been set to resolved, while the issue hasn't been fixed in the original bug report? (i tested it a few minutes ago after [Mod] Jar_ posted his comment).
When the coordinate is set, it is within a block- namely the pressure plate or tripwire string. This is probably why the spawnpoint command fails. If the player's hitbox brushes the edge of the pressure plate or string, there's a higher chance setting spawnpoint will work.
I would like to see this fixed =/ (still present in 1.7.4)
@ Jeremy: I wholeheartedly agree with you
Thanks for patching this 🙂
Also in 13w49a / 1.7.3 Pre-release
Updated: 13w49a client/server are also affected
/setworldspawn isn't ment/intended to do that.
To achieve the thing you want, you should use the /tp command (and optionally /spawnpoint playername x y z) in conjunction with commandblocks and /scoreboard 's score features.
You can then further customize its behaviour (i.e. make a firsttime spawn location or add different spawn locations for different teams)
Also watch the below tutorials from Dragnoz. These have helped me when i was facing the same problem:
Uploaded video http://youtu.be/1tkWyaSp_Js
Sorry: yes.
edit: This applies for Mojang's own server jar and Minecraft's built-in (LAN) server
Also in 13w48b ...
I didn't confirm anything, i simply hope it gets fixed before 1.8.x
I can hereby confirm that the issue has been resolved (atleast in my case), in the updated Bootstrap code (601) of the Launcher build/version that was released/signed on October 15th.
PROOF: