Josh74000MC
- Josh74000MC
- josh74000mc
- Europe/Stockholm
- Yes
- No
some entities can't be summoned when I usethe /summon commandcannot summon lightning bolt using the /summon command
When I use the /summon command,
some entities can't be summoned, this happens when I do /summon minecraft:lightning_boltWhen I use the /summon command, lightning bolts can't be summoned.
Skins don't work on versions prior to version 1.7.2Skin bug for 1.6.4 and lower
When holding the trident in game, it doesn't show it and the arm position is incorrect when holding it too. But sometimes it like shows it but not being held correctly. But for me its invisible
Summary:
Trident is invisible in the players hand in first and third person, unless in first person the player is within range of a block or entity. Or sometimes randomly starts flickering or disappears.Possible example steps to reproduce, doesn't trigger every time:
1. Create a flat world creative.
2. Equip a trident in first person in creative or survival.
3. Notice the trident is not visible, unless within range of a block or entity (hit range ~<5 blocks).
4. Switch to 3rd person and notice the trident is not visible at all in both front and back view.Video Attached:
MCPE-31673.mp4![]()
MCPE-31673 (2).mp4![]()
Notes:
Original report:
When holding the trident in game, it doesn't show it. But sometimes it like shows it but not being held correctly. But for me its invisible
Edit
The bug was fixed on version 1.2.14.2.
Summary:
Trident is invisible in the players hand in first and third person, unless in first person the player is within range of a block or entity. Or sometimes randomly starts flickering or disappears.Possible example steps to reproduce, doesn't trigger every time:
1. Create a flat world creative.
2. Equip a trident in first person in creative or survival.
3. Notice the trident is not visible, unless within range of a block or entity (hit range ~<5 blocks).
4. Switch to 3rd person and notice the trident is not visible at all in both front and back view.Video Attached:
MCPE-31673.mp4![]()
MCPE-31673 (2).mp4![]()
Notes:
Original report:
When holding the trident in game, it doesn't show it. But sometimes it like shows it but not being held correctly. But for me its invisible
Edit:
The bug was fixed on version 1.2.14.2.
Summary:
Trident is invisible in the players hand in first and third person, unless in first person the player is within range of a block or entity. Or sometimes randomly starts flickering or disappears.Possible example steps to reproduce, doesn't trigger every time:
1. Create a flat world creative.
2. Equip a trident in first person in creative or survival.
3. Notice the trident is not visible, unless within range of a block or entity (hit range ~<5 blocks).
4. Switch to 3rd person and notice the trident is not visible at all in both front and back view.Video Attached:
MCPE-31673.mp4![]()
MCPE-31673 (2).mp4![]()
Notes:
Original report:
When holding the trident in game, it doesn't show it. But sometimes it like shows it but not being held correctly. But for me its invisible
Edit:
The bug was fixed on version 1.2.14.2
.Summary:
Trident is invisible in the players hand in first and third person, unless in first person the player is within range of a block or entity. Or sometimes randomly starts flickering or disappears.Possible example steps to reproduce, doesn't trigger every time:
1. Create a flat world creative.
2. Equip a trident in first person in creative or survival.
3. Notice the trident is not visible, unless within range of a block or entity (hit range ~<5 blocks).
4. Switch to 3rd person and notice the trident is not visible at all in both front and back view.Video Attached:
MCPE-31673.mp4![]()
MCPE-31673 (2).mp4![]()
Notes:
Original report:
When holding the trident in game, it doesn't show it. But sometimes it like shows it but not being held correctly. But for me its invisible
Edit:
The bug was fixed on version 1.2.14.2, but still exists on the non beta (1.2.13.60 and 1.2.16)
Summary:
Trident is invisible in the players hand in first and third person, unless in first person the player is within range of a block or entity. Or sometimes randomly starts flickering or disappears.Possible example steps to reproduce, doesn't trigger every time:
1. Create a flat world creative.
2. Equip a trident in first person in creative or survival.
3. Notice the trident is not visible, unless within range of a block or entity (hit range ~<5 blocks).
4. Switch to 3rd person and notice the trident is not visible at all in both front and back view.Video Attached:
MCPE-31673.mp4![]()
MCPE-31673 (2).mp4![]()
Notes:
Original report:
When holding the trident in game, it doesn't show it. But sometimes it like shows it but not being held correctly. But for me its invisible
Edit:
The bug was fixed on version 1.2.14.2, but still exists on the non beta version (1.2.13.60 and 1.2.16)
![]()
It just comes up with this
Windows 10 64 Bit
Intel(R) HD Graphics
Java
Windows 10 64 Bit
Intel(R) HD Graphics
Java 8
Windows 10 64 Bit
Intel(R) HD Graphics
Java 8
4GB RAM
Usually I could set my render distance which is usually set at the max of 30, but now I can only set it to 16. This started happening after I joined the beta on Windows 10.
Usually I could set my render distance which is usually set at the max of 30, but now I can only set it to 16. This started happening after I joined the beta on Windows 10.
Device Specs:
Intel i7 processor
Intel HD Graphics
Windows 10 1709 (soon to update to 1803)
Usually I could set my render distance which is usually set at the max of 30, but now I can only set it to 16. This started happening after I joined the beta on Windows 10.
Device Specs:
Intel
i7 processor
Intel HD Graphics
Windows 10 1709 (soon to update to 1803)Usually I could set my render distance which is usually set at the max of 30, but now I can only set it to 16. This started happening after I joined the beta on Windows 10.
Device Specs:
Intel (R) Pentium (R) processor 1.7GHz 2 cores
Intel HD Graphics
Windows 10 1709 (soon to update to 1803)
Usually I could set my render distance which is usually set at the max of 30, but now I can only set it to 16. This started happening after I joined the beta on Windows 10.
Device Specs:
Intel (R) Pentium (R) processor 1.7GHz 2 cores
Intel HD Graphics
Windows 10 1709 (soon toupdateto 1803)Usually I could set my render distance which is usually set at the max of 30, but now I can only set it to 16. This started happening after I joined the beta on Windows 10.
Device Specs:
Intel (R) Pentium (R) processor 1.7GHz 2 cores
Intel HD Graphics
Windows 10 1709 (now updating to 1803 which should fix it)
Usually I could set my render distance which is usually set at the max of 30, but now I can only set it to 16. This started happening after I joined the beta on Windows 10.
Device Specs:
Intel (R) Pentium (R) processor 1.7GHz 2 cores
Intel HD Graphics
Windows 10 1709 (now updating to 1803 which should fix it)Usually I could set my render distance which is usually set at the max of 30, but now I can only set it to 16. This started happening after I joined the beta on Windows 10.
Device Specs:
Intel (R) Pentium (R) processor 1.7GHz 2 cores
Intel HD Graphics
Windows 10 1803
I think it must be the windows 10 OS update, on the previous build it was running fine.
crashes seem to have stopped, must be something that happens sometimes.
Gonna run the game again to see if crashes will stop.
I think it must be the new windows 10 update. Hoping that a bug fix update will roll out.
When I load the game up it starts to lag then crashes. This also seems to lag out my PC too.
It wasn't the pistons
CRASHPistons crash my game, also almost tries to bsod my computer
When I load the game up it starts to lag then crashes. This also seems to lag out my PC too.
When I load the game up it starts to lag then crashes. This also seems to lag out my PC too. Related to
MCPE-33072as pistons cause the game to crash.
Pistons crash my game, also almost tries to bsod my computer, MCPE-33072 should be linked as related and not duplicate
Pistons crash my game, alsoalmost tries to bsod my computer, MCPE-33072 should be linked as related and not duplicatePistons crash my game, also freezes windows 10 which some of us have to reboot our computers
@Josh74000MC Feel free to try it, but xbox one is also affected by this issue.
@Josh74000MC Tested the issue again on a xbox one S, results in a crash to dashboard. Can you possibly show the way you are testing the issue?
@Josh74000MC Thanks for clearing that up. There needs to be a block (or other push-able item) in front of the piston to reproduce the issue. The piston alone doesn't seem to cause the crash. It's when something gets pushed or pulled. (In beta release 1.5.0.1)
Josh74000MC No need to, this is caused by a Mac Objective-C library.









