Posted on Leave a comment

Bedrock: 1.19.10

This is the latest patch notes for the official release of 1.19.10 for “Bedrock” versions of Minecraft.  As you can quickly see below Allay Duplication has been added!  What else has changed?  Let us know what your favorite part of this update was. 

New Features

Allay Duplication

  • When an Allay hears a Jukebox playing, it will do a dance animation
  • If the Jukebox stops playing, or if the Allay gets too far away from the Jukebox, it will stop dancing
  • If the Allay is given an Amethyst Shard while dancing, it will play a small amethyst sound, make a heart, and duplicate into another Allay
  • After duplication, both Allays will have a 5-minute cooldown before being able to duplicate again

Changes

  • Expanded the ‘/locate’ command into locate structure and locate biome
  • The Trader Llama now has its own spawn egg
  • Added the player’s cause of death to the death screen
  • Music is now included in the game files on iOS, so players no longer need to download the music pack from the Marketplace
  • Added Bluetooth mouse and keyboard support on iOS

Fixes

Performance / Stability

  • Fixed a crash that could occur when Boats are unloaded from the world
  • Fixed a crash that could occur when a Wither is loaded into the world
  • Fixed a crash that could occur in multiplayer when a player left the game while changing dimension
  • Fixed a crash that could occur when a Fishing Rod was cast through dimension-changing portals (MCPE-154161)
  • Fixed a crash that could occur when players died while affected by Withering
  • The game no longer crashes when entering the Coin Starter Bundle screen
  • Loading a world no longer takes a very long time when having the Holiday Creator Features experimental toggle enabled

Gameplay

  • Players are no longer pushed by Doors as they close (MCPE-154734)
  • Items now stack properly in the offhand when inventory is full (MCPE-34959)
  • Equipping items in armor slots through the inventory screen now produces sounds (MCPE-46939)
  • Players can now hear each other equipping items in armor slots
  • Fixed a bug where players could take fall damage when walking around on Scaffolding at certain heights (even when not falling) (MCPE-154779)
  • Fixed a bug that reset the player’s vertical camera angle upon entering a Boat (MCPE-152762)
  • Advanced Pick Block now copies the items inside when used on a Boat with Chest (MCPE-153410)
  • Resistance effect is no longer one level weaker than it should be (MCPE-156012)
  • Haste I will now properly increase the player’s mining speed (MCPE-102237)
  • Conduit Power I now grants the effect of Haste I instead of Haste II
  • Fixed an issue with extra health from Health Boost not persisting after exiting the world (MCPE-153504)
  • Container entities like Boat with Chest can now be opened on mobile devices without crouching if all the seats are occupied
  • The player no longer endlessly jumps after entering a Boat while holding down the jump button (MCPE-155774)
  • Fixed a bug causing player hitboxes to not reset if they die while swimming (MCPE-155232)
  • Fixed an issue where new users given Operator permissions by default were not able to use operator commands
  • Fixed an issue where worlds that gave Operator permissions to new players only gave Member permissions
  • Removed the Vanilla Experiment and Wild Experiment toggles, since they no longer have any active experimental content

World Generation

  • Fixed a bug where upgrading old worlds could result in water columns below y=0
  • Mangrove Swamps are now denser to more closely match Java Edition (MCPE-153748)
    • There is still work to be done to increase the density of Mangrove trees in water
  • Grass blocks in Mangrove Swamps now have Dirt blocks underneath them (MCPE-155414)
  • Clay patches now correctly generate in Mangrove Swamps
  • Campground structures now generate correctly in Ancient Cities (MCPE-156084)
  • Updated Ancient City structures to match Java Edition
  • Sculk Vein feature can now generate within the same height span as the Sculk Patch feature (MCPE-156074)

Mobs

  • Fixed issues with mobs disappearing after going through Nether portals (MCPE-155678)
  • Fixed a bug causing tamed mobs to disappear when they go through a Nether portal in a multiplayer world (MCPE-88322)
  • Villagers now spawn as Swamp Villagers in Mangrove Swamp (MCPE-153731)
  • Villagers will now flee from Zoglins (MCPE-74974)
  • Parrots are once again poisoned by Cookies (MCPE-151671)
  • The Trader Llama now has the correct name displayed when opening its inventory (MCPE-47165)
  • Fixed a bug that prevented Trader Llamas from becoming aggressive towards entities that attack the Wandering Trader (MCPE-94996)
  • The Wandering Trader will now flee from Zoglins
  • The Wandering Trader will now drink Milk to clear its Invisibility effect (MCPE-44605)
  • Fixed a bug causing riding passengers to stop riding when reloaded if they were across chunk borders
  • Breaking a Boat with Chest or Minecart with Chest will now anger nearby Piglins (MCPE-153393)
  • Fixed entities disappearing when importing worlds converted from legacy console editions of Minecraft
  • Fixed a bug where Slimes would no longer spawn in flat worlds made before 1.18 (MCPE-119396)
  • Fixed a bug where failed Slime spawn attempts would reduce the spawning rates of other mobs (MCPE-153502)
  • Wither now breaks Obsidian when attacked by players (MCPE-64630)
  • Wither no longer breaks surrounding blocks after a shorter delay than intended after being attacked
  • Entities entering Nether portals exit in the same relative position and rotation to the portal (MCPE-139835)
  • Edited health points of Cod, Pufferfish, Salmon, and Tropical fish to be 3, matching Java Edition
  • Shulker projectile now adds effect “Levitation” instead of “Levitation II” on hit

Frog

  • Tadpoles now grow up into Temperate Frog in Meadow, and into Cold Frog in Deep Dark
  • Frogs no longer lay Frogspawn on shallow, flowing water (MCPE-152559)

Allay

  • Allays can now follow players through Nether portals (MCPE-155678)
  • Taking a stackable item from an Allay now correctly adds this item to existing stacks (MCPE-153540)
  • Taking a stackable item from an Allay no longer causes item duplication
  • Allay pickup range is changed from 64 to 32 blocks to match Java Edition (MCPE-251766)
  • Allay now retains information about the vibration it is reacting to through save and load
  • Items held by Allays now glow in darkness (MCPE-153533)

Warden

  • Warden can now path through lava (MCPE-153582)
  • Warden can now pass through water (MCPE-153602)
  • Warden is no longer pushable while emerging or digging
  • If the Warden is in liquid when attempting to despawn, it will not do the digging animation, instead, it will just despawn without any animation/sound (MCPE-155706)
  • Warden now always chases a nuisance after it roars at it
  • Warden now increases its anger towards an attacking nuisance by 100 anger for each attack
  • There are no longer graphical artifacts from the Warden’s emerge or dig particle effects (MCPE-153580)
  • Warden’s hurt animation no longer differs between Bedrock Edition and Java Edition (MCPE-153967)
  • Wardens can now spawn on more types of non-full blocks, such as upper Slabs, Redstone Dust, Snow layers, Buttons, and Tripwires (MCPE-155821)
    • Known limitations: The current solution doesn’t allow spawning on some types of blocks such as Leaves and lower Slabs
  • Warden now retains information about the vibration it is reacting to through save and load
  • Warden’s Sonic Boom attack now bypasses enchantment damage reduction such as Protection (MCPE-156282)

