Ralf

Yes it is.

I just tried for about 5 times, after working first tries i then just dropped 1 block down again like described.

Confirmed for 1.11.2, and for overworld!

Building a goldfarm in overworld (like this one: https://www.youtube.com/watch?v=A85yJTV6J4E ), waiting that many⚠️ pigman spawn and walking around portals.
Then, when hitting one (or more) to do them cry, results in some or many normal zombies to spawn outside the constructed square around portals (i built a room beneath the construction, they don't spawn inside that cellar but outside while daytime - in my construction they have 1 block of roof around that cellar).

You are right, sorry.
From the beginning, i was too fixed on those 1024 than to 128 (german wiki is not clear about this).

They can, if you contruct it this way, but it wasn't constructed with a portal in between. Maybe you concentrate on the coordinates i have provided.

Portal 1a (overworld-old): 420,45, 1797(...1800)
Portal 1b (nether-old): 51, 45, 222 (...225)

Portal 2a (overworld-new): -618, 55, 1600 (...1603)
Portal 2b (nether-new) expected generation at: -77, 55, 200

Portal 2b didn't generate which should.

The 1024 are coming from the german translated wiki, since i also checked the english site, i tested with 128 in nether as well.

By reading more about this in the english wiki, i understand, that it normally should search a portal first, if not found THEN check surrounding (16 blocks radius) for possible creation and do so, but it seams that those steps are changed/mixed.

I had same "keeping entity..." stuff. I killed 2-3 of them. One of them was an iron golem, i killed it with kill uuid and replaced it by another one (built it, not summoned), but when i came back to that area of map, it was back alive. After second killing it seemed to work.
I also killed a sheep and a villager, but since i did all this, i get 30-40 lines of "Fetching addPacket for removed entity".
Any clue what i can do against this or what that means?

I can confirm "burning coming out in nether" beginning with 1.9.0 and still with 1.9.4. (pure vanilla server).
It does not happen all the time, but most of it.
I will check out the workaround/fix, sometime soon.

I TPed to coordinates in nether, where portals coordinate are in overworld and removed lava there, seems working, no burning yet.

Edit: I must relativise my prior statement. It still happens that i'm burning when coming out of the portal in nether, though not happening as often.

I get this servermsg by simply going through portal.

Confirmed for 1.8.4 stable.

In my opinion, its a bug and should be fixed because it's breaking redstonephysics. Maybe it seems interesting, because it introduce something like a thyristor, except that a thyristor resets when loosing power at all and you might do things with a repeater energizing a block and with it all redstone surrounding it.

It's not logical what happens to the piston in my video and you are doomed when trying to trigger a piston from above - it even has unpredictable (at least i and friends cannot) behavior depending where you have a triggering button put on (height, distance to piston).

Is this bug beeing fixed sometime or how should i interpret "resolved" and "Works As Intended" ??? My own bug report is marked as duplicat, so can someone please explain me why an extended piston, staying that way without any source of redstonepower, is called "works as inteded"

( http://www.youtube.com/watch?v=GozPy3Qsuko )