Liudvikas Milasius
- Liudvikam
- liudvikam
- Europe/Helsinki
- Yes
- No
If you convert a texture pack (In this case I used FaithfulVenom v2 32x) with the program on mojang.com into a resource pack, put it into the resourcepacks folder and try to switch to it, it lags for like 3 seconds and then it doesn't switch. Just stays on the default resource pack.
Sometimes, the text when you have either English (UK) or English (US) language on gets very buggy and barely readable. I was using a texture pack (FaithfulVenom v2 32x) and obviously, I did convert it. I don't think you have to do something particular to reproduce this bug.
Sometimes, the text when you have either English (UK) or English (US) language on gets very buggy and barely readable. I was using a texture pack (FaithfulVenom v2 32x) and obviously, I did convert it. I don't think you have to do something particular to reproduce this bug.
Sometimes, the text when you have either English (UK) or English (US) language on gets very buggy and barely readable. I was using a texture pack (FaithfulVenom v2 32x) and obviously, I did convert it. I don't think you have to do something particular to reproduce this bug. The console did not say anything special. The only Java exception I saw was:
Client> java.io.IOException: Stream Closed
Client> at java.io.RandomAccessFile.seek(Native Method)
Client> at adu.a(SourceFile:308)
Client> at adu.a(SourceFile:251)
Client> at adv.close(SourceFile:232)
Client> at java.util.zip.DeflaterOutputStream.close(Unknown Source)
Client> at java.io.FilterOutputStream.close(Unknown Source)
Client> at adx.a(SourceFile:140)
Client> at adx.c(SourceFile:128)
Client> at amj.b(SourceFile:30)
Client> at amj.run(SourceFile:23)
Client> at java.lang.Thread.run(Unknown Source)
I do not think this exception has anything to do with the buggy text. I happens every time I run the snapshots, I think.
Sometimes, the text when you have either English (UK) or English (US) language on gets very buggy and barely readable. I was using a texture pack (FaithfulVenom v2 32x) and obviously, I did convert it. I don't think you have to do something particular to reproduce this bug. The console did not say anything special. The only Java exception I saw was:
Client> java.io.IOException: Stream Closed
Client> at java.io.RandomAccessFile.seek(Native Method)
Client> at adu.a(SourceFile:308)
Client> at adu.a(SourceFile:251)
Client> at adv.close(SourceFile:232)
Client> at java.util.zip.DeflaterOutputStream.close(Unknown Source)
Client> at java.io.FilterOutputStream.close(Unknown Source)
Client> at adx.a(SourceFile:140)
Client> at adx.c(SourceFile:128)
Client> at amj.b(SourceFile:30)
Client> at amj.run(SourceFile:23)
Client> at java.lang.Thread.run(Unknown Source)
I do not think this exception has anything to do with the buggy text. It (the exception) happens every time I run the snapshots, I think.
Text getting very buggy
Sometimes, the text when you have
either English (UK) or English (US) languageon gets very buggy and barely readable. I was using a texture pack (FaithfulVenom v2 32x) and obviously, I did convert it. I don't think you have to do something particular to reproduce this bug. The console did not say anything special. The only Java exception I saw was:
Client> java.io.IOException: Stream Closed
Client> at java.io.RandomAccessFile.seek(Native Method)
Client> at adu.a(SourceFile:308)
Client> at adu.a(SourceFile:251)
Client> at adv.close(SourceFile:232)
Client> at java.util.zip.DeflaterOutputStream.close(Unknown Source)
Client> at java.io.FilterOutputStream.close(Unknown Source)
Client> at adx.a(SourceFile:140)
Client> at adx.c(SourceFile:128)
Client> at amj.b(SourceFile:30)
Client> at amj.run(SourceFile:23)
Client> at java.lang.Thread.run(Unknown Source)
I do not think this exception has anything to do with the buggy text. It (the exception) happens every time I run the snapshots, I think.Sometimes, the text when you have any language that has the bigger letters on gets very buggy and barely readable. I was using a texture pack (FaithfulVenom v2 32x) and obviously, I did convert it. I don't think you have to do something particular to reproduce this bug. The console did not say anything special. The only Java exception I saw was:
Client> java.io.IOException: Stream Closed
Client> at java.io.RandomAccessFile.seek(Native Method)
Client> at adu.a(SourceFile:308)
Client> at adu.a(SourceFile:251)
Client> at adv.close(SourceFile:232)
Client> at java.util.zip.DeflaterOutputStream.close(Unknown Source)
Client> at java.io.FilterOutputStream.close(Unknown Source)
Client> at adx.a(SourceFile:140)
Client> at adx.c(SourceFile:128)
Client> at amj.b(SourceFile:30)
Client> at amj.run(SourceFile:23)
Client> at java.lang.Thread.run(Unknown Source)
I do not think this exception has anything to do with the buggy text. It (the exception) happens every time I run the snapshots, I think.
Sometimes, the text when you have any language that has the bigger letters on gets very buggy and barely readable.
I was using a texture pack (FaithfulVenom v2 32x) and obviously, I did convert it. I don't think you have to do something particular to reproduce this bug. The console did not say anything special. The only Java exception I saw was:
Client> java.io.IOException: Stream Closed
Client> at java.io.RandomAccessFile.seek(Native Method)
Client> at adu.a(SourceFile:308)
Client> at adu.a(SourceFile:251)
Client> at adv.close(SourceFile:232)
Client> at java.util.zip.DeflaterOutputStream.close(Unknown Source)
Client> at java.io.FilterOutputStream.close(Unknown Source)
Client> at adx.a(SourceFile:140)
Client> at adx.c(SourceFile:128)
Client> at amj.b(SourceFile:30)
Client> at amj.run(SourceFile:23)
Client> at java.lang.Thread.run(Unknown Source)
I do not think this exception has anything to do with the buggy text. It (the exception) happens every time I run the snapshots, I think.Sometimes, the text when you have any language that has the bigger letters on gets very buggy and barely readable. This bug happens with any texture pack (including default). I don't think you have to do something particular to reproduce this bug. The console did not say anything special. The only Java exception I saw was:
Client> java.io.IOException: Stream Closed
Client> at java.io.RandomAccessFile.seek(Native Method)
Client> at adu.a(SourceFile:308)
Client> at adu.a(SourceFile:251)
Client> at adv.close(SourceFile:232)
Client> at java.util.zip.DeflaterOutputStream.close(Unknown Source)
Client> at java.io.FilterOutputStream.close(Unknown Source)
Client> at adx.a(SourceFile:140)
Client> at adx.c(SourceFile:128)
Client> at amj.b(SourceFile:30)
Client> at amj.run(SourceFile:23)
Client> at java.lang.Thread.run(Unknown Source)
I do not think this exception has anything to do with the buggy text. It (the exception) happens every time I run the snapshots, I think.
When I try to destory an anvil in creative mode while holding any sword, it mines like I was in survival mode. However, if I try to destroy it while holding something else, it destroys normally.
When I try to destory an anvil in creative mode while holding any sword, it mines like I was in survival mode. However, if I try to destroy it while holding something else, it destroys normally.
EDIT: This applies to ALL blocks, not just anvils
When I try to destory an anvil in creative mode while holding any sword, it mines like I was in survival mode. However, if I try to destroy it while holding something else, it destroys normally.
EDIT: This applies to ALL blocks, not just anvils
EDIT: The blocks act like bedrock in survival when mined with a sword in cretive mode. (they can't be destroyed)
When I try to destory an anvil in creative mode while holding any sword, it mines like I was in survival mode. However, if I try to destroy it while holding something else, it destroys normally.
EDIT: This applies to ALL blocks, not just anvils
EDIT: The blocks act like bedrock in survival when mined with a sword in creative mode. (they can't be destroyed)
Anvils not mining properly in creativeBlocks not mining properly in creative whn holding a sword
Windows 7 64-bit Home Premium, JRE: Java 7 Update 25, JDK: Java 7 Update 25 LWJGL: 2.9.0, OpenGL Version: 4.0
,









Oh, now it works in 13w25a. Sorry to bother you!
Name a mob "Grumm" or "Dinnerbone" and it will turn upside down
You were right. This is a resource pack problem. Mods, you may close this now.