Still an issue in 1.19.10 released July 5th.
Now with screenshots! First three drops should kill all three (23 or 24 block drop --> 20 or 21 points of damage), last two drops should leave all three with one hp (22 block drop --> 19 points of damage), but that's not what happens.
Observed this today as well. Had bred a handful of baby villagers, watched two jump onto a block with a top slab above it (half block gap) and they just slid through the slab.
I think I've figured out what is happening, but I have no idea why this is a thing. In the sixteen chunks that make up the east border and the sixteen chunks that make up the south border, I cannot walk up stairs or slabs, I also cannot jump out of water, standing or flowing. I haven't tried lava. In all the other chunks, including west and north world borders, stairs, slabs, and water work correctly. Going from a south or east border chunk onto a stair or slab in the adjacent chunk also does not work. Frustrating, but I'll just exclude those chunks from any construction I do.
Just for kicks and giggles I tried another new old world tonight, all the options were the same, random seed, spawn for this world is 404,69,4 and this time stairs worked. Went back to the previous world stairs still did not work, tried some slabs as well and couldn't walk up those either. If I jumped up half a stair I could not walk up the second half. Went back to the new world stairs and slabs all worked. Really, really weird. Literally the only change I made in setting up either world was I left the first world with the default name of My World and named the second world test.
Just encountered this bug last night. Started a brand new survival old world on my kindle. Dug a tunnel down to bedrock, made a bunch of stairs, plenty of ceiling room, had to jump up the stairs, not walk up them. Walking down acted like falling off full blocks, instead of the smooth movement of stairs. Running version 1.14.30. Regarding the comment about world origin, spawn was at 420, 68, 4, clearly more than 128 blocks from 0,0. One of the world borders is at 543 (east) and another at -128 (north).
Same issue for me. Version 1.2.13.54, on a Kindle Fire, downloaded from the Google Play Store. Is this related to 32149 or 32096? I'm seeing those behaviors in my worlds as well.
Same issue here for 5th gen (not HD) kindle fire running google play store version.
Backspace works for me in 0.13.1 as well, Thanks!
And the chat window issue is here: https://bugs.mojang.com/browse/MCPE-11812
I was wrong, I have an iphone 4, not 4s and it cannot be updated past ios 7.1.2
Okay, it turns out I'm using an iphone 4, not a 4s. It was a used phone that I was told was a 4s when it was given to me, so I suspect that is part of the issue.
And still an issue in 0.13.1
Had to do a few google searches for the § symbol, but did find it. §4text doesn't show anything while I type, but after hitting return and Back, I do get red text on the screen instead of white.
I can open a separate ticket for the missing text in chat if necessary; I wasn't sure if they were related to a single keyboard issue or two different issues. And I would love to update to ios 8, but itunes won't let me, my 4s iphone is apparently EOL.
Villagers are still dying inside walls or walking through walls as the world loads in 0.13.0 alpha
Same on my iphone 4s, ios 7.1.2, mcpe 0.13.0 alpha. Before Infinite worlds were an option, Old worlds in creative mode could be set to "Always Day". Currently and in the prior version, 0.12.3, "Always Day" is only available in Infinite worlds. Would really like to have "Always Day" back in Old worlds.
Using the backspace button in World Name field, Seed field, or Chat box does not delete the text that is present. It simply moves the cursor to the left.
Additionally when using chat you can not see what you are typing, you get your keyboard and a black screen, no text.
iphone 4s, ios 7.1.2, mcpe 0.13.0 alpha
So now in 0.13 the "Always day" button is just gone. Unless you first make your world infinite. Which was the point to opening the ticket in the first place, you couldn't turn on "Always day" without also turning on "Infinite".
Changing the order of the problem is NOT fixing the problem! Before there was Infinite, we could have Always day in our Old worlds, now we can't!
Still there in 0.12.3 - Can't turn on always day without also turning on Make Infinite
Still a problem in 0.12.3
I don't have a copy of java edition to test it, so someone else will have to check that. Either way though, fall damage is not being calculated correctly, or the calculation has been changed to do different amounts of damage based on mob type, fall height, and reason for fall.