Blocks

  • Nether Sprouts and Fungi can now be placed on Mud and Muddy Mangrove Roots
  • Froglight walk sound volume is now more similar to other blocks’ walk sound volume (MCPE-154879)
  • Mob Spawners now drop XP only when destroyed by a Pickaxe
  • Fixed a visual issue where Barrier Blocks would show a red texture/overlay when being viewed from the inside (MCPE-98938)
  • Renamed “Flowered Azalea Leaves” to “Flowering Azalea Leaves”
  • Lapis Lazuli Block is now named Block of Lapis Lazuli (MCPE-105452)
  • Cut Copper Slab and its variants can now be placed on the top half of a block on the first attempt (MCPE-154302)
  • Campfires can now provide full-faced bottom support to other blocks
  • Lecterns can now provide full-faced bottom support to other blocks
  • Weeping Vines can now be placed underneath all blocks which can provide full-faced bottom support (MCPE-153083MCPE-104717)
  • Fixed an issue where Carved Pumpkins launched from Dispensers weren’t equipping to nearby mobs
  • Bell now rings when hit by any type of projectile
  • Hit sound is now played when Amethyst block is hit by projectiles (MCPE-137090)
  • Amethyst Clusters are no longer destroyed if attached to a Sculk Sensor
  • Structure Blocks can no longer be waterlogged (MCPE-59566)

Mangrove and Mud Blocks

  • Muddy Mangrove Roots are now broken fastest with a Shovel (MCPE-153710)
  • Mangrove Roots are now broken fastest with an Axe (MCPE-155606)
  • Mangrove Leaf blocks are no longer collected into different stacks when using Silk Touch (MCPE-153786)
  • Mangrove Leaves are no longer collected into separate stacks when using Shears
  • Stripped Mangrove Logs now craft into Stripped Mangrove Wood instead of Mangrove Wood (MCPE-155365)
  • Mangrove Log is now included in Bonus Chest loot tables (MCPE-153924)
  • Mangrove Propagules are no longer blocked to grow by Leaves (MCPE-154928)
  • Mangrove Propagules now render correctly when placed in Flower Pots (MCPE-155528)
  • Mangrove Propagule now uses grass sounds
  • Mangrove Propagule is no longer destroyed by flowing water (MCPE-154011)
  • Mangrove Signs now use Mangrove Plank textures for breaking particles (MCPE-156568)
  • Mangrove Propagule is now placed at a random offset (MCPE-153735)
  • Iron Bars and Glass Panes now connect to Mangrove Roots (MCPE-153871)
  • Sweet Berry Bush can now be planted on Mud, Muddy Mangrove Roots, and Rooted Dirt (MCPE-153916)

Sculk Blocks

  • A Sculk Vein block now drops as many items as its number of faces when mined with Silk Touch
  • Sculk Catalyst can now spread Sculk through Mud and Muddy Mangrove Roots (MCPE-153924)
  • When a mob dies in the proximity of multiple Sculk Catalysts, only the closest one will bloom
  • The “It Spreads” achievement is no longer unlocked when a Sculk Catalysts blooms after the death of a mob that carries no XP
  • Sculk Shriekers now scan for Wardens in a box with a side of 48 blocks, not 96 blocks
  • Sculk Shriekers now apply the Darkness effect to players with threat level 3 or 4
  • Sculk Shriekers now detect players when riding any type of entity (MCPE-153814)
  • Sculk Shriekers now activate repeatedly while players are standing on them (50%) (MCPE-153818)
  • Sculk Shriekers now implicate the player that provokes it from afar
  • Sculk Shrieker now retains information about the vibration it is reacting to through save and load
  • A Sculk Shrieker can no longer summon a Warden underwater (MCPE-153791)
  • Sculk Shrieker particles are now correctly rendered from behind (MCPE-153591)
  • Sculk Shrieker now detects players when riding all types of entities, including Striders, Skeleton Horses, Pigs, and Llamas (MCPE-153814)
  • The Sculk Sensor now correctly detects when a Big Dripleaf block changes its tilting state (MCPE-153115)
  • The Sculk Sensor now correctly detects when a Grass, Grass Path, Dirt, Coarse Dirt, or Rooted Dirt Block is tilled with a Hoe (MCPE-153734)
  • Sculk Sensors cannot detect a player equipping a handheld item anymore (MCPE-153971)
  • Sculk Sensors are now consistently occluded by Wool, no matter which direction vibrations come from (MCPE-153815)
  • Sculk Sensors cannot detect a Player placing, destroying, walking, and falling on Carpets anymore (MCPE-153956)
  • Sculk Sensors cannot detect Wool and Carpets hitting the ground in item form anymore (MCPE-152998)
  • Sculk Sensor now retains information about the vibration it is reacting to through save and load
  • Sculk Sensors can now detect a Boat with Chest having its Chest opened and closed (MCPE-156199)
  • Sculk Sensors give out a Redstone Signal of 12 and 13 when detecting fluids being placed and picked up, respectively
  • Sculk Sensors can now detect a player drinking Milk
  • Sculk Sensors can now detect a player picking up Powder Snow via Bucket (MCPE-153817)
  • Sculk Sensors cannot detect an entity jumping on Wool covered by Sculk Veins anymore
  • Sculk Sensors cannot detect an entity standing still in Scaffolding anymore (MCPE-118454)
  • Sculk Sensors can now detect an entity moving in Powder Snow and cobwebs (MCPE-153105)
  • Sculk Sensors can now detect items being placed in the hand of an Armor Stand
  • Sculk Sensors cannot detect any more items being equipped on mobs at spawn time

Items

  • Goat Horn now correctly drops when Goats ram Mangrove Logs (MCPE-154912)
  • Goat Horn now has the same sound for the “Call” variant as Java Edition (MCPE-154886)
  • The last sound for Goat Horn was renamed from “Resist” to “Dream” to match Java Edition (MCPE-155059)
  • Fixed Bottles not usable on water and Boats not placeable on water (MCPE-156451)
  • Wooden tools can now be repaired using Mangrove Planks, Crimson Planks, and Warped Planks (MCPE-153808)
  • Smelting Gold and Iron tools and weapons into Nuggets now rewards XP (MCPE-136467)
  • Shields that are disabled when struck by an Axe or by Warden now play a broken item sound (MCPE-153315)
  • Items in off-hand are once again rendered properly
  • Pufferfish now gives Poison II effect instead of Poison IV when consumed (MCPE-105392)

