I just overwrote my minecraft.jar with the new 30 update and as soon as I spawned in my game blocks were showing on fire in the middel with weird blue tinted parts every two blocks. I have a screenshot on the link. Also the title page where it says snappy things in the top right, the words were spinning out of control.
just overwrote my minecraft.jar with the new update and as soon as I spawned in my game blocks were showing on fire in the middel with weird blue tinted parts every two blocks. I have a screenshot but cannot figure out how to load it here for everyone to see.
Also the title page where it says snappy things in the top right, the words were spinning out of control.
Thoughts?
Broken textures and weird bug. You need to replace the old .jar with the one you downloaded, not put them together
Ok.
I did fresh install pacthed with mcpatcher 2.4.0 added in texture pack misa416 here is whats going on.
Select world: Hit play selected world; Screen goes to normal loading screen then jumps back to select world screen for about 1/4 a second, then goes back to loading screen and sits for a good 5 secs then loads up, saw something saying downloading terrain. But now textures are fixed and it plays fine. Load screen jump is the only issue.
i still notice a small lighting bug with cieling tiles (top half-slabs) where it isnt solid, it doesnt have smooth lighting under certain circumstances. I have a few pictures of it but do not know how to post them... the easiest way to duplicate this is to build a two level house with the interrior at least 5x5 in size. Instead of traditional "full block floors" I decided to make some redstone lamp fixtures to go inbetween the floors utilizing the new half slabs.
Side view diagram (upside down):
Bottom view:
Key: = lamp
_______________________________________________________________________
With that said, the blocks where the glass is (or an empty space left out) causes the cieling to look like it isnt smooth lighting, even though it is supposed to be, while the lights are off.
Can you guys please fix redstone torches burning out for no reason?? In my custom map I am forced to not use redstone torches as much as I'd like because they sometimes permanently burn out, and when I try to place a new one it instantly permanently burns out once it gets a redstone update. It should really get fixed.
*sigh* it was meant to do that, if it gets a repeated signal shorter than 7 ticks I think it burns out. They're keeping it that way.
But they still haven't fixed the bug that you have to destroy wooden slaps with a pickaxe instead of a normal axe.
ITS NOT A *beep*ING BUG!
It's a glitch ffs. I assume it was because of their copy-pasting of the slab code that they forgot to change the properties when they made the wooden slab. Oh, and it IS fixed, a few snapshots ago.
Minecraft Wiki: "As of 12w17a, wooden slabs have to be collected with an axe and they are affected by fire."
But this fix only works in a new map. If you load an older one, you still have the old fault.
That's because they didn't change the old wood slabs, they just added in new ones. Any slabs crafted before the change will act like stone, and any crafted after will act like wood. This way current fireplaces/etc don't burn down as soon as the update comes. And some players like it that way, so they're hoarding the current ones on vanilla servers.
*sigh* it was meant to do that, if it gets a repeated signal shorter than 7 ticks I think it burns out. They're keeping it that way.
Actually, iirc the redstone torch is supposed to burn out if it's fed back into it's own block, and turns on/off too quickly in a short amount of time. HOWEVER, after a short time it's supposed to be able to turn back on(rapid pulsar designs utilize this). As well, if you break, then place the torch again, it returns to normal. Currently, if a torch burns out, for any reason, even breaking it and placing it again won't fix it.
Weird. 12w30e vanilla and my 32x32 texture seems to work fine.
And I probably have to start getting used to what multiplayer is like. I was at 5 hunger and ate my cooked pork chop. After the first one went through, I released my right mouse button so I only eat one chop.
Doesn't work that way anymore. Can't cancel eating anymore. The game happily went on to consume the second chop. orz
Is books now craft-able? :/ Because in 12w26-27a, Books aren't craftable, so when I'm doing my hardcore world I can't create a enchanting table to enchant my equips..
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI just overwrote my minecraft.jar with the new 30 update and as soon as I spawned in my game blocks were showing on fire in the middel with weird blue tinted parts every two blocks. I have a screenshot on the link. Also the title page where it says snappy things in the top right, the words were spinning out of control.
The I have the HD update patched in.
Thoughts?
http://postimage.org/image/mz90x80xb/
Broken textures and weird bug. You need to replace the old .jar with the one you downloaded, not put them together
Maps done:1 Maps raged at: 5 Map rage quit: Waking Up
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumYes i have the previously patched HD graphics with no new texture packs. Using misa416
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI did fresh install pacthed with mcpatcher 2.4.0 added in texture pack misa416 here is whats going on.
Select world: Hit play selected world; Screen goes to normal loading screen then jumps back to select world screen for about 1/4 a second, then goes back to loading screen and sits for a good 5 secs then loads up, saw something saying downloading terrain. But now textures are fixed and it plays fine. Load screen jump is the only issue.
Thanks for the forum
Side view diagram (upside down):
Bottom view:
Key:
_______________________________________________________________________
With that said, the blocks where the glass is (or an empty space left out) causes the cieling to look like it isnt smooth lighting, even though it is supposed to be, while the lights are off.
*sigh* it was meant to do that, if it gets a repeated signal shorter than 7 ticks I think it burns out. They're keeping it that way.
ITS NOT A *beep*ING BUG!
It's a glitch ffs. I assume it was because of their copy-pasting of the slab code that they forgot to change the properties when they made the wooden slab. Oh, and it IS fixed, a few snapshots ago.
Minecraft Wiki:
"As of 12w17a, wooden slabs have to be collected with an axe and they are affected by fire."
That's because they didn't change the old wood slabs, they just added in new ones. Any slabs crafted before the change will act like stone, and any crafted after will act like wood. This way current fireplaces/etc don't burn down as soon as the update comes. And some players like it that way, so they're hoarding the current ones on vanilla servers.
Actually, iirc the redstone torch is supposed to burn out if it's fed back into it's own block, and turns on/off too quickly in a short amount of time. HOWEVER, after a short time it's supposed to be able to turn back on(rapid pulsar designs utilize this). As well, if you break, then place the torch again, it returns to normal. Currently, if a torch burns out, for any reason, even breaking it and placing it again won't fix it.
And I probably have to start getting used to what multiplayer is like. I was at 5 hunger and ate my cooked pork chop. After the first one went through, I released my right mouse button so I only eat one chop.
Doesn't work that way anymore. Can't cancel eating anymore. The game happily went on to consume the second chop. orz
Yes. And please don't capitalize every word. It's harder to read than ALL CAPS, which is hard to read.
Did you know I write Science Fiction? Well I do. Check it out at http://planetretcon.com/books/