Minecraft Forums

@ajthemacboy

When Mojang introduced slime blocks in 1.8, they re-did the piston code to completely change the way pistons move blocks. This is how slime blocks get their stickiness. In order to maintain compatibility with as many mods as possible, I chose to add new pistons with similar code, rather than directly modify existing pistons. This means that in order to utilize the sticky properties of the slime blocks, you need to use either a slime piston or sticky slime piston.

@Krutonious

Your setup of slime block, movable block, slime block, piston is behaving exactly like it should. To quote the Minecraft wiki:

Slime blocks are not pulled by a non-sticky piston, nor are they moved if an adjacent (non-slime) block is moved by a piston.

In your case that second slime block won't be moved as it would have to be pulled by an adjacent (non-slime) block.

@Everyone

I just released an update. Someone alerted me to a bug that would cause slime pistons to fail to move if a redstone repeater or comparator was attached to a slime block. That's patched now.

Quote from Stormalisk»

So I ran a test replacing mumbo jumbo's "missle silo" contraption with BiS's blocks. I ran it and it broke a bunch of the redstone underneath it, as well as creating "invisible blocks". Seems like it tried to run but failed?

Just finished overhauling the slime piston movement code (piston movement is way too complicated...). The updated version should play much nicer with redstone and other non-block blocks. There's still a slight bug still in the code, but I can't seem to figure it out and I don't think anyone will encounter it.

@Krutonious, this update should fix your deleted block bug as well.

Quote from Stormalisk»

Redstone is no longer broken due to activation, and pistons do not create "ghosts" or get stuck,

However found a bug where sometimes pistons will not fire at all or are deleted themselves if adjacent to each other. As is used in the "missile silo" redstone build.

I see you found the bug I was talking about. Turns out it was the result of a larger code error that's patched now. Try 3.1.1 and let me know what happens.

Quote from Mister_Bander»

Cool mod! I downloaded version 3.0.2, tested it and found this 'monster piston' bug (see image).

This happens when I place a sticky slime piston on a redstone block, if I first place a sticky slime piston and then a redstone block, it works fine

EDIT: This problem also happens on non-sticky slime pistons

Finally got around to fixing this, use version 3.1.2. Too many mods and things on my palate!

Getting the launching down is incredibly tricky. Even regular Minecraft seems to not launch me from time to time. In general, BIS looks for any entities in front of a slime block during an extension phase and attempts to launch them in the direction of the extension. I've gone and tweaked the launching system to remove the 'double-boost' problem, as well as the feedback loop crash you were having for the piston system on the left. The only remaining issue is that slime block clusters with pistons that push on the same tick can make blocks disappear. This only happens when you have two pistons that fire at the same time in the same direction, which you really shouldn't have anyways. I'm not planning on fixing that bug, as it requires complicated coding to check if any other pistons are firing during a tick.

Picky picky!

But really, editing launch forces is about the easiest thing to do. Check out version 3.1.5 and let me know what you think.

Honestly, I have no clue as to why that is happening. I haven't touched this mod in years. The only thing I can guess is that it gets confused moving two pistons at once with slime blocks. Perhaps adding a repeater for a delay? Not sure if it will help, but that's all I can say.

Nice mod

Quote from KingRyan3651»

Where would I put the repeater you think?

No clue. Somewhere that makes the left and right sides open at different times? I'm just saying that you might have luck if the door parts don't all open at once. Not sure.

Quote from ShizaRiku»

For this feature would making two separate versions solve this? A non-coremod and a coremod version.

I am not familiar with java (JavaScript :/) but from what it sounds like its difficult or tedious. Maybe both but i thought I would ask.

To be honest, I have no idea how to make a coremod. I'm really done with this mod anyways, but I hate to let help requests go unanswered.

The biggest thing you'd want to do is find the routine in the code that handles the pistons pushing, and make that routine call your code instead of doing its own stuff.

That's a non-trivial thing. In the easiest case -- there is one method that does this and nothing else -- you simply use ASM to put, at the beginning of the method, the equivalent of "return myMethod(argument list)".

In any case, you have to figure out what bytecode corresponds to the method call, where to insert it into the method, and then how to do so. There's at least two ways (I think) to do it; locating the where for anything but that simple case is painful; and the compiling to java assembly takes some learning.

My suggestion: Get help from others that have already done this.