mojira.dev

Impetigo

Assigned

No issues.

Reported

MCPE-146066 World different after updates - renders incorrectly, random weird chunks, not the same Incomplete MCPE-55491 Elytra damage when landing, or clipping trees Incomplete MCPE-50814 Mobs other than Guardians spawning in cleared Ocean Monument area Incomplete MCPE-39257 Pistons destroying first block they come in contact with (cactus, bamboo, etc) Duplicate MCPE-39136 Can't move an uncolored Skulker box in inventory/chests Cannot Reproduce MCPE-28693 Enchanted items in hand have weird texturing Duplicate MCPE-28683 Observer Piston Loop Duplicate MCPE-28595 Piston heads treated as solid blocks when passing in front of Observer Duplicate MCPE-28288 Experience counter too low in GUI Cannot Reproduce MCPE-27973 Game lags and is choppy because of new update Cannot Reproduce MCPE-27595 Parrots move to top of buildings/caves/layer when jumping to shaking them off shoulders Fixed MCPE-27324 Skeleton sound byte has slime bounce at end Cannot Reproduce MCPE-27254 Mob materialized in a fence with high level lighting Cannot Reproduce MCPE-27251 Xbox Lock-ups / Odd behavior while playing BTU (or after) Invalid MCPE-27250 No armor on Skeletons and Zombies Fixed MCPE-26997 Netherwart not naturely spawning in Nether Works As Intended MCPE-26995 Mob spawning rate inconsistent after exploring large chuck of world Cannot Reproduce MCPE-26993 Moving block stacks from inventory to chest/furnace splits stacks back into inventory if partial stack exists in inventory Duplicate MCPE-26992 Zero wolves in world Cannot Reproduce MCPE-26267 Skin cannot be used in multiplayer mode Cannot Reproduce

Comments

@Pig2Creeper Does this bug also completely rewrite the chunk(s) in the area?  It's not just a matter of raising the chunk, but rather rewriting the entire area.  Do you have the issue number so I can follow it?  I didn't see it.  Thanks!

@Pig2Creeper No, I am not using the beta, just the normal release process.  I gave up on the beta years ago because it kept corrupting worlds and ruining game play.

These are the settings selected (all available except the last two).

[media]

Dear @Galaxy_2Alex,

This issue is still happening in 1.16.1 and the ticket in which this was marked as a duplicate specifically stated to call out other similar issues in NEW tickets.  Please reopen this ticket and investigate.  This bug has been happening since at least 1.14 for me.

I reported issues I was having with realms a few days ago when they kept going down.  My report was quickly dismissed as a dupe without any acknowledgement of my frustration or the inconvenience that the realms being down caused. 

Judging by all the comments I'm not alone.  Here's my 2 cents which will probably be ignored by Mojang... again...

  • Mojang needs to stop treating us like garbage and recognize that we are what kept them in business.  We are the people who help make the game better because we spend our time helping for $0 pay.  If we didn't report all the issues then people would have given up on the game years ago because clearly Mojang's QA team can't do jack to find/fix their issues.  

  • I was sent to this issue and told to vote on it, an option which is not available to me.  Why do I need to vote on an issue that is CLEARLY a HUGE problem?!  That's deflecting on Mojang's part to buy them time.  They're hoping that many of us will stop complaining/give up.  That's how they operate.  

  • @[Helper]Greymagic27, there's no point in starting new reports.  They just get marked as duplicates and deleted.  Pointless waste of people's time suggesting we do this.  Not helping the problem!

  • I asked this before and I will ask again... WHO can we contact to get compensation for the multiple issues with Realms?  Mojang does not offer traditional support channels, and I will not sign-up on Twitter just to get ignored.  There must be an email address to contact for this sort of problem. 

  • I am tired of Mojang spending all their time developing Marketplace items and fixing bugs related to 3rd party garbage when they can't even fix their own basic problems.  Realms is a paid service, fix it already!

  • Mojang needs to stop ignoring their angry customers.  You are making the situation worse by ignoring us. 

  • The new Minecraft Dunegons is coming out soon... is this the kind of support we can expect for that?  Maybe a few good campaigns to boycott the new game would be a good idea?  Got lots of free time these days... I refuse to buy this product until Mojang acknowledges their problems and compensates paying users for all the time we've lost thanks to realms crashing, deleting progress, etc. etc.

 

I received 1 bucket of milk, no cake, two buckets missing when trying to craft a cake.

When crafting bread, it consumes all my wheat but returns no bread.

 

Sorry I just realized I typo'd in my first message.  It should have read... "Has this been resolved?  My son and I just spent 3 days prepping a guardian farm only to find guardians are NOT spawning. "

 

I can write up the other part in a separate ticket, but it would be great to know if this has been looked into, and get clarification on the blocks the developers were referring to.

Has this been resolved?  My son and I just spent 3 days prepping a guardian farm only to find now guardians are spawning.  This issue has been unresolved for over a year.  Is anyone looking into it?  The comment about changing the floor doesn't apply to us because we aren't using glass blocks as the floor.  What "different material" were the developers referring to?

 