Graphical

  • Players now have their hands back when they are holding a Map when they have one item in the offhand and one in the main hand. Curious how they held it without hands… (MCPE-100259)
  • Darkness effect now works in the Nether and the End dimensions
  • Lava and Powder Snow fogs now take priority over Darkness and Blindness fogs (MCPE-154928)
  • Fixed animation system issues for players in split-screen situations
    • Fixed Crossbow, Trident, and Shield rendering for other players (MCPE-118528)
    • Fixed split-screen render position when sleeping in a Bed (MCPE-65705)
    • Fixed Elytra’s animation during split-screen
    • Fix the attached Lead position when the second player is using a first-person perspective
  • Fixed an issue with reloading RTX worlds that caused DX11 to be used, resulting in a black screen (MCPE-152645)
  • Fog settings with a negative fog start will no longer cause UI elements to get tinted by fog color
  • Fixed a visual bug where liquids could have unexpected heights in the corners depending on diagonally-adjacent blocks (MCPE-152995)
  • Fixed terrain flickering in and out of the fog when playing on Nintendo Switch
  • Fixed an issue with underground light sources being generated when breaking or placing a block (MCPE-155808)

User Interface

  • Fixed touch control’s right d-pad button not working when the d-pad area overlapped with the hotbar area (MCPE-156103)
  • Infinite loading should no longer occur when entering the Dressing Room (MCPE-156209)
  • Fixed up some of the text for the emote wheel so it would fit inside the box
  • Added settings to change the duration of notifications
  • Friendly Fire game rule toggle has been moved to the Multiplayer tab on the Create New World screen
  • On mobile devices, the experience bar is now centered over the entire length of the hotbar, including the ellipsis at the end
  • Fixed issue where info and buttons did not appear for downloaded skin packs (MCPE-152216)
  • On the death screen in Pocket UI, moved the Main Menu button to the top navigation to avoid accidental button presses when dying mid-fight
  • Fixed incorrect positioning of the “Select (A)” tip on the death screen when using a gamepad controller
  • Added correct death message when dying from Sweet Berry Bush (MCPE-103583)
  • Added a minimum size to yellow splash screen text
  • Fixed a typo in the notification duration label for Accessibility Settings (MCPE-156901)
  • Fixed “Crafting” word above the crafting slots in the inventory on Classic UI (MCPE-152697)
  • Worlds created with a template will now always disable achievements
  • Fixed an issue where items could be dropped by clicking in the dark gray area of the player inventory when using Furnace, Blast Furnace, Smoker, Enchanting Table, Grindstone, Brewing Stand, Anvil, Beacon, Smithing Table, Loom, Cartography Table, and Stone Cutter
  • Fixed an issue where some paragraphs of text in modals were misaligned (MCPE-153789)
  • Container screen cursor can now be controlled by the wireless controller touchpad on PlayStation 4 (MCPE-106320)
  • Fixed a typo in the notification duration label for Accessibility Settings (MCPE-156901)
  • Player can now continuously jump while holding down the jump button (MCPE-117045)
  • Player can now descend from the top of scaffolding with the new touch controls (MCPE-154309)

Realms

  • Realms players can once again post screenshots to their Realms Feeds and comment on Realms Feed posts
  • Fixed a bug wherein failure to join a Realm gave misleading or incorrect error messages (REALMS-7242)
  • Different types of Realms subscriptions will always show the “Manage” button on the Settings > Subscriptions page if they are manageable on the current platform
  • Added a popup to notify players on Google Play about holds on Realms subscriptions
  • Clicking “Play on Realm” from World Settings now copies the world’s game rules to the Realm
  • Due to recent changes, packs and worlds with version 1.19-level custom, experimental GameTest Framework JavaScript is rejected at the time of upload within Realms
    • We’re working on more infrastructure to fully support worlds and packs with script in Realms, but in the meanwhile, packs with the experimental script are not supported in Realms
    • Note that the recently released Spellcraft Marketplace map, which uses a script, is also not supported within Realms

Spectator Mode (Experimental)

  • Players in Spectator mode no longer get effects from gameplay
  • Players in Spectator mode no longer trigger raids while in Village with Bad Omen effect
  • While in Spectator Mode, actors in other chunks are no longer culled away
  • Players in Spectator mode can now breathe anywhere
  • Players in Spectator mode can no longer be pushed by Pistons
  • Spectators will be ignored for sleeping rules to skip the night
  • Moving around as a Spectator will no longer affect a player’s hunger level
  • Spectators no longer broadcast self-made sounds; such as footsteps, climbing, watersplash, etc.
  • Player’s insomnia timer stops ticking once the player switches to Spectator mode
  • Render only head for players in Spectator mode
  • Render players in Spectator semi-transparently
  • Projectiles such as Arrows, Tridents, and Fireballs will now shoot through Spectators
  • Spectators playing with a gamepad no longer are shown unusable tooltips

Technical Updates

Updated Add-On Template Packs

  • Updated Add-On templates for 1.19.10 with new resources, behaviors, and documentation, are available to download at aka.ms/MCAddonPacks

General

  • Fixed a crash that could occur if a mob had the flocking component
  • Fixed a bug where Soul Campfire was using the wrong tag, resulting in cases where some custom recipes for Campfires were not working correctly (MCPE-98305)
  • Fixed interaction priority when using a Bucket on a waterlogged and interactable block, eg. Lever (MCPE-154221)
  • The Trader Llama is now its dedicated mob instead of being a normal Llama with specific component groups
  • Ensured content errors are not ignored when loading entity JSON schemas with invalid value types for the following fields: The “Runtime_Identifier”, “Is_Spawnable” and “Is_Summonable” fields for “description”, the “component_groups” field, and the “event” field for “events” (MCPE-151381)

Commands

  • Fixed an issue where, after 1.18.30, teleporting an entity to a chunk that has not been loaded since before 1.18.30 would result in the loss of that entity
  • Fixed an issue in the teleport command where a “facing” argument would calculate an incorrect vertical orientation (MCPE-144870)
  • Teleporting entities into unloaded chunks no longer deletes them
  • Autocomplete suggestions now show only valid parameters
  • New execute command functionality is now available via the “Upcoming Creator Features” experimental toggle
  • Chests with loot tables no longer drop items when removed with ‘/clone’, ‘/fill’ or ‘/setblock’ (MCPE-151876)
  • Fixed an issue where entities loaded by Structure Blocks and commands would cause the despawn of the original mob used to save the structure and any mobs from previous loads of the structure (MCPE-155036)
  • Pillagers and Vindicator Captains spawned with commands are once again hostile by default (MCPE-116971)

