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.

Sign up for GitHub

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

Jump to bottom

Blowing up rails causes exceptions #32

Closed
anuar2k opened this issue Dec 23, 2017 · 1 comment · Fixed by MovingBlocks/Terasology#3197
Closed

Blowing up rails causes exceptions #32

anuar2k opened this issue Dec 23, 2017 · 1 comment · Fixed by MovingBlocks/Terasology#3197

Comments

@anuar2k
Copy link
Contributor

anuar2k commented Dec 23, 2017 •
edited
Loading

In 75% times when a rail gets blown up (it doesn't matter what causes the explosion) the NullPointerException is raised. It's really hard to define when it does happen, but it's easy to replicate the issue.

Log:
https://gist.github.com/anuar2k/6d9cc6885ec33d415711e9b16e60d07f
@anuar2k anuar2k mentioned this issue Dec 23, 2017
Merged
@eviltak
Copy link
Member

eviltak commented Dec 23, 2017

Just as IntelliJ quite nicely points out, dereferencing the blockDamageModifierComponent causes a NPE. This is an engine issue.

This was referenced Dec 23, 2017
Closed
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add blockDamageModifierComponent null check eviltak/Terasology
2 participants
@eviltak @anuar2k