According to the Gamepedia wiki, spectral arrows are supposed to impart the Glowing effect for 10 seconds. When I use them, it actually does it for about 17 seconds. So I did some testing, and if you give a player or other entity the Glowing effect, it lasts much longer than specified. I couldn't discern a pattern, but in my tests, using "/effect @p minecraft:glowing 5 0" gave me glowing for a bit less than 15 seconds instead of 5. Doing the same using 10 instead, it gave me the effect for 17 or so seconds instead of 10. The weird part is that the HUD next to my inventory shows the proper amount of time, but when it reaches 0, the effect stays applied for much longer before the HUD even disappears.
To reproduce:
1) Use /effect @p minecraft:glowing 10 0 to apply the Glowing effect for apparently 10 seconds.
2) Open your inventory and watch the effects tab. When Glowing reaches 0, you'll see the effect remains almost twice as long anyway.
Attachments
Comments 9
I just tried, but holding F3+C doesn't seem to do anything. I tried for 10 seconds, 20 seconds, and 30 seconds, and it doesn't do anything except bring up the F3 menu after I release.
EDIT For what it's worth, F3+B also doesn't show the bounding boxes for me, instead simply showing the debug menu.
Maybe you need to clear up the secondary issues.
F3+C does always work - or you have a strange keyboard (e.g. laptop) where the combination Fn+F3+C not works.
Anyway, after having the issue please attach the complete output of the "Game Output (Your Minecraft name) " which can be found on the fourth tab of the launcher to this ticket.
I am on a laptop, using a wireless keyboard. It doesn't have the F keys, though, and is set up more like a laptop keyboard with a Fn key. After a little testing, I see that Fn+F3+[key] doesn't work for C, B, N, or P, but it works fine for the other hotkeys. I don't have another keyboard to test with; should I report this as a separate bug?
EDIT Never mind. I tested it with another program, and the key combinations just don't work on my keyboard. Is there a way to force a crash without that shortcut combo?
This is not a bug of Minecraft, it's a bug of your keyboard.
Often the keys like C, B, N, or P have a second meaning when used in conjuction with Fn (e.g. numpad, sound, brightness), so F3+C on a normal keyboard renders to Fn+F3 + Fn+C on your keyboard.
Edit: Don't care about the forced crash, just attach the game log.
Well, as it turns out, my keyboard will hold F3 just fine even after I release the Fn key, and then I can use all the shortcuts normally...this is something I just learned now, so I'm sorry for all this confusion. I'll attach both the crash log and the game output to the original ticket now.
Your game lags because you're logging several hundred or even thousend lines per second:
[14:38:38] [Server thread/INFO]: [@: Set score of useWand for player d47f7fc1-e502-4f11-b507-e6d00ae7d578 to 0]
[14:38:38] [Server thread/INFO]: [@: Set score of useWand for player 736c7486-9a9d-4ad9-953a-6a45ce2ef334 to 0]
[14:38:38] [Server thread/INFO]: [@: Set score of useWand for player 53c57e97-a377-4b4c-8290-ee38fe27382e to 0]
[14:38:38] [Server thread/INFO]: [@: Set score of useWand for player e0c14b0f-bb44-4805-aa2d-f5c60cf2f772 to 0][14:38:38] [Server thread/INFO]: [@: Set score of useWand for player d47f7fc1-e502-4f11-b507-e6d00ae7d578 to 0]
[14:38:38] [Server thread/INFO]: [@: Set score of useWand for player 736c7486-9a9d-4ad9-953a-6a45ce2ef334 to 0]
[14:38:38] [Server thread/INFO]: [@: Set score of useWand for player 53c57e97-a377-4b4c-8290-ee38fe27382e to 0]
[14:38:38] [Server thread/INFO]: [@: Set score of useWand for player e0c14b0f-bb44-4805-aa2d-f5c60cf2f772 to 0]Use the gamerules commandBlockOutput and/or logAdminCommands to suppress logging.
Besides that, both your Java (1.8U40 vs. 1.8U65) and your Intel graphics card drivers (10.xxx vs. 15.xxx) are outdated.
Unable to reproduce. Can you F3 + C for 10 seconds and post a crash log here? And is your world lagging? (The log should say something like "is the server overloaded? Running # seconds behind)