A workaround is to set it to minecraft:air
then the new permutation in the same tick.
Looking at the json files, the experiment does the following changes to the minecraft:behavior.float_wander
goal:
"minecraft:behavior.float_wander": {
"priority": 2,
- "must_reach": true
+ "must_reach": true,
+ "random_reselect": true,
+ "float_duration": [ 2, 7 ]
},
This is also a parity issue. Firefly bushes do generate in mangrove swamps in Bedrock Edition, at least near bodies of water.
When attempting to log in, while it may appear you're on the same login page at Minecraft.net, in actuality the following query string is added:
?error=InternalServerError&error_description=Some%2bexception%2bhappened#state=login
When clicking login again, it adds the same query string again. In the query string you can see an error description, but it's quite vague. Additionally, sisu.xboxlive.com returns 503.
@Blobs2 same for chicken, which are affected by looting.
There's more information regarding this on this Purpur issue, (Purpur is a server software that allows this occur) but this is should now be possible in vanilla using /ride
which was added in 1.19.3. I haven't tested if this is still an issue, but if it is this should be reopened.
Blocking the entire message works in 1.19.3, but staring out words in the message does not.
It appears this is caused by grass_color
being defined in cherry_grove.json
. Below is a snippet of the effects
object in said file:
"effects": {
"fog_color": 12638463,
"foliage_color": 11983713,
"grass_color": 11983713,
"mood_sound": {
"block_search_extent": 8,
"offset": 2.0,
"sound": "minecraft:ambient.cave",
"tick_delay": 6000
},
"music": {
"max_delay": 24000,
"min_delay": 12000,
"replace_current_music": false,
"sound": "minecraft:music.overworld.cherry_grove"
},
"sky_color": 8103167,
"water_color": 6141935,
"water_fog_color": 6141935
},
As you can see, grass_color
, which overrides the normal behavior of grass color being selected on the colormap due to temperature and downfall, is set to 11983713
, which when converted to hexadecimal is {color:#B6DB61}⬤#B6DB61{color}
. This is probably intended as it makes the color more pretty than it would normally be. You can override this using a datapack.
Here is FletchingTableBlock.java
. Note that this is an extension of CraftingTableBlock.java
. A solution would be to just make it an extension of Block.java
instead.
package net.minecraft.world.level.block;import net.minecraft.core.BlockPos;
import net.minecraft.world.InteractionHand;
import net.minecraft.world.InteractionResult;
import net.minecraft.world.entity.player.Player;
import net.minecraft.world.level.Level;
import net.minecraft.world.level.block.state.BlockBehaviour;
import net.minecraft.world.level.block.state.BlockState;
import net.minecraft.world.phys.BlockHitResult;public class FletchingTableBlock extends CraftingTableBlock {
protected FletchingTableBlock(BlockBehaviour.Properties paramProperties) {
super(paramProperties);
}
public InteractionResult use(BlockState paramBlockState, Level paramLevel, BlockPos paramBlockPos, Player paramPlayer, InteractionHand paramInteractionHand, BlockHitResult paramBlockHitResult) {
return InteractionResult.PASS;
}
}
Invalid, this is a feature request.
This is working as intended.
Possible solution can be converting the NBT in the item to use BlockStateTag
.
@[Mojang] Moesh that issue is regarding it being in the delete item slot, this one is regarding it being in all creative tabs. They are two separate issues.
Copper Horn was removed in beta 1.19.0.24, therefore this bug should be resolved.
Requesting this to be reopened as per @[Helper] ampolive's point.
I think this is partially intentional. I'm pretty sure things like different enchants being ignored is intentional, but not things like different potions. If so, this could be resolved by adding an item tag like allay_dont_ignore_nbt
that could be added to things like potions and etc, or maybe make specific NBT tags be ignored by allay, whilst not ignoring others. For example, allays ignoring Enchantments
tag but not Potion
tag.
I think this is Works As Intended because of the new can_summon
block state preventing the placed shriekers from spawning wardens. I could be wrong, however if this is working as intended, then MC-249470 should be changed to fixed.
Attached fixed texture.
Wrong report my bad.