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

Protect against get_content_id() raising an error #20

Closed
wants to merge 1 commit into from

Conversation

Treer
Copy link
Collaborator

@Treer Treer commented Apr 12, 2020

sfan5 submitted a fix, so this PR probably won't need to be merged. I'll close it when the fix is merged.


Implements @trungus's fix for issue #19: the minetest.get_content_id() problem in MT 5.2.0.

Whether this should be merged depends on whether Minetest devs decide to fix the behavior of get_content_id() when register_alias_force() is used.

Note that merging this fix isn't enough - someone would need to update the Content DB as well. Currently it's in PilzAdam's account.

minetest.get_content_id() can error out of the game in MT 5.2.0 if another mod (such as moreblocks) uses register_alias_force() on the node.
@Treer
Copy link
Collaborator Author

Treer commented Apr 19, 2020

sfan5's fix has been merged into Minetest, and I have faith it will solve this, so the PR is no longer required with latest MT builds.

@Treer Treer closed this Apr 19, 2020
@Treer
Copy link
Collaborator Author

Treer commented May 16, 2020

@debagos I don't know whether it was the right decision, but

  • I can't update the version in contentDB anyway, so nether will stay broken in MT5.2 for most people regardless.
  • Soon MT 5.2 will be a minor release blip in the past which nobody uses.

Those who go to github instead of contentdb could still get the fix version from this PR's source. e.g. https://github.com/Treer/nether/archive/bugfix/get_content_id.zip

@debagos
Copy link

debagos commented May 17, 2020

@Treer I didn't know that you created a fix already because i could see it anywhere. Thank you very much for the fix!

  • Soon MT 5.2 will be a minor release blip in the past which nobody uses.

Maybe that's right, but between the release of 5.2 and the next release my server is (was) in an unplayable state.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants