Jump to content
View in the app

A better way to browse. Learn more.

Forge Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Featured Replies

Posted

I'm new to modding with forge, and I'm trying to figure out how to make a chest that can be moved by pistons. I assume it involves having to make a new abstract block entity class, but I'm not sure how to override the settings that make block entities immovable by pistons. Any help would be appreciated :)

The only real option to override a BlockEntity's PushReaction is DESTROY which will destroy the block and spawn its drops.

See for example BedBlock.getPistonPushReaction()

 

The issue is Minecraft's piston logic has no code to properly support moving block entities.

e.g. copying the chest's inventory from the start location to a newly created BlockEntity in the end location.

 

I'm pretty sure if they tried to support it, it would probably be a major source of item duping glitches. 🙂 

Boilerplate:

If you don't post your logs/debug.log we can't help you. For curseforge you need to enable the forge debug.log in its minecraft settings. You should also post your crash report if you have one.

If there is no error in the log file and you don't have a crash report then post the launcher_log.txt from the minecraft folder. Again for curseforge this will be in your curseforge/minecraft/Install

Large files should be posted to a file sharing site like https://gist.github.com  You should also read the support forum sticky post.

You could try copying the piston code into a new block along with the supporting classes.

The key changes will be

* making PistonResolverStructure save the NBT from block entities that are to be pushed so it can reapply it to the new block entity.

* remove the check in PistonBaseBlock.isPushable() that stops block entities being pushed.

 

You will probably find that this doesn't work properly. Not just because it is hard to get right, but there likely a lot of hardwired Minecraft code elsewhere that expects the piston to be its specific class/instance?

 

Other issues include (the hard to get right part): 

* How to handle things like vanilla's double chests when you only push part of it?

* pistons trying to push other pistons need special handling. But the vanilla piston won't know how to handle your piston.

Boilerplate:

If you don't post your logs/debug.log we can't help you. For curseforge you need to enable the forge debug.log in its minecraft settings. You should also post your crash report if you have one.

If there is no error in the log file and you don't have a crash report then post the launcher_log.txt from the minecraft folder. Again for curseforge this will be in your curseforge/minecraft/Install

Large files should be posted to a file sharing site like https://gist.github.com  You should also read the support forum sticky post.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

Important Information

By using this site, you agree to our Terms of Use.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.