Blocks

  • Renamed minecraft:block_collision block component to minecraft:collision_box
  • Renamed the minecraft:block_light_filter component to minecraft:light_dampening and added appropriate versioning
  • Renamed the ‘part visibility’ component’s field ‘rules’ to ‘conditions’ and added appropriate versioning 
  • Renamed the ‘crafting_table’ component’s field ‘custom_description’ to ‘table_name’ and added appropriate versioning
  • Renamed the ‘minecraft:block_light_filter’ component to ‘minecraft:light_dampening’
  • Renamed the ‘part visibility’ component’s field ‘rules’ to ‘conditions’
  • Renamed the ‘crafting_table’ component’s field ‘custom_description’ to ‘table_name’
  • Blocks with block_light_absorption’ component of value 16 no longer fail to load
  • Renamed the component ‘minecraft:ticking’ to ‘minecraft:queued_ticking’
  • Renamed the ‘minecraft:ticking’ component’s field ‘range’ to ‘interval_range’, which is now described in ticks rather than seconds
  • Renamed the ‘minecraft:flammable’ block component fields ‘flame_odds’ and ‘burn_odds’ to ‘catch_chance_modifier’ and ‘destroy_chance_modifier’
  • Added ability to set ‘minecraft:flammable’ block component using booleans for default flammable or nonflammable values
  • Updated documentation for minecraft:map_color and minecraft:material_instances
  • Cake blocks now emit Block_Change game events when slices are eaten

Items

  • Fixed ‘minecraft:block_placer’ item component to correctly trigger block component ‘minecraft:on_player_placing’
  • Hunger Exhaustion component now uses new correct default values (MCPE-154238)
    • Please note, add-on packs that alter ‘player.json’ may need to ensure that the player saturation rate is set correctly to match the default values if required

Actors

  • Added ‘minecraft:drink_milk’ behavior, which allows a mob to drink Milk based on specified environmental conditions
  • Actor properties will now save and load correctly across multiple clients and entities
  • Direction facing will now be preserved through a transformation from one actor type to another
  • Fixed an issue where projectiles with an offset weren’t spawned based on the player’s rotation (MCPE-153880)
  • Fixed a bug that prevented the owner of the ‘minecraft:angry’ component from broadcasting anger to its friends if it has no target. A mob with this component will now be able to get angry if it both does not have a target and the component’s ‘filters’ list is empty (MCPE-94996)
  • Mobs can now be hit by a projectile when their hitboxes are outside the mob’s bounds
  • Replaced ‘values’ field with ‘range’ field, which only supports array JSON types. Added required ‘type’ JSON field for actor properties with supported values ‘int’‘float’‘bool’, and ‘enum’. The ‘default’ and ‘range’ fields on the property must match the type specified in the new ‘type’ field

Graphical

  • Fog setting with a negative fog start will no longer cause flames on the player model in UI to get tainted by fog color
  • “particles_blend” material is no longer culled
  • Fixed the issue where water fog expanding speed did not match the value specified in ‘midPercentage’ field (MCPE-153864)
  • Fixed issue where underwater fog transition between biomes is not smooth while affected by eye adapting effect

GameTest Framework (Experimental)

  • Added argument keepVelocity: bool to functions teleport and teleportFacing – If true, preserves velocity when teleporting the Entity
  • The /script profiler command now includes native API calls its trace call stacks
Posted on Leave a comment

JAVA: 1.19.1 Pre-Release 4

Today’s latest pre-release has to do with some changes to chat messages and fixes regarding the state of the messages on whether they are secure or not.

Technical Changes in 1.19.1 Pre-Release 4

  • Custom servers can hide player chat messages from display via a new network packet
    • This does not delete player chat messages from chat logs
  • Insecure chat messages logged in the server are prefixed with a [Not Secure] tag
  • The order of chat messages is now cryptographically verified
    • This will be used for validating the context of chat messages for Player Reports

Fixed Bugs in 1.19.1 Pre-Release 4

  • MC-253743 – The server console doesn’t state if chat messages aren’t secure or have been modified
  • MC-253813 – Chat commands with entity selectors often reported as “This message is not secure”
Posted on Leave a comment

Mojang’s Response to Concerns for Player Reporting

There has been a lot of contention and people throwing out wild ideas of what they believe the Player Report system does.  Mojang has created two separate articles expanding on how the system works and I’ll be condensing them below. 

Keep in mind, that these are not my opinions, the Minecraft Forum is not owned or influenced by Mojang Studios or Microsoft.  Some responses are not a direct copy and paste and have been shortened.  To read the entire responses in full these are the links to the two articles mentioned that my own article is covering.

Addressing Player Chat Reporting Tool
Minecraft: Java Edition Player Reporting FAQ


Common Misconceptions, Answered Questions, and Information

What technical measures are there to prevent messages from being forged?

1.19 introduced cryptographically signed chat, which prevents the forging and/or rearranging of player messages. Any message that has been forged will be flagged for our investigators. 

Why has this feature been implemented?

This feature has been added to ensure the safety of players during online interactions.  These safeguards have been put in place to keep their online service safe and welcoming to everyone.

Can I get banned for swearing/profanity?  

No.  While the first iteration of the Player Reporting feature did contain the category to report someone for profanity it has since been removed.  Keep in mind, that hate speech, threatening others, bullying, sexual solicitation,  or harassing others is not permitted. 

Will you ban people from talking about suicide?

No.  There is a difference between discussing a topic and suggesting someone do this or stating that they plan to do this themselves.  The Player Report feature used here is to attempt to provide players in this crisis situation with support and resources.

Does this affect private servers? 

Yes. While private servers are not run by Mojang, each server still has to accept and follow the EULA, Commercial Usage Guidelines, and Community Standards.

Why does Mojang need to be involved in third-party server player reporting?  Why is this feature not only applied to Realms?

All players are bound by the Community Guidelines and not all servers provide a way to report or resolve these violations.  Server Owners can still moderate their own servers the same as they always have.  Not all server owners have time or resources to review their own server reports.

Can I get banned for what I say in singleplayer?

No.  This feature is only available in multiplayer.

Is my online chat being monitored?

No.

Are you Using Bots to moderate my chat?

No.  All reports are player made.  There is no AI scanning your chat logs.

Is this a player-censoring chat filter?

No.  This system is not blocking messages from being sent.

Can someone create a report without evidence?

No.  When creating a report you must select the offending chat messages and category to submit.

Can my messages be taken out of context?

When a report is sent, surrounding chat lines are sent along with the report as well.  This gives the investigator more context for the report.

Can I get in trouble for submitting a false report?

Players are responsible for the reports that they create, and abuse of the player reporting system can lead to temporary or permanent bans, depending on the severity and frequency of the abuse. 

What if someone gains access to my account?

Unfortunately, if an attacker has gained access to your account, we would not be able to distinguish between you and them. That’s why it’s important to enable 2FA, use a strong password for your account, and don’t install untrusted mods or programs. 


Banning and Suspensions

What does being banned/suspended mean?

While banned/suspended you will not be able to connect to multiplayer servers or Realms in past, current, or future versions of Minecraft.  You can still play single-player.

Will I know why and how long I am banned/suspended?

Yes.  A reason and time will be displayed when launching the game in version 1.19.1 onward.  For older versions, you will the message displayed when attempting to join a multiplayer session.

Are all bans permanent?

No.  They vary from a temporary suspension to permanent.  Most bans should be temporary with varying durations based on how severe and the frequency of the violations.  Permanent bans are reserved for the most severe or reoccurring abuse violations.

Why is this an account ban and not an individual server ban?

Those that purposely violate Mojang’s terms require broader action.  This is to prevent them from continuing to do so across the service.

Will I get banned without my case being reviewed by a human?

No.  Each report will be reviewed by those trained specifically to investigate reports in Minecraft called investigators.

Can I appeal a ban/suspension?

Yes.  You can submit a Case Review Request here.

What if someone gets me banned unfairly?

 

All player reports will be reviewed by an investigator to make sure the complaint is well-founded so that any suspensions or bans that might result are fair. 

Our investigators are aware of the kind of things that happen in Minecraft and the possibilities of misinterpretation – for example, chat messages that relate to combat or other in-game situations. Our investigators understand chat messages can have different meanings depending on the situation and consider that context when reviewing reports. Our investigators also follow the same strict privacy procedures that Mojang Studios follows to protect the privacy of information contained in Player Reports.

If you feel that you’ve been banned unjustly, you may submit an appeal at Case Review Request.


False Bans & Abuse of the Feature

Will I be automatically banned if I am reported by a lot of players?  What about content creators or famous individuals that may get targeted?

No automatic bans will be made.  The volume of a report on a player does not affect this.  The reports will review the chat evidence provided before an action is taken.  

What if someone creates a mod that spams/fakes reports?

  • Abuse of the report system with multiple/fake reports will result in action taken against the reporter including temporary or permanent bans, depending on the severity and frequency of the abuse. 
  • Reports cannot be anonymous, and they must contain valid evidence of an abusive chat message from within the game, and a category for that abuse. 
Posted on Leave a comment

JAVA: 1.19.1 Pre-Release 2

This latest pre-release has added new indicators for when modifications have been made to chat.  Read below to get the full details of what that entails.

Changes in 1.19.1 Pre-Release 2

We’ve added the ability to see the signing status of chat messages – this is so you can easily tell when a server is tampering with or removing the signing security of, their players’ messages.

Chat Trust Status

  • Messages that are not signed with the Secure Chat system, or have been tampered with by the server will now be marked
    • Messages with missing or invalid signatures are marked as “Not Secure”
    • Messages that are detected as modified are marked as “Modified”
  • The trust status of messages is displayed with both a colored indicator and an icon
    • The colored indicator is always visible
    • The icon is only visible when the chat screen is open
  • Hovering over the icon will provide more information about the trust status
    • For modified messages, the original secure text will also be displayed in the tooltip

Technical Changes in 1.19.1 Pre-Release 2

Chat Types

  • Chat types added to the chat_types registry are now only used for player chat, and not system messages
    • The system and game_info chat types have been removed
  • Chat types have been simplified and are now only required to define chat and narration decorations
    • Chat types no longer support overlays
    • A system message should instead be used to display overlays

server.properties

  • enforce-secure-profile is now defaulted to true for dedicated servers

Fixed Bugs in 1.19.1 Pre-Release 2

  • MC-253112 – The game output console is logged with warnings regarding chat packets with invalid signatures when using entity selectors within commands
  • MC-253121 – Entities and other non-player chat message sources appear as players on the Select Chat Messages to Report screen
  • MC-253493 – The descriptions of report categories can once again overlap the “Description:” subtitle
  • MC-253495 – Selection boxes of fields within the “Select Report Category” menu list don’t contain white outlines when selected using the TAB key
  • MC-253497 – Entities and other non-player chat message sources appear in the Social Interactions menu
  • MC-253501 – Long messages within the “Select Chat Messages to Report” menu can extend beyond selection boxes and past the scroll bar
  • MC-253517 – Online players cannot connect to offline server because “invalid profile public key signature”
Posted on Leave a comment

Bedrock: Beta & Preview 1.19.20.20

The latest Beta/Preview has made some additional changes to continue to try and create the same experience when playing either JAVA or Bedrock versions of the game.  Check below to see exactly what has been adjusted.

Also, remember that next week we will not see a Beta/Preview.

Features and Bug Fixes

Vanilla Parity

  • Zombies now have a 10% chance to be able to break doors on hard difficulty (MCPE-79636)
  • Removed “Wood” from the names of Mangrove Wood Planks, Stairs, and Slabs (MCPE-156791)
  • The Wandering Trader’s spawning now matches Java Edition and will no longer spawn in water, lava, or underground (MCPE-46911)
  • End Portal Frame Block is now named “End Portal Frame” instead of “End Portal” (MCPE-76821)
  • Tadpoles flopping around while on land now more closely match Java Edition and fishes in speed (MCPE-154316)
  • Polar Bears no longer panic when attacked
  • Piglins will now stop attacking if the player puts on Gold Armor (MCPE-65516)

Spectator Mode (Experimental)

  • Players can now place blocks where a spectator is hovering
  • Players now have their hands back when they are holding a Map when they have one item in the offhand and one in the main hand. Curious how they held it without hands… (MCPE-100259)

Audio

  • Fixed a bug that caused the new Wild Update music to not play in the Wild Update biomes when in Creative mode

Blocks

  • Twisting Vines and Weeping Vines with no support now pop even when the random ticking speed is set to 0 (MCPE-69305)
  • Sculk Catalyst now blooms when a mob with no experience dies next to it
  • Hanging Mangrove Propagules no longer drop a Propagule item when Silk Touched if not at max growth (MCPE-156821)
  • Muddy Mangrove Roots can now be placed sideways (MCPE-153721)
  • Hanging Mangrove Propagule no longer changes color when certain blocks are placed nearby (MCPE-156570)

Gameplay

  • Fixed an issue that could occur when traveling through a nether portal to the overworld (MCPE-158167)

VR

  • The ‘Toggle Perspective’ hint now shows the player’s assignment instead of the default assignment

Mangrove & Azalea Leaves

  • Mangrove and Azalea Leaves no longer prevent tree growth (MCPE-154980)

