Sir Lord Jeff
- mickeyjm
- mickeyjm
- Europe/Stockholm
- Yes
- No
MC-3788![[Mojang] Jeb (Jens Bergensten)](../../../data/assets/gravatar/jeb.jpeg){kind=small}
MCL-1766
Shows 0.0.0.0:PORT and using actual ip 192.168.0._:PORT doesnt work either
LAN Broken (Shows 0.0.0.0:PORT and using actual ip 192.168.0._:PORT doesnt work either)LAN Broken
Command Blocks
Command blocks that have a name with a format code (like §2) will change the colour of the rest of the text unless a coloured player name (from a team) is in the message, at which point the text goes white again. This is inconsistent with player names which automatically reformat themselves (eg Joined message, killed message although oddly not left message)
Sometimes if you move the mouse too fast and click inside the hotbar slot
)and then move your mouse outside the window (normally I do that because of the momentum of the mouse) it will
insteadregister the user as clicking outside the inventory window.This isn't due to a large tick time and the game thinking the mouse was outside the window because I am running at ~200fps so there is no way I could have moved the mouse that far in 1/200th of a second. Besides the time between clicking and it dropping is clearly visible (around 1/10 of a second I'd guess).
It looks like this may be due to the new dragging items feature waiting to see if it is a drag or click. If so I'd recommend saving the previous location of the mouse at the start of a drag and using that position data if it was actually just a "drop".
Sorry if this is a duplicate but I wasn't sure how to word the search and couldn't find anything.
Sometimes if you move the mouse too fast and click inside the hotbar slot and then move your mouse outside the window (normally I do that because of the momentum of the mouse
This isn't due to a large tick time and the game thinking the mouse was outside the window at the time because I am running at ~200fps so there is no way I could have moved the mouse that far in 1/200th of a second. Besides the time between clicking and it dropping is clearly visible (around 1/10 of a second I'd guess).
It looks like this may be due to the new dragging items feature waiting to see if it is a drag or click. If so I'd recommend saving the previous location of the mouse at the start of a drag and using that position data if it was actually just a "drop".
Sorry if this is a duplicate but I wasn't sure how to word the search and couldn't find anything.
Windows 7 64 bit Home premium
Java 7 update 9 64bit (i think)Windows 7 64 bit Home premium
Java 1.7.0_09
This may be due to the long standing bug/feature that if you press alt with a key down then release the key and click the game it wont register you releasing the key therefore meaning that you cant walk backwards because you are still "Pressing" forwards.
PS no-one report/fix the alt bug its really useful if you need to go afk for a sec and want to continue walking
In version 1.5.2, I had this running a vanilla LAN server. Windows 7 64bit Java 7. My brother who was also on the server saw the arrows fly weird but could shoot normal ones himself
(Updated and better worded version of MC9738)
If 2 players are standing in roughly the same place and one of them is given an item there is a chance it will be picked up by the other player.
(Probably due to items being spawned at the location of the player which also causes items to not pick up if the player teleports)Would be better/sensible to put items into the inventory rather than at the feet of the player as this is more consistent
(Updated and better worded version of MC9738)
If 2 players are standing in roughly the same place and one of them is given an item there is a chance it will be picked up by the other player.
(Probably due to items being spawned at the location of the player which also causes items to not pick up if the player teleports)Would be better/sensible to put items into the inventory rather than at the feet of the player as this is more consistent
(Updated and better worded version of
MC-9738)If 2 players are standing in roughly the same place and one of them is given an item there is a chance it will be picked up by the other player.
(Probably due to items being spawned at the location of the player which also causes items to not pick up if the player teleports)Would be better/sensible to put items into the inventory rather than at the feet of the player as this is more consistent
Yes but that causes poor formatting with command outputs as it will always be white and not grey and italics, but changing it to be like that means that if you change the command to a say command the formatting will be wrong again. And this is inconsistent with coloured player names anyway, which reformat themselves to be correct.
Agreed, also if you check out my report I suggested a potential solution (code wise not work around)
Note I haven't tried this myself but SMP is now within SSP so logically all multiplayer bugs (maybe except those involving latency or other players) should be in single player so running as server shouldn't make a difference
Confirmed to also occurs with block breaking particles, and other types too I'd imagine
Same problem in 1.5.2, never been able to see world in multiplayer menu unless on the same pc.
Workaround is in direct connect to enter COMPUTERNAME:port or use ipconfig in cmd.exe to get your local ip and use that with the port
I have noticed this also happens when you play a record if default music is playing
Tested it in 15w50a and I didn't crash, can anyone else confirm it's been fixed or did I get lucky?
Edit: Checked the source code, it has been fixed.
The previous code (renamed by me so I can understand it better)
The new code (again, renamed so I can understand it)
As you can see in the new code for placing fire only runs if the fireball didn't hit any entity
As swekob says, most likely intended. If you look in the code for small fireballs it checks that the mob isn't fireproof before dealing damage. All nether mobs are fireproof and consequently can't be damaged by fireballs.
The issue is with the server so I can't force a crash but I can include the latest.log