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
When creating an custom block entity like this: StartupEvents.registry("block", (event) => { event.create("test") .blockEntity((entityInfo) => { entityInfo.inventory(9, 3); entityInfo.rightClickOpensInventory(); }) })
It seems that the inventory of said block entity cannot be interacted by anything but player. Things like vanilla hoppers and create funnels completely ignore the inventory. This is probably because the inventory of the custom block entity isn't a regular inventory but rather a custom attactment.
I'm not certain whether this is intentional.
Crash report/logs
No response
The text was updated successfully, but these errors were encountered:
For those who also encounter this problem on 1.20.1, PowerfulJS seems to be the solution. Here's some example code for a block that has no manual inventory, but gives an attached hopper 1 sugarcane per second:
note that while you might not think the "insert Item" function is needed, removing it will make any item hoppered into the block, accidentally or otherwise, vanish into oblivion.
Minecraft Version
1.20.1
KubeJS Version
2001.6.5-build.7
Rhino Version
2001.2.2-build.18
Architectury Version
9.2.14
Forge/Fabric Version
Forge 47.2.0
Describe your issue
When creating an custom block entity like this:
StartupEvents.registry("block", (event) => { event.create("test") .blockEntity((entityInfo) => { entityInfo.inventory(9, 3); entityInfo.rightClickOpensInventory(); }) })
It seems that the inventory of said block entity cannot be interacted by anything but player. Things like vanilla hoppers and create funnels completely ignore the inventory. This is probably because the inventory of the custom block entity isn't a regular inventory but rather a custom attactment.
I'm not certain whether this is intentional.
Crash report/logs
No response
The text was updated successfully, but these errors were encountered: