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

Piston head data is probably incorrect #88

Closed
joserobjr opened this issue Jan 26, 2020 · 1 comment
Closed

Piston head data is probably incorrect #88

joserobjr opened this issue Jan 26, 2020 · 1 comment
Assignees
Labels
Resolution: resolved The issue has been addressed or the request has been accepted Type: bug Something isn't working
Milestone

Comments

@joserobjr
Copy link
Member

Affected Version
3.1.0-SNAPSHOT

Describe the bug
Nukkit 1.X doesn't support pistons so I couldn't test this feature, but CloudburstMC/Nukkit#914 implements it and PowerNukkit V1.X have it merged, so after a world conversion from Java Edition 1.15.2 to Nukkit 1.X and then opening the world with PowerNukkit, I could see that the heads are being rendered with the info_update block, which indicates that it has an incorrect block id or data value.

To Reproduce
Steps to reproduce the behavior:

  1. Create a Java Edition 1.15.2 world and place a sticky piston receiving redstone power
  2. Convert a to the Nukkit 1.X format
  3. Move the world to a PowerNukkit setup
  4. Go to the piston location in Bedrock Edition
  5. See the block_info instead of an extended piston arm

Expected behavior
See an extended piston arm

Screenshots
image

@joserobjr joserobjr added the Type: bug Something isn't working label Jan 26, 2020
@joserobjr joserobjr added this to the v3.0.1 milestone Jan 26, 2020
@joserobjr joserobjr self-assigned this Jan 26, 2020
@joserobjr
Copy link
Member Author

Fixed.
image

@joserobjr joserobjr added the Resolution: resolved The issue has been addressed or the request has been accepted label Jan 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution: resolved The issue has been addressed or the request has been accepted Type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant