Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No block updates when setting blocks #2292

Closed
sjoerdtim opened this issue Jul 23, 2019 · 2 comments
Closed

No block updates when setting blocks #2292

sjoerdtim opened this issue Jul 23, 2019 · 2 comments
Labels
bug An issue that needs to be fixed. Alternatively, a PR fixing an issue. completed The issue has been fully resolved and the change will be in the next Skript update.

Comments

@sjoerdtim
Copy link

Description

When a block is set using Skript, there is no block update. This causes blocks like fences and iron bars to not connect to eachother and/or other surrounding blocks.

Steps to Reproduce

Set a couple blocks to fence blocks using Skript and watch how they get connected.

Expected Behavior

Block updates are called, causing these fences to connect to eachother properly.

Errors / Screenshots

Proof

Server Information

  • Server version/platform: Paper version git-Paper-639 (MC 1.13.2) (Implementing API version 1.13.2-R0.1-SNAPSHOT)
  • Skript version: Skript version 2.4-beta3
@bensku
Copy link
Member

bensku commented Aug 4, 2019

Is this something new, or has Skript always done this? In any case, Skript causing block updates would make setting many blocks significantly slower.

@bensku bensku added the waiting for reply The report needs a response from the reporter to determine course of action. label Aug 4, 2019
@sjoerdtim
Copy link
Author

sjoerdtim commented Aug 4, 2019

Is this something new, or has Skript always done this? In any case, Skript causing block updates would make setting many blocks significantly slower.

Might just be Minecraft changing how they handle the fence block states.

Still, I think setting a block to fence using Skript should have it connect properly. Not sure what other way you could use to resolve this.

@ShaneBeee ShaneBeee added bug An issue that needs to be fixed. Alternatively, a PR fixing an issue. completed The issue has been fully resolved and the change will be in the next Skript update. and removed waiting for reply The report needs a response from the reporter to determine course of action. labels Jun 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An issue that needs to be fixed. Alternatively, a PR fixing an issue. completed The issue has been fully resolved and the change will be in the next Skript update.
Projects
None yet
Development

No branches or pull requests

3 participants