Cracker's Wither Storm Mod

Cracker's Wither Storm Mod

5M Downloads

Unable to place amulet painting

Nov1st2k10 opened this issue ยท 5 comments

commented

Please check the guidelines before submitting: #217

Minecraft version
The version of Minecraft the mod is running on
1.19.4
Mod version
The version of the mod you are using
3.2.1.3
Describe the bug
A clear and concise description of what the bug is.
Amulet painting is unable to be placed

To Reproduce
Steps to reproduce the behavior:

  1. Get a 'painting'
  2. Make a 2 block tall 1 block wide wall
  3. Place painting on wall
  4. Amulet painting cant get placed

Crash Reports / Logs
Crash reports / logs hosted on pastebin, gist, etc.

Is OptiFine installed?
Specify if you're using OptiFine
No
Screenshots
If applicable, add screenshots to help explain your problem.
image

texture for unplacable painting
you can find the texture for the painting at witherstormmod/assets/witherstormmod/textures/painting/amulet.png

commented

Was unable to reproduce this in 1.19.4, the painting is placed just fine.

commented

@LocalWaterCreeper911911 how were you able to place it? are you sure you're on 1.19.4? not 1.19.2 or anything, because i do believe the modded paintings cannot be placed due to the changes with paintings in 1.19.4 so i don't understand how you would have gotten it working

  1. Its 1.19.4 with experimental features turned ON.

  2. amulet painting is in creative menu:

Go to setting and search for setting called 'operator utilites' and turn it on
then go to creative menu and see a button with command block on it, click it
there are 4 vanilla paintings and 1 cwsm painting, so yeah
i tried placing this painting and it was placed just fine

commented

@LocalWaterCreeper911911 how were you able to place it? are you sure you're on 1.19.4? not 1.19.2 or anything, because i do believe the modded paintings cannot be placed due to the changes with paintings in 1.19.4 so i don't understand how you would have gotten it working

commented

Most players won't be playing with experimental features on. Checked and can confirm this bug exists.

commented

Will be fixed in the next 1.19.4/1.20.1 release