Mob Effects

  • Fixed an issue with extra health from Health Boost not persisting after exiting the world (MCPE-153504)
  • Fixed an issue that caused FOV to stutter when sprinting while the player had a speed effect applied

Mobile Controls

  • Added support for middle mouse click on iOS

Mobs

  • Jobless Zombie Villagers are no longer unable to ride Minecarts and Boats (MCPE-76831)
  • Ravager is now able to destroy Mangrove Leaves, Azalea, Azalea Leaves, Cave Vines, Dripleaves, Spore Blossoms, and Hanging Roots (MCPE-156551) (MCPE-125322)

Sculk Sensor

  • If two vibrations are emitted at the same time, Sculk Sensors will now react to the closest one (MCPE-155793)
  • If two vibrations are emitted at the same time and the same distance, Sculk Sensors will now react to the one with the highest frequency
  • Sculk Sensors now detect a Creeper exploding with a frequency of 15
  • Sculk Sensors now detect an End Crystal exploding with a frequency of 15 (MCPE-153733)
  • Sculk Sensors now detect a Fish being let out of a Bucket with a frequency of 12
  • Sculk Sensors now detect a TNT being fired out of a Dispenser with a frequency of 12

Stability & Performance

  • Fixed a crash that could occur when teleporting and killing an entity in the same tick
  • Entities that die completely now have their data removed from the world file (MCPE-155283)
  • Fix potential crash when returning to the Overworld from the Nether or The End (
  • The game no longer crashes when entering Coin Starter Bundle Screen

User Interface

  • Redesigned the toggle switches to make it easier to distinguish between the on and off states
  • Saddled Pig’s tooltip changed to “Ride” instead of “Mount” to match other ridable mobs

Trades

  • Fixed an issue that prevented Fisherman Villagers from offering to buy Boats at max level

Technical Updates

General

  • Fixed bugs where the client state could get out of sync with the server if using an item is canceled or fails

Bucket Item

  • Releasing a bucketed custom mob now spawns the correct type of mob
  • Fixed the order in which a bucketed mob is created when released, which means any Actor Properties on it will load correctly

Dedicated Server

  • Added a server property disable-player-interaction which informs clients that they should ignore other players when interacting with the world
  • Added a new dedicated server property, “chat-restriction”, that can be modified in the “server.properties” file to restrict the chat for all players connecting to the server. The property’s possible values are “None”, “Dropped”, and “Disabled”. See the default file for more information

Graphical

  • With data-driven block tessellation, geometry box pivot-base rotation now rotates around the correct pivot point
  • Add Content warnings for large icons for texture tessellation (eg. objects in hand)

Stability and Performance

  • The Client can now generate its own LevelChunks, saving the Server from having to generate and stream over every chunk in view. The server will be limited to generating LevelChunks that are in ticking range and saved on disk
    • Created a new ChunkSource and ChunkViewSource for the Client to generate chunks with
    • Added new FeatureRegistryPacket to send contents of FeatureRegistry to Client
    • Added most BiomeComponents into BiomeDefinitionListPacket for proper Client Biome post-processing
    • Added FeatureToggle ‘Client Side Generation’
    • Modified existing telemetry to split between Server and Client side LevelChunk generation
    • Added code to fix up client-side lighting so it matches the Server side

Experimental Features

Actor Properties

  • Added Content Errors for when there are too many properties on the actor (more than 32) or when a string enum name is too long (more than 32 characters)

  • Restored ability to use a Molang expression string for default values of Actor Properties (These are primarily useful for random starting values)

GameTest Framework

  • Performance Watchdog
    • Added a performance watchdog that monitors GameTests for slow-running scripts
    • Executing a slow-running script will result in content log warnings
    • Additionally, the long script hangs (more than 3 seconds in a single tick) will result in an exception
    • Added new properties to propertiesfor watchdog configuration on Dedicated Server
      • script-watchdog-enable- Enables the watchdog (default = true)
      • script-watchdog-hang-threshold- Sets the watchdog threshold for single tick hangs (default = 3000 ms)
      • script-watchdog-spike-threshold- Sets the watchdog threshold for single tick spikes (default = 100 ms)
      • script-watchdog-slow-threshold- Sets the watchdog threshold for slow scripts over multiple ticks (default = 2ms)
    • Updated mojang-minecraft-uiforms to respond when the client was unable to show a modal form
      • Renamed isCanceledfield to canceled
      • Added cancelationReasonfield
      • Added FormCancelationReasonenum
    • ScoreboardObjectiveDisplayOptions
      • Added ‘ScoreboardObjectiveDisplayOptions’ class
      • Added read-only property ‘Objective: objective’
      • Added read-only property ‘ObjectiveSortOrder: sortOrder’
    • Scoreboard
      • Added function ‘removeObjective(objectiveId: string | Objective): void’ – Untracks an objective
      • Added function ‘addObjective(objectiveId: string, displayName: string): Objective’ – Creates and objective to be tracked, identified with objectiveId and displayed on the screen with displayName
      • Added function ‘getObjectiveAtDisplaySlot(displaySlotId: string): ScoreboardObjectiveDisplayOptions’ – Gets objective and sort order contained in the DisplayObjective slot specified by displaySlotId
      • Added function ‘setObjectiveAtDisplaySlot(displaySlotId: string, ScoreboardObjectiveDisplayOptions: scoreboardObjectiveDisplayOptions): Objective’ – Sets the objective and sort order of the display slot, as specified by displaySlotId
      • Added function ‘clearObjectiveAtDisplaySlot(displaySlotId: string): Objective’ – Clear’s the DisplayObjective of the objective it is currently displaying
    • Block
      • Added Block SignComponent that allows for retrieving the value of sign text – Accessible from getComponent(“sign”)on sign blocks
    • BlockSignComponent
      • Added read-only property text: string- Gets the sign text

General

  • Limit the number of elements in the conditions field of the minecraft:part_visibility to 64
  • Renamed minecraft:aim_collisionblock component to minecraft:selection_box 
  • Renamed the ‘minecraft:block_light_emission’ component to ‘minecraft:light_emission’ and changed its accepted value type from float to int
  • Renamed ‘minecraft:destroy_time’ to ‘minecraft:destructible_by_mining’ and restructured the component to be either defined as a boolean or as an object
    • Setting the component to true will give the block the default destroy time and setting it to false will make the block indestructible by mining
    • Setting the component as an object will let users define the number of seconds needed to destroy the block with base equipment
  • Changed the minecraft:frictioncomponent to represent friction of block instead of movement
Posted on Leave a comment

Let’s Talk About the New Chat Reporting Feature

Hello all!  I know a lot of you haven’t been exactly with Mojang Studio’s latest implementation of the Chat Reporting feature and with the release of the latest Release Candidate they have also released a help article that I’ll link separately here.  If you want a breakdown of what’s in the article read below.


The first thing to note, a lot of people’s concerns about what you can or can’t say on a private server haven’t been new for what appears to be as long as Microsoft has owned the game.  There are clear guidelines that they provide to what isn’t acceptable using any of their services.  Yes, that means their games and their realms.  Link to review Microsoft’s Service Agreement here, Microsoft’s Community Standards here, and finally Xbox Community Standards here.  The addition of the chat reporting feature has just made it easier to submit chat evidence, and with last night’s addition, sending even more chat for additional context.

Minecraft has always been a game for everyone, and sadly some people find it funny to join people’s servers to spam heinous things.  While simply a server can ban these individuals, that doesn’t stop them from moving on to another server to repeat their actions essentially with no consequences, because let’s be real here, they weren’t going to play on the servers they were “trolling” to begin with.

I understand that people are worried about getting banned unjustly or servers that allow certain behaviors from getting reported.  Let’s review below the categories and the “how to” for when you submit a Player Report.


How To Submit a Player Report

On JAVA Edition, the first thing you will do is either press the “P” key or access this by opening the Pause Menu.  From here, you will select the chat the Reason and select the chat messages(s).  Additional messages to provide context for these messages will be submitted as well for review without the need to select them.  There is also a place where you can submit your own comments when submitting the report.  In this space, you can provide additional evidence that you have to support your claim.


Categories

Imminent Harm – Self-harm or Suicide

Someone is threatening to harm themselves in real life or talking about harming themselves in real life. 

Child Sexual Exploitation or Abuse 

Someone is talking about or otherwise promoting indecent behavior involving children. 

Terrorism or Violent Extremism

Someone is talking about, promoting, or threatening acts of terrorism or violent extremism for political, religious, ideological, or other reasons. 

Hate Speech 

Someone is attacking you or another player based on characteristics of their identity, like religion, race, or sexuality. 

Imminent Harm – Threat to Harm Others

Someone is threatening to harm you or someone else in real life. 

Non-Consensual Intimate Imagery

Someone is talking about, sharing, or otherwise promoting private and intimate images. 

Harassment or Bullying

Someone is shaming, attacking, or bullying you or someone else. This includes when someone is repeatedly trying to contact you or someone else without consent or posting private personal information about you or someone else without consent (“doxing”). 

Defamation, Impersonation, False Information

Someone is damaging someone else’s reputation, pretending to be someone they’re not, or sharing false information with the aim to exploit or mislead others. 

Drugs or Alcohol

Someone is encouraging others to partake in illegal drug-related activities or encouraging underage drinking. 


What Happens After a Report Is Submitted?

A report that has been submitted by the following method above is reviewed by a member of a team of Moderators.  They will review the report, and if they find that the message contents do break any of the service violations above, will apply a suspension for online play for a period of time, or depending on how egregious the report is a permanent ban.

When making these decisions they are not only looking at the submitted message.  They are reviewing the additional messages to find the context for the message as well.  They will also review if the report was made in bad faith.  Keep in mind that when submitting a report, you are responsible for creating that report.  If you are found to be abusing this system can lead to actions taken against your account.


What If I Was Suspended/Banned Unjustly?

No one is going to sit here and claim that this system is flawless.  You can expect that sometimes a mistake will be made.  No system will ever be perfect but that doesn’t mean throwing it out entirely.  Mojang Studios does have an appeal system.  You can find it at the bottom of the Help Center pages as well as I will provide a link to provide a ticket for a Case Review.

The Bottom of the Help Center page.

Posted on Leave a comment

Let’s Talk About the New Payer Reporting Feature | Small Update

As of June 30th, Mojang Studios changed the wording of a few things but the context has remained the same.  For a quick summary of what has changed Chat Reporting has been renamed to Player Reporting, and Minecraft Moderators has been changed to Minecraft Investigator


Hello all!  I know a lot of you haven’t been exactly happy with Mojang Studio’s latest implementation of the Player Reporting feature and with the release of the latest Release Candidate they have also released a help article that I’ll link separately here.  If you want a breakdown of what’s in the article read below.


The first thing to note, a lot of people’s concerns about what you can or can’t say on a private server haven’t been new for what appears to be as long as Microsoft has owned the game.  There are clear guidelines that they provide to what isn’t acceptable using any of their services.  Yes, that means their games and their realms.  Link to review Microsoft’s Service Agreement here, Microsoft’s Community Standards here, and finally Xbox Community Standards here.  The addition of the chat reporting feature has just made it easier to submit chat evidence, and with last night’s addition, sending even more chat for additional context.

Minecraft has always been a game for everyone, and sadly some people find it funny to join people’s servers to spam heinous things.  While simply a server can ban these individuals, that doesn’t stop them from moving on to another server to repeat their actions essentially with no consequences, because let’s be real here, they weren’t going to play on the servers they were “trolling” to begin with.

I understand that people are worried about getting banned unjustly or servers that allow certain behaviors from getting reported.  Let’s review below the categories and the “how to” for when you submit a Player Report.


How To Submit a Player Report

On JAVA Edition, the first thing you will do is either press the “P” key or access this by opening the Pause Menu.  From here, you will select the chat the Reason and select the chat messages(s).  Additional messages to provide context for these messages will be submitted as well for review without the need to select them.  There is also a place where you can submit your own comments when submitting the report.  In this space, you can provide additional evidence that you have to support your claim.


Categories

Imminent Harm – Self-harm or Suicide

Someone is threatening to harm themselves in real life or talking about harming themselves in real life. 

Child Sexual Exploitation or Abuse 

Someone is talking about or otherwise promoting indecent behavior involving children. 

Terrorism or Violent Extremism

Someone is talking about, promoting, or threatening acts of terrorism or violent extremism for political, religious, ideological, or other reasons. 

Hate Speech 

Someone is attacking you or another player based on characteristics of their identity, like religion, race, or sexuality. 

Imminent Harm – Threat to Harm Others

Someone is threatening to harm you or someone else in real life. 

Non-Consensual Intimate Imagery

Someone is talking about, sharing, or otherwise promoting private and intimate images. 

Harassment or Bullying

Someone is shaming, attacking, or bullying you or someone else. This includes when someone is repeatedly trying to contact you or someone else without consent or posting private personal information about you or someone else without consent (“doxing”). 

Defamation, Impersonation, False Information

Someone is damaging someone else’s reputation, pretending to be someone they’re not, or sharing false information with the aim to exploit or mislead others. 

Drugs or Alcohol

Someone is encouraging others to partake in illegal drug-related activities or encouraging underage drinking. 


What Happens After a Report Is Submitted?

A player report that has been submitted by the following method above is reviewed by a member of a team of Investigators.  They will review the report, and if they find that the message contents do break any of the service violations above, will apply a suspension for online play for a period of time, or depending on how egregious the report is a permanent ban.

When making these decisions they are not only looking at the submitted message.  They are reviewing the additional messages to find the context for the message as well.  They will also review if the report was made in bad faith.  Keep in mind that when submitting a report, you are responsible for creating that report.  If you are found to be abusing this system can lead to actions taken against your account.


What If I Was Suspended/Banned Unjustly?

No one is going to sit here and claim that this system is flawless.  You can expect that sometimes a mistake will be made.  No system will ever be perfect but that doesn’t mean throwing it out entirely.  Mojang Studios does have an appeal system.  You can find it at the bottom of the Help Center pages as well as I will provide a link to provide a ticket for a Case Review.

The Bottom of the Help Center page.

Posted on Leave a comment

JAVA Edition: 1.19.1 Release Candidate 1

Today’s Release Candidate for JAVA Edition adds some clarity and additions to some of the Chat Reporting categories as well as a technical change for how the run_command click event functions.  Check it out below.

Changes in 1.19.1 Release Candidate 1

  • Updated the categories for chat reporting
    • The “Profanity”, “Nudity or pornography” and “Extreme violence or gore” categories have been removed
    • The description for the “Drugs and alcohol” category has been updated to “Someone is encouraging others to partake in illegal drug-related activities or encouraging underage drinking”
    • The description of the “Harassment and bullying” category has been extended with the following: or posting private personal information about you or someone else without consent (“doxing”).
  • Increased the amount of chat context sent with each chat report

Technical Changes in 1.19.1 Release Candidate 1

  • The run_command click event for text components no longer supports sending chat messages directly
    • Only commands are supported, so a command such as /say should be used instead
    • This means values now always need to be ‘/’-prefixed

Fixed Bugs in 1.19.1 Release Candidate 1

  • MC-250020 – Allay doesn’t ignore items when mobGriefing is set to false
  • MC-252511 – Bedrock not generating on the new blending border between old and new blending
  • MC-252987 – Illegal character ‘\n’ in text component clickEvent
  • MC-253114 – Selection boxes within the “Select Chat Messages to Report” menu don’t disappear when deselecting fields after reentering the menu
  • MC-253188 – Selection boxes within the “Select Chat Messages to Report” menu differ in size ever so slightly depending on how they’re selected
  • MC-253225 – Selection boxes of fields within player reporting menu lists don’t contain white outlines when selected using the TAB key
  • MC-253227 – Players can only be reported using the reporting system if they’re present within the world
  • MC-253336 – Using the eye of ender “crashes” game in the seed: -3721742095548798177
  • MC-253422 – The selection of the “Please report breaches of our Community Standards” text within the “Select Report Category” menu is slightly confusing due to the words “Community Standards” being underlined by default
Posted on Leave a comment

Bedrock: 1.19.2 & 1.19.10.24 Beta & Preview

Let’s start off with the latest update that fixes a few of those pesky annoying bugs.

1.19.2

Fixes:

  • Fixed several crashes that could occur during gameplay
  • Fixed a bug on certain flat worlds where below-0 terrain was accidentally being removed on level load, if there was bedrock at y=0 (MCPE-156679MCPE-156698)
  • Mobs that teleport through a Nether portal with a destination above y=128 will no longer have their position adjusted to 128 (MCPE-155465)

Beta & Preview 1.19.10.24

The latest preview and beta help with stability, changes to the duplication of the Allay, and issues with the Trader Llama Spawn Egg.  If you had problems with the D-Pad not working they also seem to have fixed this bug as well.

Features and Bug Fixes

Experimental features

  • Removed the Vanilla Experiment toggle since it has no active experimental content
  • Removed the Wild Experiment toggle since it has no active experimental content

Allay

  • Allay duplication cooldown is now 5 minutes (up from 2.5 minutes)

Mobs

  • Fixed a bug that caused an empty Trader Llama Spawn Egg to appear in the Creative menu in pre-1.19.10 worlds

Stability and Performance

  • Fixed a crash when assigning an invalid entity to Mob Spawners

Touch Controls

  • Fixed touch control’s right d-pad button not working when the d-pad area overlapped with the hotbar area (MCPE-156103)
Posted on Leave a comment

JAVA Edition: 1.19.1 Pre-Release 1

Mojang Studios just dropped the latest re-release for 1.19.1.  If things go smoothly we can expect this to release next Tuesday the 28th.  

For those worried about the Chat Report system that was newly added Mojang Studios will be releasing a help article soon that will explain it a bit more, so maybe hold off on the doom posting for a tad bit longer.

Changes in 1.19.1 Pre-Release 1

  • Allay duplication now has a 5-minute cooldown
  • Along with the support for reporting chat, reported players can now be banned from online play and Realms after moderator review
  • The game will show a notice screen on startup if you have been banned from online play
    • The reason for the ban is shown as well as how long the ban is valid for

Fixed Bugs in 1.19.1 Pre-Release 1

  • MC-249973 – Loading resource packs are significantly slower in 1.19
  • MC-252327 – World list fails to load after restarting the game and deleting a world
  • MC-252508 – Realms worldgen type missing language string
  • MC-253055 – Resource packs causing each WeighedSoundEvents to duplicate Sounds
  • MC-253102 – Chat reporting uses “Messages” for one message
  • MC-253105 – Chat report category scroll bar intersects the selected option outline
  • MC-253108 – Selection boxes within the “Select Report Category” menu aren’t vertically centered with the text inside them
  • MC-253109 – The descriptions of report categories can overlap the “Description:” subtitle
  • MC-253110 – Text within the “Discard report and comments?” menu isn’t horizontally centered
  • MC-253111 – You cannot use CTRL+HOME or CTRL+END to navigate to the beginning or end of text within the “Report Chat” menu
  • MC-253113 – Chat message content can extend past the outline of a button and past the scroll bar
  • MC-253123 – The button within the “Sending your report” menu changes upon resizing the game window
  • MC-253126 – The scroll bar within the “Select Chat Messages to Report” menu sometimes resets its position to the bottom of the list after scrolling upwards
  • MC-253127 – Reason is not provided when chat report creation is not able to be started
  • MC-253134 – Allays from older worlds don’t duplicate
  • MC-253176 – The character indicator symbol within the “Report Chat” menu is untranslatable
  • MC-253178 – The word “Non-consensual” is spelled as “Non-consentual” within the “gui.abuseReport.reason.non_consensual_intimate_imagery” string
  • MC-253183 – The word “Unrelated” within the “gui.chatSelection.fold” string is incorrectly capitalized
  • MC-253185 – The ESC key cannot be used to exit the “Sending your report” menu
  • MC-253191 – Particles produced from allays duplicating cannot be seen by other players