Lyndsbal
- Lyndsbal
- JIRAUSER746888
- Europe/Stockholm
- Yes
- No
MCPE-167408
REALMS-12209
After fighting an ominous wave of mobs from a trial spawner placed by a player, the trial spawner appears to lose its mob data and not function after its cooldown ends.
Step to Reproduce:
1. Place a trial spawner in creative mode and use a spawn egg (any) to tag a mob to it
2. Fight an ominous battle with the spawner
3. Wait until cooldown ends for the spawner to be active againExpected Result:
The spawner will return to being a waiting or active spawner with the mob data still attachedObserved Result:
The spawner appears to be empty and has no mob data yet still appears to be active
After fighting an ominous wave of mobs from a trial spawner placed by a player, the trial spawner appears to lose its mob data and not function after its cooldown ends.
Step to Reproduce:
1. Place a trial spawner in creative mode and use a spawn egg (any) to tag a mob to it
2. Fight an ominous battle with the spawner
3. Wait until cooldown ends for the spawner to be active againExpected Result:
The spawner will return to being a waiting or active spawner with the mob data still attachedObserved Result:
The spawner appears to be empty and has no mob data yet still appears to be activeAfter fighting an ominous wave of mobs from a trial spawner placed by a player, the trial spawner appears to lose its mob data and not function after its cooldown ends.
Step to Reproduce:
1. Place a trial spawner in creative mode and use a spawn egg (any) to tag a mob to it
2. Fight an ominous battle with the spawner
3. Wait until cooldown ends for the spawner to be active againExpected Result:
The spawner will return to being a waiting or active spawner with the mob data still attached
*
Observed Result:*
The spawner appears to be empty and has no mob data yet still appears to be active
After fighting an ominous wave of mobs from a trial spawner placed by a player, the trial spawner appears to lose its mob data and not function after its cooldown ends.
Step to Reproduce:
1. Place a trial spawner in creative mode and use a spawn egg (any) to tag a mob to it
2. Fight an ominous battle with the spawner
3. Wait until cooldown ends for the spawner to be active againExpected Result:
The spawner will return to being a waiting or active spawner with the mob data still attached
*Observed Result:*
The spawner appears to be empty and has no mob data yet still appears to be activeAfter fighting an ominous wave of mobs from a trial spawner placed by a player, the trial spawner appears to lose its mob data and not function after its cooldown ends.
Step to Reproduce:
1. Place a trial spawner in creative mode and use a spawn egg (any) to tag a mob to it
2. Fight an ominous battle with the spawner
3. Wait until cooldown ends for the spawner to be active againExpected Result:
The spawner will return to being a waiting or active spawner with the mob data still attachedObserved Result:
The spawner appears to be empty and has no mob data yet still appears to be active
Turning player-placedtrialspawnersinto ominous ones will delete the mob data insideafter cooldownPlayer-Placed Trial Spawners corrupted after cooldown
After fighting a
n ominouswave of mobs from a trial spawner placed by a player, the trial spawner appears to lose its mob data and not function after its cooldown ends.Step to Reproduce:
1. Place a trial spawner in creative mode and use a spawn egg (any) to tag a mob to it
2. Fight an ominousbattle with the spawner
3. Wait until cooldown ends for the spawner to be active againExpected Result:
The spawner will return to being a waiting or active spawner with the mob data still attachedObserved Result:
The spawner appears to be empty and has no mob data yet still appears to be active
This issue was resolved with the update to the related issue that released today (referring to
MCPE-185960) This can be closed, the fix also resolved this issue.
Water mobs can't be placed in water buckets on realms. I have tested this with tadpoles and axolotls on multiple worlds in my realm, it works as intended in the regular game.
Steps to reproduce:
1. Get an axolotl bucket or tadpole bucket
2. Place down the mob, preferably in a hole so it can be contained
3. Collect the water back in your bucket
4. Attempt to pick up the mob with your water bucketExpected Result:
Mob is picked up with water bucket
*Observed Result:*
Water bucket doesn't collect the mob no matter how many times you tryWater mobs can't be placed in water buckets on realms. I have tested this with tadpoles and axolotls on multiple worlds in my realm, it works as intended in the regular game.
Steps to reproduce:
1. Get an axolotl bucket or tadpole bucket
2. Place down the mob, preferably in a hole so it can be contained
3. Collect the water back in your bucket
4. Attempt to pick up the mob with your water bucketExpected Result:
Mob is picked up with water bucketObserved Result:
Water bucket doesn't collect the mob no matter how many times you try
Lyndsbal, that is currently tracked in MCPE-178759.
This is happening on windows where opening the realms stories feed will occasionally crash the game, but not upon opening the realm. Should I create a separate ticket for this?
Hi, I am suffering a similar issue in version 1.21.21. I have loads of commands on my world (not a server) and the tick speed appears to be cut in half. Breaking blocks also has a small delay as well.
An update: I found that it actually was a command block causing lag, a very specific one; it was a repeat command that tested for players that had one of a specific tag and none of another. Not sure if that's supposed to be causing so much lag.
MCPE-185960relates to the issue but does not clearly match this issue, since it has to do with ominous events and player-placed spawners.MCPE-185960is related to naturally-generated spawners that were reassigned a mob. I was not seeing this issue with non-ominous fights with player-placed trial spawners.Does this happen without the texture pack?
Still an issue in release 1.21.44
This issue is still occuring in 1.21.51 and needs to be reopened. Still happening in my worlds
As mentioned in the related issue this is still happening in 1.21.51