Daniel Lunsford

I'm seeing this as well. Only on multiplayer, though—SP is normal for me

Attached image

Attachments not cooperating; http://www.drlgraphics.com/images/Minecraft/driperrorexample.png

Can't really show the "drip" without video 😛

I have a leaky roof of brick stairs, rightside-up, dripping from the upper seam (not the lower, apparently). FWIW, it seems similar to the way light "leaks" through the seams on stairs as well. v1.5

Edit: Actually, it might be more accurate to say that it drips from the joins where there is an air-block to either side of it

Further Edit: It occurs to me now that I did NOT see this when the roof was wood, only after I switched to brick

I'm big enough to admit when I'm wrong.

Apparently, what is being experienced here is the 2-in-1 effect, as follows:
"2-in-1 Nether Portals - It is possible to end up in a situation where a Nether Portal "randomly" places the player in 1 of 2 possible Normal World destination portals. This is simply because the Nether Portal has two effective coordinates as it is 2 blocks wide, say (X, Y, Z) on the left, and (X+1, Y, Z) on the right. If the player entered on the left side, (X, Y, Z) translates to (X*8, Y, Z*8) in the overworld and the game picks the portal closest to that. If the player entered on the right side, (X+1, Y, Z) translates to (X*8+8, Y, Z*8) and the game picks a portal closest to that point instead. This situation occurs when the Nether Portal's location is roughly equidistant between the 2 Normal World portals (within 8 blocks overworld distance difference)."

After further testing my situation, I have confirmed that this is the case.

However, the documentation references two overworld portals that ALREADY EXIST, and does NOT indicate that the effect will create a NEW overworld portal where only ONE exists—which is what has occurred in my situation. Otherwise, it is behaving exactly as described. So, could be a bug—as the OP stated, I haven't encountered this before 1.4.3—or could be an oversight in the documentation.

That said, the compass issue is definitely a bug.

To be fair, Caio, you are the only one participating in this discussion that is insisting it is working as intended. I seriously doubt that it is--it isn't behaving in a logical manner; I can't bring myself to believe they specifically intended that a portal duplicate itself, and randomly at that. On the other hand, I don't necessarily think it's a malfunction, but an unintended consequence of how it's been written.

It should be fixed, or refined, or at least, made "official."

I can see in my scenario how the portals may be working as described--though it still doesn't make sense that it's being inconsistent, but since it's recalculating each time...

The compass situation is related to the portal--every time I re-enter, it's off, to the same "new" point. Now that I think about it, it could be something to do with the compass being in the Nether...?

I would be willing to accept this errant behavior as "correct" if it could be explained why a portal that (a) already exists, and (b) is the originator of the nether portal, is not suitable for re-connection, and (c) in my experience, not even consistently, since it does SOMETIMES connect to it--it can't be suitable AND unsuitable. Free obsidian is not an excuse to leave a bug alone (still assuming it IS one).

And the compass, whether it points to the spawn or 0,0 or whatever should, at least, point to the SAME place all the time, and not shift when you return through a portal (until the program is reloaded)--this IS a bug, without question. Maybe not hugely important, but should be fixed.

I experienced this error, for the first time, in 1.4.2 (after having briefly used the 1.4.3 pre-release on the same world, and restored 1.4.2). I later destroyed the "wrong" destination portal, went back to the start portal, returned from the Nether, and the destination was "corrected" to the proper start portal.

Possibly unrelated: each time I return from the Nether through either the start or "wrong" portal, my compass points to the wrong "north" until I exit and reload the game (after which, it's still "off" by a few meters).