#When placing blocks with Force Place, copied NBT data is not respected + game crashes

1 messages · Page 1 of 1 (latest)

hoary fogBOT
#

@neon inlet uploaded a log, Axiom version: Axiom 2.7.0
Environment: Windows, Minecraft 1.20.4 only using Axiom and Fabric API.
Mode: Builder Mode

Description:
When Force Place is enabled and I use the "ctrl +c" function to copy a block with non-default NBT data (for example, the top half of a door or a fence with one of its directions active), the block is placed with its default data (i.e. irrespective of the copied data). When placed enough times—in my testing, it's ranged from a mere ~3-5 up to ~15—the game will crash.

What I expected to happen was...:
Blocks placed with respect to their copied NBT data.

What actually happened was...:
Blocks placed without respect to their copied NBT data + game crashes.

Steps to Reproduce:

  • Enabled Force Place (as far as I've found, No Updates does not need to be enabled).
  • Copy a block with non-default block data (I tested with doors and fences, but the crash may occur with more blocks—does not seem to crash with tall grass, however).
  • Place the block with the copied data multiple times.

Can you recreate the bug?
Yes

Attachments:
Crash report:
Demonstration: https://www.youtube.com/watch?v=-0yJfEPJajs

  • Fabric 0.15.7 on 1.20.4

Axiom version: Axiom 2.7.0
Steps to Reproduce:

  • Turn on Force Place (as far as I've found, No Updates does not need to be enabled).
  • Copy a block with non-default block data (I tested with doors and fences, but it may occur with more blocks—does not seem to happen with grass).
  • Place the block with the copied data multiple times.
▶ Play video
#

@neon inlet uploaded a log, The bot deleted the message + the pastebin, so here's the crash report:

  • Fabric 0.15.7 on 1.20.4
safe peak
#

Fixed both issues

neon inlet
#

Thank you!