Put the summary of the bug you're having here
What I expected to happen was...:
Describe what you thought should happen here
What actually happened was...:
Describe what happened here
Steps to Reproduce:
1. Put a step by step guide on how to trigger the bug here
2. ...
3. ...
Minecraft Crash Report ----
// Why is it breaking 😞
Time: 2/20/14 4:00 PM
Description: Rendering screen
java.lang.IllegalArgumentException: bad Base64 input character at 2810: 64 (decimal)
at io.netty.handler.codec.base64.Base64.decode(Base64.java:247)
at io.netty.handler.codec.base64.Base64.decode(Base64.java:197)
at io.netty.handler.codec.base64.Base64.decode(Base64.java:188)
at bge.b(SourceFile:155)
at bge.a(SourceFile:130)
at bat.a(SourceFile:26)
at bay.b(SourceFile:382)
at bay.a(SourceFile:259)
at bgb.a(SourceFile:283)
at bll.b(SourceFile:851)
at azd.ad(SourceFile:780)
at azd.e(SourceFile:704)
at net.minecraft.client.main.Main.main(SourceFile:103)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
– Head –
Stacktrace:
at io.netty.handler.codec.base64.Base64.decode(Base64.java:247)
at io.netty.handler.codec.base64.Base64.decode(Base64.java:197)
at io.netty.handler.codec.base64.Base64.decode(Base64.java:188)
at bge.b(SourceFile:155)
at bge.a(SourceFile:130)
at bat.a(SourceFile:26)
at bay.b(SourceFile:382)
at bay.a(SourceFile:259)
at bgb.a(SourceFile:283)
– Screen render details –
Details:
Screen name: bgb
Mouse location: Scaled: (239, 143). Absolute: (478, 193)
Screen size: Scaled: (427, 240). Absolute: (854, 480). Scale factor of 2
Stacktrace:
at bll.b(SourceFile:851)
at azd.ad(SourceFile:780)
at azd.e(SourceFile:704)
at net.minecraft.client.main.Main.main(SourceFile:103)
– System Details –
Details:
Minecraft Version: 1.7.2
Operating System: Windows 7 (x86) version 6.1
Java Version: 1.7.0_45, Oracle Corporation
Java VM Version: Java HotSpot(TM) Client VM (mixed mode, sharing), Oracle Corporation
Memory: 22451016 bytes (21 MB) / 77987840 bytes (74 MB) up to 518979584 bytes (494 MB)
JVM Flags: 2 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx512M
AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
Launched Version: 1.7.2
LWJGL: 2.9.0
OpenGL: ATI Radeon 3100 Graphics GL version 2.1.8787, ATI Technologies Inc.
Is Modded: Probably not. Jar signature remains and client brand is untouched.
Type: Client (map_client.txt)
Resource Packs: [_Vibrant.zip]
Current Language: English (US)
Profiler Position: N/A (disabled)
Vec3 Pool Size: ~ERROR~ NullPointerException: null
Anisotropic Filtering: On (16)
Linked issues
Comments 10
Why do you think that your ticket is not a duplicate of MC-38385 ?
Im sorry, I guess I need to know the jargon. What I meant to say is that my issue hasn't been resolved so my 2nd and 3rd request shouldn't be looked at as a new one.
"Resolved as duplicate" in the sense of this bug tracker means, that this ticket was merged with MC-38385, because the same issue was reported earlier.
The ticket MC-38385 is still unresolved or open, because the devs didn't fix that problem, thus your issue isn't resolved too.
Keep in mind that this site is not a help forum (focus on helping users), it's a bug tracker (focused on organizing bugs)
Ok and thank you for taking the time out to explain. Im not computer savvy but my son love's minecraft. Who would I contact to help us fix our issue? Please tell me that you have the answer. Lol
Now one of the developers of Mojang is in charge, but I'm afraid contacting them won't speed up anything.
So I just have to sit, wait and keep trying until it works? Or do you have any other suggestions? Btw, I know that you may be very busy but thanks again for being so patient.
You may vote for MC-38385 (this ticket has 0 votes at the moment...) and watch that ticket, then you'll get an email if something happens there.
This issue has not been resolved. I am still having the same problem. This not a duplicate issue.