You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mysterious Cubes placed by non-AE2 worldgen structures are undetectable by the Meteorite Compass.
The Mysterious Cubes that are generated in default AE2 meteorites are detected without issue, as are ones that are placed by hand. When they are placed by custom worldgen features, however, the compass does not detect them, even when you're literally standing on top of said cube. Strangely, as far as I can tell there is no difference whatsoever in the blockstate between the manually placed Cubes, the AE2-generated ones, and the custom-generated ones.
I tested again using a minimal mod set and the issue persisted.
Mods:
AE2 15.3.3
Jade 11.13.1
JEI 15.20.0.106
Paxi 1.20-Forge-4.0 (for the automatic datapack usage)
YUNG's API 1.20-Forge-4.0.6 (Required for Paxi)
Minecraft 1.20.1
Forge 47.3.33
How to reproduce the bug
Have a Mysterious Cube placed by a custom worldgen feature
Create or acquire a Meteorite Compass
Move within range that the Meteorite Compass should detect the Mysterious Cube
See that the Mysterious Cube is not being detected
Expected behavior
The Meteorite Compass should detect Mysterious Cubes placed by all world generation.
Additional details
This was discovered when I was working on a less-destructive meteorite generation datapack. Without being able to detect the new meteorites, though, the datapack becomes pretty unusuable.
Which minecraft version are you using?
1.20
On which mod loaders does it happen?
Forge
Crash log
N/A
The text was updated successfully, but these errors were encountered:
Describe the bug
Mysterious Cubes placed by non-AE2 worldgen structures are undetectable by the Meteorite Compass.
The Mysterious Cubes that are generated in default AE2 meteorites are detected without issue, as are ones that are placed by hand. When they are placed by custom worldgen features, however, the compass does not detect them, even when you're literally standing on top of said cube. Strangely, as far as I can tell there is no difference whatsoever in the blockstate between the manually placed Cubes, the AE2-generated ones, and the custom-generated ones.
I tested again using a minimal mod set and the issue persisted.
Mods:
AE2 15.3.3
Jade 11.13.1
JEI 15.20.0.106
Paxi 1.20-Forge-4.0 (for the automatic datapack usage)
YUNG's API 1.20-Forge-4.0.6 (Required for Paxi)
Minecraft 1.20.1
Forge 47.3.33
How to reproduce the bug
Expected behavior
The Meteorite Compass should detect Mysterious Cubes placed by all world generation.
Additional details
This was discovered when I was working on a less-destructive meteorite generation datapack. Without being able to detect the new meteorites, though, the datapack becomes pretty unusuable.
Which minecraft version are you using?
1.20
On which mod loaders does it happen?
Forge
Crash log
N/A
The text was updated successfully, but these errors were encountered: