Skip to content

EssentialX-antibuild has strong protection for signs #6598

Open

Description

@doubi1230

Type of bug

Other unexpected behaviour

/ess dump all output

https://essentialsx.net/dump?bytebin=Ti5F4jYiqm

Error log (if applicable)

No response

Bug description

After I installed the EssentialX-antibuild plugin, pistons on the server couldn't push any blocks with signs. Deleting the plugin restored everything to normal. It's obvious that EssentialX-antibuild has a hidden protection feature for signs. The plugin doesn't allow changing the configuration, so I'm requesting a fix.

Steps to reproduce

After installing EssentialX-antibuild, use a piston to push a block with a sign on it

Expected behaviour

Request to remove EssentialX-antibuild's forced protection on signs, as it affects a lot of redstone machines.

Actual behaviour

Request to remove EssentialX-antibuild's forced protection on signs, as it affects a lot of redstone machines.

Additional Information

No response

Activity

  1. added theissue type on Jul 31, 2026
  2. github-actions commented on Jul 31, 2026

    @github-actions
  3. MochaMilkie commented on Nov 6, 2026

    @MochaMilkie

    I tried to reproduce this on the reported configuration and couldn't.
    Vanilla behavior does not allow a piston to extend if a sign is directly in the path of the blocks moving. This is reflected in the plugin based on my testing. All other instances of sign interactions broke the sign when expected, and left the sign placed when expected in my testing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bug: unconfirmedPotential bugs that need replicating to verify.

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions