Please press F3+C for 10 seconds, and upload the generated crash log.
Has anyone tried updating LWJGL?
I don't confirm on 1.5.2.
Also I didn't read the walls of text.
Can you attach a copy of the save?
find -L ~ | grep -i 'minecraft.*crash.*client\.txt$' | xargs cat > ~/minecraft-crashes.txt
Apparently Apple's find(1) command requires a path to work...which is stupid, since the GNU/Linux version I am familiar with doesn't.
Though I am about to give up on the issue. Nothing wrong on your system if the server is indeed modded; in which case, you would try a different server. In fact, try that; see if you can connect to a different multiplayer server.
Confirmed 1.5.2-PRE.
Old scale is intended behaviour if you didn't activate the map ๐
@Anon Ymus
The .tiff files claim the client is unmodded. Have you confirmed the server is modded? I'm treating the current issues with testing as a keyboard-chair interface malfunction. Either that or Apple messed something up, though one of my friends (who uses a Mac) confirms that my instructions (with minimal alterations) work.
@Luci
How exactly are you starting Minecraft?
From a terminal, please execute the following command:
cd ~ ; find -L | grep -i 'minecraft.*crash.*client\.txt$' | xargs cat > ~/minecraft-crashes.txt
and upload the file 'minecraft-crashes.txt', located in your home directory, to this ticket.
The first page of the error report claims that it did save the logs, though.
Please press โงโG, and paste in:
/Users/lucibedwell-lee/Library/Application Support/minecraft/crash-reports
and attach the file "crash-2013-04-28_17.18.51-client.txt" to the ticket.
Enviorment:
Minecraft 1.5.1
Mac OSX x86_64 10.7.5
Java 1.6.0_41 (Apple-supplied)
Are you actually using a tripwire hook? Both ends of the string need to lead to one, and the string needs to be straight, and not too long.
How far away is everyone from the components that are turning on?
Chances are that any of the following are true:
It is not a stability error
It is caused by doing direct editing of maps
There is a simple workaround, which is good practice to do anyway (resetting the text mode)
There are no votes for the issue, so Mojang doesn't know about the issue
It would also help to, if Java being outdated isn't the cause, crash the game by pressing F3+C for 10 seconds, and attaching the crash log, so we have a better idea about your hardware.
If it crashed, please upload the crash logs, otherwise the ticket is incomplete.
???
How do you click on two things at the same time?
What mods do you have installed?
Have you actually confirmed that the issue exists with all the versions you wrote down?
@Torabi:
Given that he has a wireless signal right now, I'd assume he is signed in.
Can you describe step-by-step how to reproduce the issue?
Can you press Shift+F3 and show us the pie?
I assume you do not have a subscription. This bug will be invalid in that case.
The following is UNCONFIRMED, and merely speculation on my part:
If you somehow get into the config without any active Realm (Realms require a subscription), then when you request for the world to be reset, the client doesn't know what to tell the Mojang servers (the Realms are NOT locally located), and crashes.
The option is probably not there because you do not have an active subscription.
(I've been messing around with Tekkit, sorry for the delay)
(No, not modded MC for this issue)
I do not entirely understand what you are saying. The rockets all are practically identical; and become perfectly identical when the game is saved.
I can also confirm that I get a similar bug in Tekkit Lite, running MC 1.4.7, so the bug has been around since then at least; however it is with the mod-added redstone batteries rather than the fireworks. However, I believe that the core reason is identical. I will try testing the issue in a vanilla 1.4.7 at some point; if the issue still holds, we will know that the cause is not related to the Redstone Update.