Shawn Carter

It is usable as it is, and might even be the best way to handle the render in perspectives. It just becomes confusing because in first person it makes you feel or think you are flying or standing as opposed to isGliding postion.

If rendered down in first person i would imagine you would have to look down to see what is in your hands causing you to fly down. So maybe the OCD in this can be looked over. giggle.

Same issue, this world was created with 15w34a multiplayer server, the error happens with worlds created with earlier versions as well.
After about 10 to 40 seconds, I am disconnected with error "image included."

Can confirm that end portals do not work as well, when created from creative mode. Teleports user to empty area north west of the end island and user dies in void shortly after.

We are getting this error with out using any summon, eggs and or cheat commands. Just testing pure survival. I would imagine in our case it would be natural spawners causing the issue.
The issue is so frequent that it is causing poor server performance.

String names for prefix / suffix must be under 16 charcters including color codes. NBTexplorer.

String Prefix and Suffix need to be under 16 characters long including added color coding.

in the Scoreboard.dat file, find the team name that has longer than 16 total characters in the prefix suffix and reduce the characters.

See the NBTexplorer screenshot above for an example.

Can confirm this for 1.8.3 server jar and realms. Arrows do not hit any target when shooting from within a boat. Arrows leave inventory though, just never end up in a block or on ground. Just vanish :-\
Sigh, Boat wars for the win. lol.

I do believe i need to close this report, after hours of testing and scribbling some math. I have figured out the issue and order of damage per our progression system.

I do apologise for the report. The durability at default item and default allowed in game enchants does seem to be mitigating damage as expected.

@CubeTheThird, Expected Behaviour in our case would be to break the helmet first since the Durability is less, and in our tests we were not taking fall damage. In all cases the boots break first. Even test cases where we have add no enchants, the boots will take more damage and break first, via fighting mobs. "NOTE: no fall damage." This is what led us to believe possibly the Durability is not behaving as expected.

@kumasasa - unbreaking 7 or v11 in our case is obtained through progression events via command blocks.

Thank You Sonic and Kumasasa, with out updating drivers that acer has not provided yet the issue was resolved 3 separate times by restarting the game client, but seems to happen again after about half hour of game play.
Have contacted acer for updated drivers.

I had issues with this when trying to run the clock to fast, tick it down to 4tps or use 2nd command block to set air to the redstone on 2nd cycle.

The issue seems to only effect when placing on block faces, facing East and West in 1.8.2pre4.

Just a few blocks below default level of 63 for water. server jar ver. 1.8.2pre1 (new world)

{"coordinateScale"\:684.412,"heightScale"\:684.412,"lowerLimitScale"\:512.0,"upperLimitScale"\:512.0,"depthNoiseScaleX"\:200.0,"depthNoiseScaleZ"\:200.0,"depthNoiseScaleExponent"\:0.5,"mainNoiseScaleX"\:80.0,"mainNoiseScaleY"\:160.0,"mainNoiseScaleZ"\:80.0,"baseSize"\:8.5,"stretchY"\:12.0,"biomeDepthWeight"\:1.0,"biomeDepthOffset"\:0.0,"biomeScaleWeight"\:1.0,"biomeScaleOffset"\:0.0,"seaLevel"\:58,"useCaves"\:true,"useDungeons"\:true,"dungeonChance"\:100,"useStrongholds"\:true,"useVillages"\:true,"useMineShafts"\:true,"useTemples"\:true,"useMonuments"\:true,"useRavines"\:true,"useWaterLakes"\:true,"waterLakeChance"\:30,"useLavaLakes"\:true,"lavaLakeChance"\:80,"useLavaOceans"\:false,"fixedBiome"\:-1,"biomeSize"\:1,"riverSize"\:2,"dirtSize"\:20,"dirtCount"\:10,"dirtMinHeight"\:0,"dirtMaxHeight"\:256,"gravelSize"\:20,"gravelCount"\:10,"gravelMinHeight"\:0,"gravelMaxHeight"\:256,"graniteSize"\:20,"graniteCount"\:15,"graniteMinHeight"\:0,"graniteMaxHeight"\:255,"dioriteSize"\:20,"dioriteCount"\:15,"dioriteMinHeight"\:0,"dioriteMaxHeight"\:255,"andesiteSize"\:20,"andesiteCount"\:15,"andesiteMinHeight"\:0,"andesiteMaxHeight"\:255,"coalSize"\:20,"coalCount"\:20,"coalMinHeight"\:0,"coalMaxHeight"\:255,"ironSize"\:10,"ironCount"\:20,"ironMinHeight"\:0,"ironMaxHeight"\:105,"goldSize"\:10,"goldCount"\:10,"goldMinHeight"\:0,"goldMaxHeight"\:105,"redstoneSize"\:8,"redstoneCount"\:8,"redstoneMinHeight"\:0,"redstoneMaxHeight"\:105,"diamondSize"\:4,"diamondCount"\:40,"diamondMinHeight"\:0,"diamondMaxHeight"\:105,"lapisSize"\:7,"lapisCount"\:1,"lapisCenterHeight"\:16,"lapisSpread"\:105}

level-seed=-885595143

x -247 y74 z478

Same issue in 1.8.1 pre5 server. The intended approx 20 x 20 block centered around spawn point as the randomized spawn area changes when spawn protection is changed and or world border is expanded causing undesirable expanded randomization of spawn, mostly to the north east in the case of the world border.

Expected results: Spawn protection area and World border to be separate from the expected 20 x 20 randomized spawn area.

I resolved this error for my 1.8.1pre3 / pre5 servers by disabled the Service for ReadyBoost on our Windows server machines. I noticed randomly windows was using 100% of HD resource read/write and was causing the server to "Run Behind" or just crashing I/O error.

4 days running since last maintenance & backup, with no crashing and minimal "Run Behind."

using startup bat:
"C:\Program Files\Java\jre1.8.0_25\bin\java.exe" -server -d64 -Xms3848M -Xmx3848M -jar minecraft_server.1.8.1-pre5.jar nogui

Confirmed in 1.8.1pre5 and just caught a user doing it. He was forcing his client down and reopening, Logging back in and picking up emeralds he was throwing down in spawn.
Error Log: http://pastebin.com/VW9QGcSg
server ip: play.MinecraftGods.com
After several errors as seen in the pastebin, i checked the users inventory and seen he has managed to gain 59 emeralds.

I was able to duplicate this myself by logging my client into 2 separate machines and forcing one down, then joining with the other machine. I did this on LAN connection with the server, seems easier to do if outside the Network where the server is hosted.