asdf
- zoshi235
- zoshi235
- America/New_York
- Yes
- No
![[Mojang] Jeb (Jens Bergensten)](../../../data/assets/gravatar/jeb.jpeg){kind=small}
MC-9436
Those 2 new screenshots would demonstrate the problem a bit better if it were day.
Placing double slabs ignores datavaluePlacing double slabs ignores damage value
The ability to use double slabs in creative mode is infinitely useful. It doubles building speed when using slabs, and the normally unobtainable slab with a damage value of 6 is a block used regularly by most advanced builders I've seen.
In the snapshot, this functionality has been removed. Placing a double brick slab results in a double stone slab, and double birch slab results in oak. This is incredibly annoying to say the least.
Come to think of it, blocks like Huge Mushroom that have always ignored da
tavalue are just as annoying. I'm sure I'm not the only one who would like to build their own giant mushrooms without having to use pistons or MCEdit. Please remedy this.The ability to use double slabs in creative mode is infinitely useful. It doubles building speed when using slabs, and the normally unobtainable slab with a damage value of 6 is a block used regularly by most advanced builders I've seen.
In the snapshot, this functionality has been removed. Placing a double brick slab results in a double stone slab, and double birch slab results in oak. This is incredibly annoying to say the least.
Come to think of it, blocks like Huge Mushroom that have always ignored damage value are just as annoying. I'm sure I'm not the only one who would like to build their own giant mushrooms without having to use pistons or MCEdit. Please remedy this.
Minecraft, in slow motion. This one is so strange I can't really explain it beyond that. I think it's best to just watch the video.
http://www.youtube.com/watch?v=3fi58ITZaPM
I wouldn't normally be reporting something I wasn't able to at least reproduce, but my friend recently confirmed this was happening to him,
and I would personally classify this as "Urgent."Minecraft, in slow motion. This one is so strange I can't really explain it beyond that. I think it's best to just watch the video.
http://www.youtube.com/watch?v=3fi58ITZaPM
I wouldn't normally be reporting something I wasn't able to at least reproduce, but my friend recently confirmed this was happening to him, but he doesn't have a Jira account, and this is the kind of bug I'd rather risk duplicating than not reporting.
Minecraft, in slow motion. This one is so strange I can't really explain it beyond that. I think it's best to just watch the video.
http://www.youtube.com/watch?v=3fi58ITZaPM
I wouldn't normally be reporting something I wasn't able to at least reproduce, but my friend recently confirmed this was happening to him, but he doesn't have a Jira account, and this is the kind of bug I'd rather risk duplicat
ingthan not reporting.Minecraft, in slow motion. This one is so strange I can't really explain it beyond that. I think it's best to just watch the video.
http://www.youtube.com/watch?v=3fi58ITZaPM
I wouldn't normally be reporting something I wasn't able to at least reproduce, but my friend recently confirmed this was happening to him, but he doesn't have a Jira account, and this is the kind of bug I'd rather risk reporting a duplicate than not reporting at all.
Hold on a minute, apparently ctrl+enter means publish. let me get this filled out.
Windows 7 home premium, Service Pack 1
Hold on a minute, apparently ctrl+enter means publish. let me get this filled out.
The new variable redstone strength is having some strange effects on certain blocks. When an object such as a weighted pressure plate or daylight sensor is placed, and hooked up to a line connected to a row of pistons, then slowly increased in power, almost every other piston pulses twice and causes the next piston to get stuck in a position where it is both extended and retracted at the same time. Which pistons get stuck is 100% reproducible every time the machine is reset, but changes when the machine is moved or rotated.
Windows 7 home premium, Service Pack 1
Windows 7 home premium, Service Pack 1
Java Recommended Version 7, Update 10
The new variable redstone strength is having some strange effects on certain blocks. When an object such as a weighted pressure plate or daylight sensor is placed, and hooked up to a line connected to a row of pistons, then slowly increased in power, almost every other piston pulses twice and causes the next piston to get stuck in a position where it is both extended and retracted at the same time. Which pistons get stuck is 100% reproducible every time the machine is reset, but changes when the machine is moved or rotated.
Note that this is not a duplicate of
MC-127
The new variable redstone strength is having some strange effects on certain blocks. When an object such as a weighted pressure plate or daylight sensor is placed, and hooked up to a line connected to a row of pistons, then slowly increased in power, almost every other piston pulses twice and causes the next piston to get stuck in a position where it is both extended and retracted at the same time. Which pistons get stuck is 100% reproducible every time the machine is reset, but changes when the machine is moved or rotated.
Note that this is not a duplicate of
MC-127as far as I can tell as the pistons getting stuck seems to be a by-product of a bug with the redstone, not the actual bug I am reporting.
The new variable redstone strength is having some strange effects on certain blocks. When an object such as a weighted pressure plate or daylight sensor is placed, and hooked up to a line connected to a row of pistons, then slowly increased in power, almost every other piston pulses twice and causes the next piston to get stuck in a position where it is both extended and retracted at the same time. Which pistons get stuck is 100% reproducible every time the machine is reset, but changes when the machine is moved or rotated.
Note that this is not a duplicate of
MC-127, as far as I can tell, as the pistons getting stuck seems to be a by-product of a bug with the redstone, not the actual bug I am reporting.
The new variable redstone strength is having some strange effects on certain blocks. When an object such as a weighted pressure plate or daylight sensor is placed,
andhooked up to a line connected to a row of pistons,thenslowly increased in power, almost every other piston pulses twice and causes the next piston to get stuck in a position where it is both extended and retracted at the same time. Which pistons get stuck is 100% reproducible every time the machine is reset, but changes when the machine is moved or rotated.Note that this is not a duplicate of
MC-127, as far as I can tell, as the pistons getting stuck seems to be a by-product of a bug with the redstone, not the actual bug I am reporting.The new variable redstone strength is having some strange effects on certain blocks. When an object such as a weighted pressure plate or daylight sensor is placed, hooked up to a line connected to a row of pistons, and slowly increased in power, almost every other piston pulses twice and causes the next piston to get stuck in a position where it is both extended and retracted at the same time. Which pistons get stuck is 100% reproducible every time the machine is reset, but changes when the machine is moved or rotated.
Note that this is not a duplicate of
MC-127, as far as I can tell, as the pistons getting stuck seems to be a by-product of a bug with the redstone, not the actual bug I am reporting.
The new variable redstone strength is having some strange effects on certain blocks. When an object such as a weighted pressure plate or daylight sensor is placed, hooked up to a line connected to a row of pistons, and slowly increased in power, almost every other piston pulses twice and causes the next piston to get stuck in a position where it is both extended and retracted at the same time. Which pistons get stuck is 100% reproducible every time the machine is reset, but changes when the machine is moved or rotated.
Note that this is not a duplicate ofMC-127, as far as I can tell, as the pistons getting stuck seems to be a by-product of a bug with the redstone, not the actual bug I am reporting.The new variable redstone strength is having some strange effects on certain blocks. When an object such as a weighted pressure plate or daylight sensor is placed, hooked up to a line connected to a row of pistons, and slowly increased in power, almost every other piston pulses twice and causes the next piston to get stuck in a position where it is both extended and retracted at the same time. Which pistons get stuck is 100% reproducible every time the machine is reset, but changes when the machine is moved or rotated.
Please note that this is not a duplicate of
MC-127, as far as I can tell, as the pistons getting stuck seems to be a by-product of a bug with the redstone, not the actual bug I am reporting.
The new variable redstone strength is having some strange effects on certain blocks. When an object such as a weighted pressure plate or daylight sensor is placed, hooked up to a line connected to a row of pistons, and slowly increased in power,
almost every other piston pulses twiceand causes the next piston to get stuck in a position where it is both extended and retracted at the same time. Which pistons get stuck is 100% reproducible every time the machine is reset, but changes when the machine is moved or rotated.Please note that this is not a duplicate of
MC-127, as far as I can tell, as the pistons getting stuck seems to be a by-product of a bug with the redstone, not the actual bug I am reporting.The new variable redstone strength is having some strange effects on certain blocks. When an object such as a weighted pressure plate or daylight sensor is placed, hooked up to a line connected to a row of pistons, and slowly increased in power, The redstone seems to cut out for a split second and causes the next piston to get stuck in a position where it is both extended and retracted at the same time. Which pistons get stuck is 100% reproducible every time the machine is reset, but changes when the machine is moved or rotated.
Please note that this is not a duplicate of
MC-127, as far as I can tell, as the pistons getting stuck seems to be a by-product of a bug with the redstone, not the actual bug I am reporting.
The new variable redstone strength is having some strange effects on certain blocks. When an object such as a weighted pressure plate or daylight sensor is placed, hooked up to a line connected to a row of pistons, and slowly increased in power, The redstone seems to cut out for a split second
andcausesthe next piston to get stuck in a position where it is both extended and retracted at the same time. Which pistons get stuck is 100% reproducible every time the machine is reset, but changes when the machine is moved or rotated.Please note that this is not a duplicate of
MC-127, as far as I can tell, as the pistons getting stuck seems to be a by-product of a bug with the redstone, not the actual bug I am reporting.The new variable redstone strength is having some strange effects on certain blocks. When an object such as a weighted pressure plate or daylight sensor is placed, hooked up to a line connected to a row of pistons, and slowly increased in power, The redstone seems to cut out for a split second, causing the next piston to get stuck in a position where it is both extended and retracted at the same time. Which pistons get stuck is 100% reproducible every time the machine is reset, but changes when the machine is moved or rotated.
Please note that this is not a duplicate of
MC-127, as far as I can tell, as the pistons getting stuck seems to be a by-product of a bug with the redstone, not the actual bug I am reporting.
I can almost guarantee that this contains some duplicates, however, I would rather post all instances I found in one place than try and weed out the specific instances that have been reported already.
---------------
Blocks affected: Glass, Redstone Block, Glowstone, Slab, Stair
Blocks used for testing: Repeater, Door, Pressure Plate, Button, Lever (top, bottom, side), Rail, Ladder, Trapdoor, Torch (top, side), Flowerpot, Redstone Dust, Fire (top, bottom, side)
----------------
First image: Control. How we would expect blocks that must be
placed onother blocks to behave.Glass: Non-solid block. Would expect it to support nothing, yet supports torches, just on top.
Redstone Block: Does not support Buttons or Ladders.
Glowstone: Supports only Redstone Dust and Trapdoor
Slab and Stair: Special case. Only thing I expected to work that did not is a lever on the bottom of a bottom slab/stair.
I can almost guarantee that this contains some duplicates, however, I would rather post all instances I found in one place than try and weed out the specific instances that have been reported already.
---------------
Blocks affected: Glass, Redstone Block, Glowstone, Slab, Stair
Blocks used for testing: Repeater, Door, Pressure Plate, Button, Lever (top, bottom, side), Rail, Ladder, Trapdoor, Torch (top, side), Flowerpot, Redstone Dust, Fire (top, bottom, side)
----------------
First image: Control. How we would expect blocks that must be attatched to other blocks to behave.
Glass: Non-solid block. Would expect it to support nothing, yet supports torches, just on top.
Redstone Block: Does not support Buttons or Ladders.
Glowstone: Supports only Redstone Dust and Trapdoor
Slab and Stair: Special case. Only thing I expected to work that did not is a lever on the bottom of a bottom slab/stair.
A good fix would be to simply make the dispenser fire as fast as whatever clock you're using can go. It would not only resolve the update bug but also remove the need to use a silly workaround to make the dispenser fire quickly.
This is a bug with stacks of items that use 2 textures. It also happens with stacked potions. Strangely it doesn't happen with clocks or compasses, apparently they use a different method to make the second texture rotatable.
Oh cool, only 30%? Looks like people are getting better at searching. Last one I saw was at 50%.
The thing is, I did in fact search for problems relating to minecarts. What do you want me to do, not post a glitch in case I just missed a duplicate?
Edit: Ah, I see why. The bug this is a duplicate of was on 1.4 yesterday. I only looked at 1.5 glitches, since I don't remember ever seeing this in 1.4.
That would make more sense, but then every time you misplaced a slab you'd have to recraft it. That would get especially annoying on large builds.
I believe it's a request to fix version 1.4.5, not a version in which it is fixed. English is a silly language.
I'm seeing this confirmed in many peoples' videos, though not in any of my personal experiences. On servers as well.
You know, as many reports as there are, searching for related bug report before reporting yourself just isn't an effective option in most cases. Sorry for the duplicate.
Restarting the game didn't do it, I always had to fly away and unload the chunk to make it happen.
do the words "Work In Progress" or "Developer Art" mean anything to you silly people? The icon says "WIP", and the block itself is incredibly buggy and currently uses textures from another block. The Beacon went through like, 8 aesthetic and crafting changes before being released.
Though I do like (as well as share) the "Report everything you find" mentality, as long as you search for similar issues first.
I'm also getting instances of a single item staying on top of a hopper and being duplicated into subsequent hoppers infinitely.
I have found another way to produce this bug - as a byproduct of another bug I seem to have found in issue
MC-6486.@Charlie McFadden
Worse than the piston cloning a block glitch, it's the dreaded block cloning a piston glitch!
If it were intended, it would have been marked as "Works as intended" as soon as it was confirmed. But no, this report is marked as Confirmed and Unresolved.
Yeah! Go Jeb! Assuming it is in fact fixed and not just no longer reproducing in his end...
Correction: it's SUPPOSEDLY resolved. TO THE TESTING RANGE!
I think it is. I seem to recall some mindcrack videos on recent snapshots with the issue still present.
Added a couple screenshots from my duplicate of the report. Note that the hole in the ceiling of the first one is to show the thickness of the ceiling and does not actually affect the bad lighting of the room.
Well, I didn't do that last image, but I assume the area is completely enclosed and lightless, yet you can clearly light still getting in.
There is no hole. The entire glitch is that light is passing through solid objects, as seen in my screenshots.
There isn't a hole. Trust me. The only reason there's a hole in one of my screenshots is to show the thickness of the ceiling, it wouldn't cause the effect shown.
The rules of redstone are very simple when you know them. No other device takes a block update as an input, except piston bud switches, which is also confirmed to be a bug. It also causes more problems than it solves, as redstone that isn't pointing at the dispenser, and in some cases not even next to the dispenser, will set it off.
Press the plus button next to the attachments header and upload using that instead.
So you aren't going to note the ones that don't work as intended?
You aren't supposed to be able to put levers on the bottoms of slabs when you can put them on the top? What's the reasoning behind that?
Not quite. There was a mod a while back that allowed you too place torches on bottom slabs, by just lowering the mesh and bounding box by half a block. The torch itself was still technically in the block above the slab.
It has been fixed in the latest snapshot. Not the version that has already been released. If it were fixed in the version that was already released, it would be 1.4.8 instead of 1.4.7.
I couldn't have said it better myself.
Minecraft hasn't always had these lighting issues. If only there were a reliable way to figure out exactly what change introduced what issue.
Well, ok, but I meant ALL the lighting glitches. We've had dark spots since quite a bit before the increase in height.
Please give a screenshot or video of it happening, showing with F3 what snapshot you're in.
@William Pearson: One of the goals of the Redstone Update was to make Redstone more reliable and self-consistent. No other block activates on redstone updates, and the behavior didn't even make sense. Yes, it IS all bug.
Ah, floating point precision errors. You have plagued us since the beginning. First you reared your head as we approached the farlands, now you show it again as time itself.
I believe I have found a serious issue related to this bug. A quick search through the issue tracker revealed my worst fears: Anvils can be decorporealized at will. I have uploaded a series of four images describing the process.
yeah, that would be why it was closed several months ago.
Poor frapjump. In the mean time, see if doubling the thickness of the top ceiling helps. It did for my stuff.
This is not actually fixed. Map "The Lands of Reminiscence" still crashes when loading a spawner.
Map can be found here: http://www.planetminecraft.com/project/the-lands-of-reminiscence-a-survivaladventure-map-for-single-and-multi-players/
Created a profile for 1.5, since most servers haven't switched yet, only option for the default profile is now play offline. No way to play online, no option to delete the new profile, nothing.
Edit:
Found how to delete the alternate profile, default profile remains broken.
Edit 2:
Found a workaround by creating a new profile with the same settings as default and using that. Unfortunately it seems that you can only create one active profile at a time, as logging into another profile with the same account causes the previous profiles to become offline only upon restarting the launcher.
Oh wow, didn't even think of that. Robin's workaround is way better. It's almost a non-issue now. Switch, logout, play.
I have uploaded some screenshots. Figure 1 shows the pattern it uses to choose spaces to place the player. There's an issue where the area is one block too short on the south end, as in figure 2. I've also found a quirk where it prioritizes spots based on surrounding spots that should have no effect, as in figure 3.
Clam lol, that is most likely an entirely different issue. The range of a minecart is much smaller than 10 blocks, and I've seen people dumped out over 50 blocks away usually where they were a minute or so before getting out.
The glitch is only partially fixed. Rather than spawning you several blocks away from the minecart, it drops you within one block of the minecart. The issue of the area being one block smaller on the south side is still there, and with the area so small, this completely eliminates dismounting the minecart to the south.
In addition, dismounting a boat offsets your drop position depending on the direction the boat is facing, making even more difficult to work with than minecarts.
Edit: The more I work with boats the less consistent their dismount position is. Recreating setups in different plocations changes whether you can dismount in a certain position, so does changing something and then undoing that change. The setup involves placing a boat between four stone walls, the boat floating on water, and attempting to dismount outside of the walls. I am uploading a screenshot to demonstrate the starting setup.
I'm having a similar issue, but my client is downloading skins successfully. Instead of my skin being default Steve, it's a previous version of my skin and remains unchangeable.
You can see my report as the fourth duplicate on this issue for more details. I'm not sure it's actually a duplicate since every detail of the issue is different, but whatever.
Can you give us a screenshot of the location it happened in, PTR_91?
The four screenshots I originally posted are invalid. The real cause is looking at an anvil facing the other direction, not turning. The hitboxes of all anvils is set to the last one you looked at. The same thing happens with double chests, but the difference isn't big enough to let you pass through completely, which if I'm not mistaken, makes this issue a duplicate.
Still present in 14w17a.
Clone does not respect orientation with rails. There seems to be 2 separate issues here, one where the setblock command doesn't respect orientation of some blocks, and one where rail's default behavior is overriding the behavior of the setblock and clone commands.