This happens because spectating another entity only attaches your camera, not your entire character. Due to the fact that chunks are rendered in proximity to your character, when your camera moves far enough way, the rendering doesn't continue.
You can see this in action by using any mod with a Freecam mode (like Tweakeroo, for example). When you activate Freecam whilst spectating an entity, your camera will pop up where you began spectating that entity (and you'll see your character floating there, too). Deactivating Freecam puts your camera back into the entity you were spectating.
@Robert Macedolian If there was more than one, than it was an internet issue. Did not mead to multi-post.
Regarding the back and forth between the Mods and Tronics in the earlier comments, I understand the issue.
It has to do with the way that Players and Developers see the game. Developers are used to things performing in certain ways and locations; Players, however, are not. When it comes to the way that commands work when executed from clicking a sign or text in a book, a Developer will know that the command is being executed through the chat by the player that activated it. The Player, on the other hand, will not. Unless the Player themself is versed in code and has a background in that area (which will allow them to understand the inner workings of the game), they will assume it has it's own mechanism to run commands as Players naturally deem that any command run by them must be first typed out into chat before being executed, otherwise it would be run in the background (like commands run from a function file, for example). Because of that, when the Player puts a command under run_command that is too long (but is formatted correctly), the game will spit out the typical Invalid JSON errors, even though the command is correct, leading to the Player getting confused as to why it won't work. Ultimately, the Player will have to find out on their own (likely through Internet searching) about the limit and why it exists, further adding to the confusion and frustration.
What Tronics was trying to propose was to alter the way that the game alerts players to the issue of a command being too long under run_command as simply telling the Player that the command is invalid leads to confusion as they're unlikely to know how the run_command works in the first place. By having alerts that inform the Player about the limit, it would help to alleviate any potential confusion.
My Opinion: This can go both ways in terms of being a Bug or a Feature Request. While it does have the feel of a Feature Request, it can also be seen as a bug as typically a game's developers would choose to design the game in a way that everyone can use it with the only real confusion being when the players are new and must learn the controls and (user-side, not behind-the-scenes) mechanics. I, personally, would go with a chat message alerting the player to the command being too long. (I know the proper place to suggest it.)
Present as of 21w42a
@j_p_smith I always do use the search function first before making a post, but rarely does it actually show any relevant posts, leading me to ultimately create a duplicate.
No idea if this is still being worked on, but can confirm for 1.16 (full release).
Did you make sure there isn't a lava lake under the ground or nearby?
Tested and Confirmed for 1.14.4 Pre-Release 5
Tested and Comfirmed for 1.14.4 Pre-Release 5
Renamed items still retain their usefulness. The crafting book doesn't pick up on renamed items because changing the name changes the NBT of the item and the crafting book is looking for specific (unnamed, normal) items to use.
This isn't a bug as it isn't due to the XP at all. Looking at the crash report, it appears an Enderman wandered into your return portal and glitched out. If you can get back into your world, run the command /kill @e[type=Enderman] and that should fix it.
Time: 1/07/19 12:29 AM
Description: Colliding entity with block
-- Block being collided with --
Details:
Block: Block{minecraft:end_portal}
Block location: World: (-1,63,-1), Chunk: (at 15,3,15 in -1,-1; contains blocks -16,0,-16 to -1,255,-1), Region: (-1,-1; contains chunks -32,-32 to -1,-1, blocks -512,0,-512 to -1,255,-1)
Stacktrace:
at ail.al(SourceFile:916)-- Entity being checked for collision --
Details:
Entity Type: minecraft:enderman (aud)
Entity ID: 159
Entity Name: Enderman
Entity's Exact location: -0.46, 63.31, 0.17
Entity's Block location: World: (-1,63,0), Chunk: (at 15,3,0 in -1,0; contains blocks -16,0,0 to -1,255,15), Region: (-1,0; contains chunks -32,0 to -1,31, blocks -512,0,0 to -1,255,511)
Entity's Momentum: 0.00, -0.23, 0.14
Entity's Passengers: []
Entity's Vehicle: ~~ERROR~~ NullPointerException: null
@Meri Diana Pigmen are different in this case, for when the lightning strikes, in that moment, the pig is despawned at the exact time a Pigman is spawned, and they always spawn with a Golden Sword.
Now this is odd... It's only when you use the "SkeletonType" or "Type" tags with the /summon command that they don't have their respective weapon. Leaving it off spawns them as if they spawned naturally.
Noticed this as well. Happened to me 3 times.Confirmed 1.9.2
Confirmed. Run in latest Spigot 1.9.2 server, got NullPointerException in console:
[10:00:01] [Server thread/WARN]: java.lang.NullPointerException
[10:00:01] [Server thread/WARN]: at net.minecraft.server.v1_9_R1.Village.a(Village.java:394)
[10:00:01] [Server thread/WARN]: at net.minecraft.server.v1_9_R1.PersistentVillage.a(SourceFile:215)
[10:00:01] [Server thread/WARN]: at net.minecraft.server.v1_9_R1.PersistentCollection.get(PersistentCollection.java:50)
[10:00:01] [Server thread/WARN]: at net.minecraft.server.v1_9_R1.WorldServer.b(WorldServer.java:75)
[10:00:01] [Server thread/WARN]: at net.minecraft.server.v1_9_R1.MinecraftServer.a(MinecraftServer.java:268)
[10:00:01] [Server thread/WARN]: at net.minecraft.server.v1_9_R1.DedicatedServer.init(DedicatedServer.java:269)
[10:00:01] [Server thread/WARN]: at net.minecraft.server.v1_9_R1.MinecraftServer.run(MinecraftServer.java:527)
[10:00:01] [Server thread/WARN]: at java.lang.Thread.run(Unknown Source)
EDIT: Doesn't matter if the reputation is negative, positive, or zero. As long as it's there, you get the NullPointerException error.
From the start of 1.8 to 1.9. Wow. This bug has sure been overlooked.
EDIT: Just happened to me. Kinda annoying.
Happens for me too in 1.9 release. Doesn't seem to affect anything, but I think these may be causing the split-second lag spikes I kept getting.
[14:55:08] [Client thread/ERROR]: Item entity 902073 has no item?!
[14:55:08] [Client thread/ERROR]: Item entity 902073 has no item?!
[14:56:21] [Client thread/ERROR]: Item entity 903762 has no item?!
[14:56:21] [Client thread/ERROR]: Item entity 903762 has no item?!
[14:56:21] [Client thread/ERROR]: Item entity 903762 has no item?!
[14:56:21] [Client thread/ERROR]: Item entity 903762 has no item?!
[14:56:21] [Client thread/ERROR]: Item entity 903762 has no item?!
[14:56:21] [Client thread/ERROR]: Item entity 903762 has no item?!
[14:56:21] [Client thread/ERROR]: Item entity 903762 has no item?!
[14:57:12] [Client thread/ERROR]: Item entity 905420 has no item?!
[14:57:12] [Client thread/ERROR]: Item entity 905420 has no item?!
[14:57:56] [Client thread/ERROR]: Item entity 906896 has no item?!
[14:57:56] [Client thread/ERROR]: Item entity 906896 has no item?!
[15:20:45] [Thread-5/ERROR]: Error in class 'LibraryLWJGLOpenAL'
[15:20:45] [Thread-5/ERROR]: Source '1e574f1e-f745-4e41-866e-b4addffe496c' not found in method 'play'
I'm in a Creative Superflat World with a single layer of air. Trying to work on a redstone project and this is getting really annoying.
@Anthony Cicinelli Either the search function needs an overhaul or the bug tracker should move away from Jira because 90% of the time, searching something does not show anything for that issue even though it already exists. This causes lots of duplicates to be created, like this one.