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

Lava falling property key not recognized #1662

Closed
BemusedLeader10 opened this issue Dec 3, 2024 · 3 comments · Fixed by #1666
Closed

Lava falling property key not recognized #1662

BemusedLeader10 opened this issue Dec 3, 2024 · 3 comments · Fixed by #1666
Assignees
Labels
🐛 bug Something isn't working
Milestone

Comments

@BemusedLeader10
Copy link

BemusedLeader10 commented Dec 3, 2024

The falling property key is used for lava springs, yet in the most recent update this is now no longer recognized by Spyglass

"state": {
  "Name": "minecraft:lava",
  "Properties": {
    "falling": "true"
  }
}

Image

@misode
Copy link
Member

misode commented Dec 10, 2024

As far as I can tell, falling is not a block property of lava (it is a fluid property though). You cannot autocomplete it in /setblock and it isn't present in the data generated files.

Image
Image

@misode misode added the *works as intended This is not a bug; it's a feature! label Dec 10, 2024
@misode misode closed this as not planned Won't fix, can't repro, duplicate, stale Dec 10, 2024
@misode
Copy link
Member

misode commented Dec 10, 2024

Okay I see. The issue is actually that the spring feature type uses a fluid state rather than a block state.

@misode misode reopened this Dec 10, 2024
@misode misode added 🐛 bug Something isn't working and removed *works as intended This is not a bug; it's a feature! labels Dec 10, 2024
@BemusedLeader10
Copy link
Author

@misode misode added this to the Backlog milestone Dec 10, 2024
@misode misode self-assigned this Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants