10-16-2014, 11:40 PM
There is no explicit chunk cache in MCS, because the entire cWorld is in fact a chunk cache.
If I were to write a plugin like this, I'd go about it this way:
- Install a post-generator hook that saves the entire chunk somewhere, and then processes it so that all the invisible blocks are ores.
- Install a player-digging hook that checks if the visibility has changed, and if so, restores the needed blocks from the "backup".
- In order to speed things up, I'd keep backups of the four chunks closest to the player loaded, so that the restoration process takes as little time as possible.
This will not be perfect, however, because the obfuscation cannot really process blocks on the chunk's edge - there is no neighbor data while generating. This could be worked around, if needed.
If I were to write a plugin like this, I'd go about it this way:
- Install a post-generator hook that saves the entire chunk somewhere, and then processes it so that all the invisible blocks are ores.
- Install a player-digging hook that checks if the visibility has changed, and if so, restores the needed blocks from the "backup".
- In order to speed things up, I'd keep backups of the four chunks closest to the player loaded, so that the restoration process takes as little time as possible.
This will not be perfect, however, because the obfuscation cannot really process blocks on the chunk's edge - there is no neighbor data while generating. This could be worked around, if needed.