Skip to content

GitLab

    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    • Menu
    Projects Groups Snippets
  • Get a free trial
  • Sign up
  • Login
  • Sign in / Register
  • CubeKrowd Bug Tracker CubeKrowd Bug Tracker
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 47
    • Issues 47
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Insights
    • Issue
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • CubeKrowd Network
  • CubeKrowd Bug TrackerCubeKrowd Bug Tracker
  • Issues
  • #134
Closed
Open
Created Jan 03, 2021 by Fl05k8r@flofeatdennis

Piston doesn't extend after retracting when powered while retracting

Description:

When a Sticky Piston has two (or more) connected blocks (f.e. 2 Slimeblocks or Slimeblock+Stone) directly in front of it, pulls them, and gets powered while retracting, it doesn't push/extend/update after having retracted. In Vanilla it does.

Steps to reproduce:

  1. Place a Sticky Piston. The Direction of the Piston doesn't matter.
  2. Place a Slime block and another block directly infront of the piston.
  3. Place a redstone line to power it.
  4. Place a second redstone line to power it, connected to the same source as the first redstone line, but inverted. (You can use a redstone torch for this)

Example: Setup

  1. Unpower it

Expected Result (Tested in 1.16.4 Vanilla): In_Vanilla

Result on CubeKrowd: In_CubeKrowd

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking