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

Add remembering blocks that the player has revealed proximity #281

Open
VanyaNexus opened this issue Apr 9, 2023 · 2 comments
Open

Add remembering blocks that the player has revealed proximity #281

VanyaNexus opened this issue Apr 9, 2023 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@VanyaNexus
Copy link

Description

If a player loaded blocks that were hidden through proximity, then when loading a chunk, the player again needs to load them all within his radius.

Proposed Behaviour

I propose to add a time setting in the config, how long the player will not need to update the blocks again, and if any player sets or changes these blocks again, then remove them from memory and the player will again need to see and open them

Extra Details

No response

@VanyaNexus VanyaNexus added the enhancement New feature or request label Apr 9, 2023
@NgLoader NgLoader self-assigned this Apr 14, 2023
@NgLoader

This comment was marked as outdated.

@Ingrim4
Copy link
Member

Ingrim4 commented Apr 15, 2023

Sounds like a great idea only problem being it interferes with the cache system because all chunks once in the cache are read-only and can't be modified. Therefore this would involve modifying the chunk every time it gets send which would make the cache obsolete. I do plan to phase out the cache in the near future since it's the source of most of the current problems with orebfuscator. That's why this can only be added once the cache got removed and or reworked to the point where this is possible without a big performance impact.

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

No branches or pull requests

3 participants