-
Notifications
You must be signed in to change notification settings - Fork 2
Configurations
Tip
To open the config, press Alt + ]
The configuration might look intimidating, but we'll break it all down step by step.
The distance at which unscanned chunks stop rendering (while scanning, you see yellow planes - these are the chunks that need to be scanned; this is the limit for them). Increasing this number will lower your FPS.
If you enable this option, chunks beyond the render distance will still be displayed, but on your HUD instead of in the game world. Enabling this option will lower your FPS.
Chunks are rendered relative to the player's camera. If you fly up, they will rise with you. A negative offset allows you to always see them below you.
You can adjust the color and transparency.
The rendering limit for blocks highlighted by the scan. Default is -1 = no limit.
You can change the color and transparency of the highlighted blocks.
Toggles the rendering of faces for all scanned areas. Turning this off will slightly increase FPS.
The color of the faces.
The distance at which blocks will not be rendered fully, but only as 2 perpendicular planes. LOD2 is 1 plane facing the player.
LOD2 - horizon. At this distance, blocks will be rendered at the player's camera level (on the horizon) for better visibility. However, the next setting disables this behavior.
Switches the rendering of blocks beyond the LOD2 distance to the HUD. This is much more noticeable because the squares don't shrink with distance and don't disappear from the render as you move further away.
If multiple blocks are located together (e.g., obsidian in lava lakes), the inner faces between them won't be visible. However, this increases CPU and memory load because adjacent blocks need to be merged into a single entity. It's hard to say exactly how this affects performance, as it balances the load between the CPU and GPU. You can toggle it and check the difference (for example, using the "Show render time in HUD" setting in the HUD section, which will be covered later).
Inside the mod, a loop constantly runs, pulling one chunk from the queue every n milliseconds to scan it. Lowering this setting makes the scan faster, but might negatively impact performance. I set it to 2 and it's fine for me, but your mileage may vary. 10 is the "golden mean".
When a setBlockState event occurs in the world on the client side, the chunk where it happened is updated. Usually, chunk updates only happen from player actions. This affects the chunk scanning queue; if there are many updates in loaded chunks, the queue might get clogged.
If enabled, upon joining a server, a message will indicate whether it supports server-side scanning.
You can assign a keybind to look at a random highlighted block when pressed (probably not needed anymore).
Toggles the entire rendering. Can be assigned to a keybind.
The keybind that opens this window. Default is Alt + ]
Toggles the HUD rendering.
Shows the time spent on world rendering and HUD rendering in milliseconds. Useful for performance testing. Milliseconds are rounded to 3 decimal places.
Relative offset of the HUD lines from its anchor point.
The side of the screen to which the HUD will be anchored.
You can change the HUD scale.
The server config is set via the /scanset command. You can view parameter values by typing /scanset , and change them with /scanset .
After making changes, you need to type /scanset save. /scanset reset will revert them to default, and you need to save after that as well.
There are several parameters:
- budget - server-side scanning runs on the same thread as the server itself. This parameter changes the number of milliseconds available for scanning per second.
Below are parameters for specific functions, I don't see the point in detailing them
- nbt
- chunks
- packets
- deltaPos
- pendingNbt
- maxSelectedBlock - once this number of highlighted blocks is reached, the scan will stop. Can be increased.