Also, I had read that mobs were not supposed to be able to spawn inside the template boundaries, but after we hollowed it out skeletons and spiders were spawning (we witnessed it at the very corner of the parameter).  If this is accurate then is this another monument related bug?

No longer happening in current versions.

As of 1.8 Ocelots cannot be tamed, so how can we get the Lion Tamer achievement if it is tied to Ocelots?  Shouldn't it be tied to Cats now?

After experiencing a good amount of play without the problem it suddenly started again and now continues whether I have a map or not in hand or in my inventory.  Sigh... 

Additionally, experienced a power failure afterwards while playing and lost my map file.  Just disappeared from Minecraft.  Had a backup but that was 24 hours old so lost a lot. 😞

Are you using a map in your off-hand?  Try moving it to the inventory bar and see if that resolves the problem.  I was experiencing the same crashes but doing this seems to have fixed it, at least for now.

Follow-up to my previous message...  

After a lot of roaming around without a map in my off-hand I haven't experienced a crash.  If I hold the map in the inventory bar, it seems to work - updating the map, without crashing the game. 

Has anyone else that has experienced the unexpected crashing been using the map in the off-hand?  If so, try using the map non-offhand and see if that works.  Either way, report it here so we know if the map in the off-hand is causing the problem.

@Lee,

This only started happening to me in the 1.6.08 release.  This is the first time I've seen something that affected game play in such a significant way, apart from some terrible lighting issues that used to happen and sometimes pop up from time to time and connectivity problems with other players.

Under the previous beta 1.6.05 I had a world with a file size of over 400MB mostly due to having to travel many many blocks to find a manor house from a map.  That map just corrupted last week and is now unplayable or retrievable.  Really pissed about that because my friend and I had put a lot of time into it.

Explorability is the game and if we can't have unlimited sized worlds that are truly unlimited without crashing the game or corrupting the game file then what's the point of having unlimited?  In theory its great but I don't think the people at Majong/Microsoft have been able to properly crack the recovery of memory when unloading blocks that are no longer in play.  Eventually the game crashes.  I've only experienced a few corrupt game files in my many years of playing, but those are usually the critical ones that hurt.  

Backup regularly if you don't want to lose what you are working on.  It would be great if backups were automatic.  It would also be great if we could access local files to restore them if the cloud versions fail, but that's something they refuse to let players do.  There it is...

Seems to be a memory issue.  Whenever the total mem gets close to 2000 it crashes.  Worse when two players are in the world.  Only started after 1.6.08 update and happens consistently, making exploring and moving more that 500 blocks challenging as the mem starts getting consumed.

Yes, I am still experiencing this issue. It is NOT fixed. I've left two other comments relating to this under different tickets that all related to cloud syncs.

Seems to happen due to larger save files. They don't sync. Smaller ones do. Please resolve ASAP.

This issue is NOT fixed. Tried to migrate my games to a new Xbox and realized that the Cloud sync has not been working for at least a month. Saves are working locally but not syncing to the cloud. Never even had a notice this was happening until I tried to migrate.

Fix this. It is unacceptable to lose months of game play because of a bug that was introduced recently in an update. At this point I cannot migrate large saves because they won't sync to the Cloud.

Allow us a way to export/import the saves to a USB drive like we could on the Xbox 360. This would solve the problem (at least until you fix the cloud sync).

Got the Xbox One X for Xmas and when I went to migrate my games over everything worked fine EXCEPT Minecraft. I can't sync with the Cloud to transfer the games. Gives me an error about the other Xbox is still trying to sync.

This seems like a size issue as the smaller worlds were backed up. I even copied the larger worlds just to see if they would sync to the cloud and no go. One larger world that was on the cloud corrupted on the new Xbox One X.

I did a lot of reading on the Internet about this and Microsoft blames Mojang and Mojang blames Xbox. The passing of the blame game. There are multiple versions of this issue in the database. Come on Mojang/Microsoft.. fix your game!

Still present in 1.2.6.2 beta. 😞

Almost 3 months since I reported this issue and it is still happening in the latest versions. 😞

Whenever I have challenged Minecraft "behaviors" or the like, I am pointed to the Wiki. Whether it is user-editable or not, if Minecraft representatives are going to use it as their rule book, then it works both ways.

The piston head is actually not a block, and I disagree that the "All other block / block state changes" Wiki entry actually applies. If a mob moves into a block, it does not trigger the observer. The piston head isn't any different. It's a temporary intrusion and should be treated as such. When sugarcane grows into the block it is there for a longer period of time to potentially always there. The piston is passing through, so to speak, and should not be treated the same way.

Besides, if the piston head is moving into a block that already has an object in it, then it should not re-trigger the observer as the state of the block is not changing from empty to full. It's going from full to full. It's not until the piston head has left the block that a change of state actually takes place, whether its changing the state of a block like sugarcane, or moving a block out of the current clock.

Ultimately, the behavior I am describing just makes the Observer a better feature of Minecraft. It makes for much simpler devices that are simply not possible with the changed behavior in the latest release. It is extremely frustrating having to rebuild every time someone at Minecraft decides its easier to fix other problems by changing behaviors in something else.