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

Jump to bottom

Use minetest.after, not minetest.register_globalstep #4

Closed
tacotexmex opened this issue Sep 7, 2017 · 3 comments
Closed

Use minetest.after, not minetest.register_globalstep #4

tacotexmex opened this issue Sep 7, 2017 · 3 comments
Labels
enhancement

Comments

@tacotexmex
Copy link
Collaborator

tacotexmex commented Sep 7, 2017 •
edited

Recently learned that the minetest.after function is less CPU intensive than minetest.register_globalstep.

For optimization, the minetest.after approach should be implemented.

(Am I doing it right, @sofar?)
@SmallJoker
Copy link
Member

Use minetest.after when it improves the readability of the code. Please see minetest-mods/item_drop@e84433d#commitcomment-29486594

@tacotexmex
Copy link
Collaborator Author

tacotexmex commented Jun 26, 2018 •
edited

Well did it? 🙂 (…improve the readability of the code?) ¯_(ツ)_/¯

@tacotexmex
Copy link
Collaborator Author

Closing as the issue is accomplished.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@SmallJoker @tacotexmex