You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a fairly major back-end change that should improve performance for the case where someone has sites that aren't actively mined, or are only partially mined.
In effect, I'm looking to track the entity placed/mined events so that the ore entities we query are only ones that are within a miner's effective range. This would also let us somewhat decouple sites from ore entities, and simplify #47 as well as allow a variant of #37 to work sanely.
The text was updated successfully, but these errors were encountered:
As per #46, we can ask miners about ore within their range, and be
notified when the miners are created/destroyed.
(currently, we're using that to write a message counting the total ore
amount under the miner; baby steps)
The deleted files will come back in some form or other.
This is a fairly major back-end change that should improve performance for the case where someone has sites that aren't actively mined, or are only partially mined.
In effect, I'm looking to track the entity placed/mined events so that the ore entities we query are only ones that are within a miner's effective range. This would also let us somewhat decouple sites from ore entities, and simplify #47 as well as allow a variant of #37 to work sanely.
The text was updated successfully, but these errors were encountered: