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

New set blocks not rendered in previously empty chunks #2989

Open
2 tasks done
shaijana opened this issue Nov 11, 2024 · 0 comments
Open
2 tasks done

New set blocks not rendered in previously empty chunks #2989

shaijana opened this issue Nov 11, 2024 · 0 comments
Labels
Requires Testing This is a new issue which needs to be approved before labeled with "bug"

Comments

@shaijana
Copy link

shaijana commented Nov 11, 2024

Server Implementation

Paper

Server Version

1.21.3

Describe the bug

When using //set (or similar commands) with the latest versions of Paper and FAWE, block changes are not rendered correctly in chunks that were previously empty. However, after relogging, the changes appear as expected.

This issue does not occur when using a Fabric client with Sodium installed. The error also occurs with the latest version of Spigot.

To Reproduce

  1. Create a server with the newest snapshot of paper and fawe and their default config.
  2. Start a vanilla client.
  3. Select two cornors in empty chunks and use //set 1.

Expected behaviour

The block change should be visible .

Screenshots / Videos

image

https://youtu.be/q_Qc5Eex8Q8

Error log (if applicable)

No errors reported

Fawe Debugpaste

https://athion.net/ISPaster/paste/view/f90b1418834f4c7daeeedfbee191525e

Fawe Version

2.12.1-SNAPSHOT-964

Checklist

Anything else?

No response

@shaijana shaijana added the Requires Testing This is a new issue which needs to be approved before labeled with "bug" label Nov 11, 2024
@shaijana shaijana changed the title New set blocks not rendered New set blocks not rendered in previously empty chunks Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Requires Testing This is a new issue which needs to be approved before labeled with "bug"
Projects
None yet
Development

No branches or pull requests

1 participant