Confirmed for 18w02a
Just hit escape then you will get out of the loop.
I hope it gets fixed before 1.13 officially releases.
I'll go see if it also affects the wither.
It doesn't affect the wither lol
This is probably one hilarious glitch in world generation.
Gonna test to see if it's fixed in 18w07a.
Confirmed for 18w07a
Confirmed for 18w07c
Add Windows 10 to the Environment section too.
https://minecraft.net/en-us/download/alternative get the old launcher so it fixes the problems.
confirmed for 18w09a
confirmed for 18w10a
Idk how this bug happened. But this bug is so annoying.
Also there is a mod that brings the new skin API to old versions of minecraft.
I'm trying to move this to the web services
When I held it, it was invisible.
I'm also using an Xbox One S for the beta programme too.
It's an april fools joke too lol
I'm gonna see if version 18w11a is affected
confirmed for 18w11a
I can't even use it on 1.13
Edit: It works, but I had to make my own workaround for it to work.
Just make a work around
This is my work around for 18w11a.
Textures are normal
This screen is looking completely normal.
this sometimes happens, its just a world generation glitch.
I've seen this happen on the legacy Xbox One Edition/ Console Edition before only with the woodland mansion.
On the latest beta build, it seems to be fixed.
Well, since I only play bedrock edition on Xbox One, I think it might not even affect the Xbox One.
Bubble columns aren't added yet.
That's Java Edition, move it over to the java edition section of the bug tracker.
This is also affected on the Xbox One version.
It comes up with this after saying Logging in after a while
I can say that this is confirmed
I've seen a ravine generate like what ravines generate in java edition.
If something like happens on one server, it just times me out on all servers.
This is what shows up on screen.
Plus I'm using a resource pack which only changes the ui and sounds. Even without the resource pack it still happens.
Update your game to 1.2.14.3 as that has new features. Note: you have to join the beta using the insiders hub on windows 10 or xbox one.
On java edition you can enchant a trident with unbreaking and mending.
Oh but after a while it stops and it works just fine then.
Before it would say render distance = 30 chunks, now it says 16 chunks instead of 30. My PC usually supports 30 chunks.
confirmed for 18w14b, on bedrock edition you can actually summon lightning bolts using /summon lightning_bolt
This started happening again after the first 1.13 snapshot came out.
Also confirmed for 18w14b
Yeah, this is what happens on 18w14b, it says unable to summon entity.
We can only do bug reports in english so yeah.
I've encountered this issue on the xbox one beta, but it got fixed.
If you want your loved world back, then reconvert it from the legacy xbox one edition.
I'm also using keyboard and mouse since my pc doesn't support touch controls.
Also I was thinking of upgrading to an NVIDIA Geforce GTX 1080ti Graphics Card so I can get like over 100fps for minecraft on java and so that I can get an 80 chunk reder distance to solve this issue.
Get an Nvidia graphics card, that will help solve the problem.
I think my drivers need updating so that could be why then.
This even happened on xbox one once for me.
This was fixed on 1.2.14.2 on all devices on the beta program
The link should actually be related to my issue as I still get this issue on 1.2.20.1
Confirmed for 18w15a
Yeah I've seen that happen, must be something to do with the water rendering being updated.
I've been getting this issue on both Windows 10 and Xbox One, when I try to connect up my iPad (which is on 1.2.15 aquatic update) and it says outdated client.
confirmed for 18w16a
This doesn't happen with some resource packs though, but this happens with a few though.
I'm hoping that when I update my PC to the latest windows 10 version, that the render distance can get changed over 16.
This is on the newest Windows 10 OS update.
And it also black screens the computer sometimes
I'm gonna see if 1.5.0.1 fixed this crash.
I'm also having this issue when minecraft crashes on the title screen on the newest Windows 10 PC 1803 update.
and still no fix
I have a world with pistons and I believe that causes crashes
This mostly impacts the latest windows 10 update which is 1803
Related to
MCPE-17233Related to
MCPE-17233Duplicate of
MCPE-33049as I reported this before this bug was reportedThis effects Windows 10 PC's a lot as it almost crashes systems with a BSOD saying your pc had a problem and needs to restart.
Don't mark it as future release as you don't have access to them yet. Just put it as 1.5.0.1 or 1.2.13
Blazes are Overpowered lol
@mega_spud can you link
MCPE-33072as related as it almost tries to blue screen a computer with Windows 10Could you link
MCPE-33072toMCPE-33049as related since the game almost tries to blue screen Windows 10 1709 and 1803 on tablets and PC's (mine is an Acer Aspire ES1-571 with intel hd graphics).Duplicate of
MCPE-31673as I reported it on the first aquatic beta.Finally this annoying bug is fixed
I had this happen once when I connected a mouse to my Xbox One S.
I type fast most of the time anyways too.
It should work as intended as shulkers can catch on fire as it isn't a block, it is an entity or mob as we call it.
Gonna test to see if Xbox One is affected since Windows 10 is affected.
Tested on Xbox One S, results were negative, no crash. Next test will be the title screen, results yet again, no crash. So Xbox One S isn't affected by this bug.
Xbox One S isn't affected
I was testing it on a flat world and used pistons, a sticky and normal piston, I used a lever to activate the pistons and it didn't freeze.
Probably something to do with the new way terrain generates with the new biome names.
There probably isn't any pistons in the area.
Duplicate of
MCPE-33072Just go to world options and turn weather cycle off.
We only resolve bugs that are in english, so this is closed as invalid. If you could report this bug in english, then that would make it easier to see what bug is reported.
If all items could be held in the offhand slot, then that would be something ported from java edition.
Duplicate of
MCPE-33072Could you link
MCPE-33049as related since it freezes computers running Windows 10 and some of us even have to reboot our computers.Duplicate of
MCPE-33072Duplicate of
MCPE-33072This is most likely WAI as enderdragons have a large hitbox.
Duplicate of
MCPE-33072Duplicate of
MCPE-33072This is probably working as intended.
Most likely WAI since if it wasn't the case, crashes would occur.
This was fixed since the first update aquatic beta was released.
The title screen panorama needs updating too.
Duplicate of
MCPE-33072as I see the version 1.5.0.1 in the affected versions.Oh when I did the test to see if something would happen the pistons faced west.
I have a feeling its a duplicate of
MCPE-33072duplicate of
MCPE-33072your game is outdated, update to the latest version
This bug might be fixed on 1.4.0 when it comes on app stores in the next few hours.
I've attached an image showing that it didn't show up.
Lemme see if it still updated or not.
it didn't update even though I unenrolled from the beta, I even uninstalled and reinstalled.
still affects 1.5.0.4, title still crashes
Also affects 1.5.0.4, must be something to do with
MCPE-33072but pistons got fixed on 1.5.0.4These crashes are automaticly logged
This also affects Windows 10 on the phase 2 beta.
I wonder if deleting the game files and reinstalling it will fix it.
it worked, no freezing and crashing
this issue is not the same as
MCPE-33223as this crashes the title screen even without a world installed, probably something to do with resource packs being installed.Doesn't affect Xbox One, must be your internet or something. Can't reproduce
also the creeper skin should look like an actual creeper.
To me it looks normal, probably just you then.
the flat world chunks disappearing bug has returned except on infinite worlds with generated structures when going from one dimension to the overworld.
Duplicate of
MCPE-32434this bug used to happen on beta 1.7.3, but got fixed in beta 1.8 which is good as it got annoying.
this is also fixed on 1.6.1
this should be a feature rather than a bug, mob skin packs should be on the market place since everyone wants it.
This is obviously a feature as it is working as intended
Try updating java, maybe that'll fix it
why do you still use windows xp? Its unsupported
It must be a mac issue then, it doesn't affect windows 10 as I've not had an issue with crashes upon loading world, gonna try to see if I can reproduce this on windows 10 and if it does crash, it possibly affects windows, if no crash happens, then windows isn't affected.
Also confirmed on 1.14, seems like this wasn't fixed on macOS