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

config question + all blocks list #366

Open
DrRek opened this issue Mar 27, 2024 · 3 comments
Open

config question + all blocks list #366

DrRek opened this issue Mar 27, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@DrRek
Copy link

DrRek commented Mar 27, 2024

Description

*** Not really a suggestion but some questions that might be useful also for others. ***

Hey, I've some basic question on this amazing plugin that I think can be helpful to know also for other people planning to use it

I'm on a vanilla server and my goal is to make it harder for the people to use x-ray to find bases to grief.

To achieve that, I want to add as many blocks as possible to the proximity and the obfuscation features.

So that if people try to use x-ray with special setting to find for example crafting benches, wood or any other block that might be present in a base then they cannot identify any of those.

Does this approach make sense and fits within the use cases of this proxy or is there a better one?
Does adding too many hidden blocks impact significantly on performance to the best of your knowledge?
My server is 1.20.4, how can I get a list of all the possible blocks? Including for example all various torches (not just Minecraft:torch) and blocks with multiple states

Thanks!

Proposed Behaviour

n/a

Extra Details

No response

@DrRek DrRek added the enhancement New feature or request label Mar 27, 2024
@Ingrim4
Copy link
Member

Ingrim4 commented Jun 23, 2024

Sorry for the late response.

Response to Your Questions:

  1. Does this approach make sense and fit within the use cases of this proxy or is there a better one?

    • Yes, your approach does make sense. Adding more blocks to the proximity and obfuscation features can help deter x-ray users from identifying bases by masking key blocks like crafting benches and wood. This aligns with the intended use of the plugin.
  2. Does adding too many hidden blocks impact performance significantly to the best of your knowledge?

    • Adding a large number of blocks can indeed impact performance. Specifically, it will increase memory usage since the location of each proximity block needs to be stored per player. Additionally, processing time will increase as the plugin needs to check each block for occluding neighboring blocks. Therefore, while there's no technical limitation to adding all blocks, we recommend adding only as many blocks as necessary to balance performance and obfuscation.
  3. How can I get a list of all the possible blocks in Minecraft 1.20.4, including variations like different types of torches?

    • You can obtain a list of all blocks, including their various states, from the Minecraft wiki.

Recommendations:

  • We won't be adding an option to include all blocks by default because we don't want to encourage this practice due to potential performance issues.
  • You are more than welcome to customize the config and add as many blocks as you see fit. The more powerful your server hardware, the more blocks you can add without experiencing significant performance degradation.

@Chevels
Copy link

Chevels commented Oct 25, 2024

Sorry for the late response.

Response to Your Questions:

1. **Does this approach make sense and fit within the use cases of this proxy or is there a better one?**
   
   * Yes, your approach does make sense. Adding more blocks to the proximity and obfuscation features can help deter x-ray users from identifying bases by masking key blocks like crafting benches and wood. This aligns with the intended use of the plugin.

2. **Does adding too many hidden blocks impact performance significantly to the best of your knowledge?**
   
   * Adding a large number of blocks can indeed impact performance. Specifically, it will increase memory usage since the location of each proximity block needs to be stored per player. Additionally, processing time will increase as the plugin needs to check each block for occluding neighboring blocks. Therefore, while there's no technical limitation to adding all blocks, we recommend adding only as many blocks as necessary to balance performance and obfuscation.

3. **How can I get a list of all the possible blocks in Minecraft 1.20.4, including variations like different types of torches?**
   
   * You can obtain a list of all blocks, including their various states, from the [Minecraft wiki](https://minecraft.wiki/w/Java_Edition_data_values/Blocks).

Recommendations:

* We won't be adding an option to include all blocks by default because we don't want to encourage this practice due to potential performance issues.

* You are more than welcome to customize the config and add as many blocks as you see fit. The more powerful your server hardware, the more blocks you can add without experiencing significant performance degradation.

Hello! :)
I have been using OFC since it exists and since there is the raycast option I ask myself the following question:
Should I add all the blocks that I want to hide in both proximity hider and obfuscation? I am mainly talking about the blocks used to identify redstone systems and bases.

Subsidiary question:
Does raycast allow to counter ESP and the Freecam mod? (for blocks/tile entities added in the config of course)
In reality I should have asked this question first so that my first question makes more sense; my goal being to try to counter ESP/Freecam mods.
In the past you told me that it was not possible with OFC but at that time there was no raycast option yet

@Ingrim4
Copy link
Member

Ingrim4 commented Oct 25, 2024

You can add blocks to both the obfuscation and proximity hider lists. Blocks will obfuscate when surrounded by opaque blocks, defaulting to proximity hiding otherwise. Adding blocks to both lists may slightly impact performance, as each block in the obfuscation list checks its six neighboring blocks. Proximity hiding is less intensive; however, if used alone, memory usage increases drastically due to tracking each proximity-hidden block per player and loaded chunk (each block per player is roughly 4 bytes of memory).

We provide a brief explanation of raycasting in our wiki here. Since raycasting only affects when proximity blocks are deobfuscated, it may not directly counter ESP or Freecam mods. Could you elaborate on how you see raycasting addressing these mods? This context would help clarify if any adjustments to our approach might support your goal more effectively.

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