8000 Instead of tracking mass left in a mined object, track total mass removed · Issue #81 · dustproject/dust · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Instead of tracking mass left in a mined object, track total mass removed #81

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
Open
dhvanipa opened this issue Mar 5, 2025 · 4 comments
Open

Instead of tracking mass left in a mined object, track total mass removed #81

dhvanipa opened this issue Mar 5, 2025 · 4 comments

Comments

@dhvanipa
Copy link
Member
dhvanipa commented Mar 5, 2025

another option is to do the reverse, instead of tracking remaining mass we track “total mass removed”, then when you mine you always get it from object type to see if all the mass was removed. In this case no need to update

makes it easier to update mass of objects post-deployment

h/t @vdrg
@vdrg
Copy link
Contributor
vdrg commented Mar 17, 2025

The only issue I see with this is that decreasing the mass could become tricky, as some objects might have already been mined past the new mass

@dhvanipa
Copy link
Member Author

The only issue I see with this is that decreasing the mass could become tricky, as some objects might have already been mined past the new mass

Right but the next time you call "mine" it would turn it into air right? Cuz mass left would be 0. It'd be like mining a 0 mass block like wheat

@vdrg
Copy link
Contributor
vdrg commented Mar 19, 2025

but wouldn't there be an inconsistency in the energy conservation? if you already removed a bunch of mass from the object, and then you change its mass to a lower value, the difference was already transferred to the pool (created out of nothing if you look at it from the perspective of the new mass changes)

@dhvanipa
Copy link
Member Author
dhvanipa commented Mar 19, 2025 •
edited
Loading

yea true, maybe then lets not change it haha. Can close this issue if you agree

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

No branches or pull requests
2 participants
@vdrg @dhvanipa
0