当前版本:1.9.4.1
请阅读以下内容,而不是仅仅点击右上角的下载按钮然后自己去摸索。
Bukkit 团队不支持经过修改的 Craftbukkit 版本。在向 Bukkit 团队报告错误或崩溃之前,请先卸载 OTCO 进行测试。
功能特性:
修改前:

修改后(假矿石):

在将完整的区块数据包发送给客户端之前对其进行编辑。该过程不在主服务器线程中运行,因此只要您的服务器没有耗尽所有核心资源,它应该对性能的影响微乎其微。所有相邻没有空气、水、岩浆或玻璃等其他透明方块的矿石方块和箱子,或者所有其他透明方块,都会作为石头方块发送给客户端。当矿石方块或箱子旁边的方块被移除时,会强制向客户端发送方块更新,从而使真实方块变得可见。或者,可以将所有石头方块作为矿石方块发送出去,然后在玩家挖掘时更新为显示为石头方块。
这应该在某种程度上降低 X-ray 作弊的效果,从他们那里隐藏世界中大多数矿石以及显眼的埋藏宝箱。为了高效地实现这一点,必须修改部分实际的服务器代码。下载包中包含一个插件和一个用于修补服务器 jar 文件的类文件。为了让它与使用 Spout 编辑数据包的其他插件兼容,您必须下载并使用专为 Spout 设计的版本。
安装说明
CraftBukkit 安装方法:
- 将 rawcritics_ore_obfuscation_installer.jar 添加到您的服务器 plugins 文件夹中。
- 启动服务器。
- 等待修补完成。
- 从您的 plugins 文件夹中移除 rawcritics_ore_obfuscation_installer.jar
- 将 rawcritics_ore_obfuscation_plugin.jar 添加到您的 plugins 文件夹中
- 如果修补程序无法重命名您的服务器 jar 文件,请将 "rawcbpatchtemp.jar" 重命名为您的服务器 jar 应有的名称。
- 启动服务器。如果插件没有发送任何错误,则说明安装成功。
如果您熟悉操作,也可以使用 7-zip 等工具手动复制包含的 "net" 和 "org" 文件夹及其中的所有文件到服务器 jar 文件中。如果是手动操作,您需要删除 META-INF 目录中的 BUKKIT.SF 和 BUKKIT.RSA 文件。
适用于 1.7 以下版本(CraftBukkit 旧版)的安装方法:
- 使用任何能够编辑 jar 文件内容的程序,将附带的 Packet51MapChunk.class 和 ChunkCompressionThread.class 覆盖到旧文件中。只需将这些文件夹“net”和“org”添加到 jar 包中即可完成此操作。如果需要,您可以先备份 server.jar/net/minecraft/server/Packet51MapChunk.class 和 server.jar/org/bukkit/craftbukkit/ChunkCompressionThread.class。常用的此类程序包括 WinRar 和 7-zip。
- 将 rawcritics_ore_obfuscation_plugin.jar 添加到您的 plugins 目录中
- 如果启动服务器时没有发送任何错误,则说明安装成功
Spout 插件的安装方法:
- 将 rawcritics_ore_obfuscation_plugin_spout.jar 复制到您的 plugins 文件夹中
- 必须使用 Spout
- 请勿安装来自其他版本的类文件,仅使用 Spout 插件
配置
示例 oo-engine-mode.txt 配置文件:
#选择您要运行的混淆引擎。
#1 隐藏所有旁边没有透明方块的所有矿石和箱子。
#2 无论旁边是否有透明方块,都会隐藏所有矿石,并隐藏旁边没有透明方块的箱子。矿石在被挖掘或右键点击时会重新出现。
#3 仅检查矿石的光照等级,如果处于完全黑暗中则隐藏它们。这是最快的引擎模式。
#4(默认值)将所有旁边没有相邻透明方块的石头和矿石转化为高度 20 以上的铁矿石和下方的钻石矿石。将所有旁边没有相邻透明方块的箱子转化为石头。
#5 随机将旁边没有相邻透明方块的石头转化为矿石。比模式 4 稍微更占用处理资源。
enginemode=4
#视为透明的方块 ID 列表,以逗号分隔。
transparentIds=8,9,10,11,20,27,28,37,38,39,40,44,50,53,55,63,64,65,66,67,68,69,71,75,76,77,78,79,85,96,101,102,104,105,106,107,108,109,113,114,115,131,132,139,140,141,142,143,144,145
#构成您世界大部分地面的方块 ID。除非您拥有自定义的世界生成,否则应为代表石头的 1。
maingroundblock=1
#为矿石发送方块更新的范围半径。较高的值会使用更多的处理能力和带宽,但对于连接较差的玩家体验更好。默认值为 2,建议不超过 4。
oreupdateradius=2
#何时发送玩家矿石更新。0(默认)在方块破坏事件时触发。1 在方块受损时触发,这样可以略微降低延迟的感知,但会增加主服务器线程的处理开销。
oreupdatemode=0
#如果为 true,则在爆炸后检查暴露的矿石。如果你有一个用于禁用苦力怕方块伤害的插件,根据该插件的实现方式,禁用此功能可能节省处理资源。
checkexplosions=true
#通过将所有没有相邻透明方块的箱子变成石头(直到被揭开)来隐藏所有引擎模式下的箱子。
hidechests=true
#如果为 true,管理员(ops.txt 中的玩家)将不会对其运行混淆器。
disableforops=false
#如果为 true,将为每个世界使用单独的配置文件。要为特定世界创建配置,请复制此文件并将其重命名为 YourWorldName.txt(例如 World1.txt、World1_Nether.txt 等)。
usemultipleworldconfigurations=false
引擎模式:
推荐使用默认的矿石混淆引擎,但你可以在配置文件中更改它:
\plugins\RawcriticsOreObfuscationPlugin\oo-engine-mode.txt
模式 1 - 隐藏所有没有相邻透明方块的矿石和箱子。
模式 2 - 隐藏所有矿石,无论是否有相邻方块,直到移除其旁边的方块或右键点击它们;如果没有相邻透明方块,则隐藏箱子。
模式 3 - 检查矿石的光照等级,如果矿石方块的光照等级为 0,则将其隐藏。
模式 4 - (默认)将所有没有相邻透明方块的石头和矿石发送为高度 20 以上的铁矿,以及以下的钻石矿。这意味着即使对方块类型进行特定过滤,也无法看到任何在洞穴中未暴露的矿石,且 xray 用户无法判断洞穴中暴露的铁矿或钻石矿是真实的还是虚假的。唯一的缺点是,任何有延迟的玩家在挖掘时必须等待才能知道他们挖到的是真实矿石还是只是石头。
模式 5 - 将石头随机显示为某种矿石。比模式 4 稍微更消耗处理资源。
其他配置:
在同一配置文件中编辑 transparentIds=8,9,10,11,20,27,28,37,38,39,40,44,50,53,55,63,64,65,66,67,68,69,71,75,76,77,78,79,85,96,101,102,104,105,106,107,108,109,113,114,115,131,132,139,140,141,142,143,144,145,允许你选择哪些方块 ID 被视为透明。空气始终被视为透明以优化性能。
maingroundblock=1 是主方块 ID,即矿石周围地面由哪种方块构成。在大多数世界中,这通常是石头(1)。
oreupdateradius 选项设置了移除方块周围发送方块更新以处理矿石的半径。较高的值会占用更多的处理能力和带宽,但对于连接状况不佳的玩家体验更好。默认值为 2,建议不要设置高于 4。
如果 checkexplosions 为 true,则在爆炸后会检查暴露的矿石。如果你有一个用于禁用苦力怕方块损坏的插件,根据该插件的具体实现方式,禁用此功能可能会节省处理能力。
如果 hidechests 为 true,则没有透明方块相邻的箱子会被隐藏为石头,直到它们旁边的某个方块被移除(或运行了引擎针对箱子的特定逻辑)。如果已经使用 Lockette 等插件保护箱子,可以禁用此功能。
如果 disableforops 为 true,则 obfuscater 不会对在 ops.txt 文件中的玩家发送的数据包进行处理。
如果 usemultipleworldconfigurations=true,则将使用每个世界的独立配置文件。oo-engine-mode.txt 中的设置将作为没有特定配置的世界的默认值。世界的配置文件通过在 oo-enginemode.txt 相同位置创建的 you_world_name.txt 文件来指定(例如,名为 world3 的世界对应 world3.txt,名为 myminecraftworld_nether 的世界文件夹对应 myminecraftworld_nether.txt,依此类推)。
世界专属配置文件
世界专属配置文件(yourworldname.txt)包含以下选项:
#选择要运行的混淆引擎。
#0 为此世界禁用矿石混淆。
#1 隐藏所有旁边没有透明方块的矿石和箱子。
#2 隐藏所有矿石,无论其旁边是否有透明方块,并隐藏旁边没有透明方块的箱子。矿石在被挖掘时或右键点击时会重新出现。
#3 仅检查矿石的光照等级,如果处于完全黑暗中则隐藏它们。最快的引擎模式。
#4(默认)将高度 20 以上且旁边没有透明方块的石头和矿石全部转换为铁矿石,高度 20 以下转换为钻石矿石。将旁边没有透明方块的箱子转换为石头。
#5 随机将没有相邻透明方块的石头转化为矿石。比选项4更耗费性能。
enginemode=4
#构成你世界大部分地面的方块的 ID。除非你有自定义的世界生成,否则应为 Stone 的 1。
maingroundblock=1
#如果为 true,则在爆炸后检查暴露的矿石。如果你有一个用于禁用苦力怕方块伤害的插件,根据该插件的编写方式,禁用此选项可能会节省处理资源。
checkexplosions=true
#通过将所有没有相邻透明方块的箱子变为石头(直到被 uncover 为止),在所有引擎模式下隐藏箱子。
hidechests=true
命令(用于测试)
所有这些命令仅限 OP 使用。
/otco - 列出命令
/otco-reload - 重新加载配置文件。请注意,在更多区块发送到你的客户端之前,你将看不到更改!
/otco-configs - 列出已加载的配置文件及其是否正在用于某个世界
/otco-toggleopdisable - 临时切换是否对 OP 禁用混淆。若要永久更改,你必须编辑配置文件。
/otco-resendmychunk - 向你所在的当前位置周围的区块重新发送数据到你的客户端。
/otco-reloadmychunk - 保存并重新加载你当前站立的区块。
因为有些人问起
任何金额的捐赠都表示感谢!(并且在你需要时,我会提供更为详细的支援!)
Current Version: 1.9.4.1
Read below instead of just clicking download in the top right and trying to figure it out on your own.
The Bukkit team does not support modified versions of Craftbukkit. Test with OTCO uninstalled before reporting bugs or crashes to the Bukkit team.
Features:
- Rewrites chunk packets sent to the client to hide unexposed ores
Before:

After (Fake Ore):

Edits the whole chunk data packets before they are sent out to clients. It's not run in the main server thread, so as long as your server is not using up all of its cores, it should cause little performance difference. Either all ore blocks and chests that have no adjacent air, water, lava, or glass, or other transparent block block are sent to the client as stone blocks. When a block is removed next to an ore block or chest, a block update is forced on the client, causing the real block to become visible. Or, all stone blocks can be sent out as ore blocks, then updated to show as stone blocks as a player mines.
This should lower the effectiveness of x-rayers somewhat, hiding a majority of any world's ores, and notably buried chests, from them. To do this efficiently, part of the actual server code had to be modified. The download contains both a plugin, and a class file to patch a server jar with. For it to work with other plugins that edit packets using Spout, you must download and use the Spout specific version instead.
Installation
Installation for CraftBukkit:
- Add rawcritics_ore_obfuscation_installer.jar to your server plugins.
- Start server.
- Let patching finish.
- Remove rawcritics_ore_obfuscation_installer.jar from your plugins folder
- Add rawcritics_ore_obfuscation_plugin.jar to your plugins folder
- If patcher could not rename your server jar, rename "rawcbpatchtemp.jar" to what your server jar should be.
- Start server. If the plugin doesn't send any errors, it worked.
You could also manually copy included "net" and "org" folders and all contained files into your server jar using a utility like 7-zip, if you are comfortable with that. You will have to delete BUKKIT.SF and BUKKIT.RSA from the META-INF directory if you do it manually.
Installation for Versions Older Than 1.7 (CraftBukkit Legacy Versions):
- Use any program that can edit the contents of jar files to copy the included Packet51MapChunk.class and ChunkCompressionThread.class over the old ones, the folders "net" and "org" can simply be added to the jar to do this. You can backup server.jar/net/minecraft/server/Packet51MapChunk.class and server.jar/org/bukkit/craftbukkit/ChunkCompressionThread.class first if you feel the need. Common programs that you could do this with include WinRar and 7-zip.
- Add rawcritics_ore_obfuscation_plugin.jar to your plugins directory
- If it doesn't send any errors when you start your server, it worked
Installation for Spout:
- Copy rawcritics_ore_obfuscation_plugin_spout.jar into your plugins folder
- Must be using Spout
- Do not install the class files from any other version, only use the Spout plugin
Configuration
Example oo-engine-mode.txt Configuration File:
#Choose the obfuscation engine you want to run.
#1 Hides all ores and chests that don't have a transparent block next to them.
#2 Hides all ores regardless of whether they have a transparent block next to them, and hides chests that don't have a transparent block beside them. Ores reappear when dug, or when they are right clicked on.
#3 Only checks light levels for ores and hides them if they are in total darkness. Fastest engine mode.
#4 (default) Turns all stone AND ores without adjacent transparent blocks into iron ore above height 20, and diamond ore below. Turns chests without adjacent adjacent transparent blocks to stone.
#5 Randomly turns stone without adjacent transparent blocks into Ore. Slighly more process intensive then 4.
enginemode=4
#List of block ids to count as transparent, seperated by commas.
transparentIds=8,9,10,11,20,27,28,37,38,39,40,44,50,53,55,63,64,65,66,67,68,69,71,75,76,77,78,79,85,96,101,102,104,105,106,107,108,109,113,114,115,131,132,139,140,141,142,143,144,145
#The id of the block the majority of your world's ground consists of. Should be 1 for Stone unless you have a custom worldgen.
maingroundblock=1
#Radius around removed blocks that block updates are sent for ores. Higher values use more processing power and bandwith but are nicer for players with bad connections. Default 2, recommended no higher then 4.
oreupdateradius=2
#When to send player ore updates. 0 (default) is on block break events. 1 is on block damage, which can make latency slightly less noticable, but uses more processing power in the main server thread.
oreupdatemode=0
#Checks for exposed ores after explosions if true. If you have a plugin for disabling block damage from creepers, depending on how the plugin is written in might save processing power to disable this.
checkexplosions=true
#Hides chests in all engine modes by turning chests without adjacent transparent blocks into stone until uncovered.
hidechests=true
#If true, Ops (players in ops.txt) will not have the obfuscator ran for them.
disableforops=false
#If true, then seperate configurations for each world will be used. To make a configuration for a specific world, make a copy of this file and rename it YourWorldName.txt (i.e. World1.txt, World1_Nether.txt, etc.)
usemultipleworldconfigurations=false
Engine Modes:
The default ore obfuscation engine is recommended, but you can change which one in the config at
\plugins\RawcriticsOreObfuscationPlugin\oo-engine-mode.txt
Mode 1 - Hides all ores and chests that don't have an adjacent transparent block.
Mode 2 - Hides all ores regardless of adjacent block until a block by them is removed or they are right clicked, hides chests if they don't have an adjacent transparent block
Mode 3 - Checks light levels of ores, if an ore block has a light level of 0 it is hidden.
Mode 4 - (Default) Sends all stone and ores without an adjacent transparent block as iron ore above height 20, diamond below. This means even with specific filtering of block types, no ore that isn't exposed in caves can be seen at all, and an xrayer can't tell if iron ore or diamond ore exposed in caves is real or not. Only downside is that any players mining with any latency will have to wait to see whether they're mining real ore or just stone.
Mode 5 - Sends stone as a random ore. Slightly more process intensive than 4.
Other Configuration:
Editing transparentIds=8,9,10,11,20,27,28,37,38,39,40,44,50,53,55,63,64,65,66,67,68,69,71,75,76,77,78,79,85,96,101,102,104,105,106,107,108,109,113,114,115,131,132,139,140,141,142,143,144,145 in the same config file allows you to choose which block ids are counted as transparent. Air always is for performance.
maingroundblock=1 is the id of the main block the ground surrounding your ores consists of. In most worlds, this would be stone (1).
The oreupdateradius option sets the radius around removed blocks that block updates are sent for ores. Higher values use more processing power and bandwith but are nicer for players with bad connections. 2 is the default option, recommended to set it no higher than 4.
If checkexplosions is true, exposed ores are checked for after explosions. If you have a plugin for disabling block damage from creepers, depending on how that plugin is written in might save processing power to disable this.
If hidechests is true, chests without any transparent blocks adjacent to them are hidden as stone until a block next to them is removed (or whichever specific logic is performed by an engine for chests is ran). Might disable if Lockette, etc, is already protecting chests.
If disableforops is true, the obfuscater will not be ran on packets sent to those who are in your ops.txt file.
If usemultipleworldconfigurations=true, then seperate configurations for each world will be used. The settings in oo-engine-mode.txt are used as the defaults for a world without a specific configuration. A configuration for a world is specified by a you_world_name.txt file in the same location as oo-enginemode.txt (So a world called world3 would be world3.txt, a world folder named myminecraftworld_nether would be myminecraftworld_nether.txt, and so forth).
World Specific Configuration File
A world specific configuration file (yourworldname.txt) has the following options:
#Choose the obfuscation engine you want to run.
#0 Ore Obfuscation is disabled for this world.
#1 Hides all ores and chests that don't have a transparent block next to them.
#2 Hides all ores regardless of whether they have a transparent block next to them, and hides chests that don't have a transparent block beside them. Ores reappear when dug, or when they are right clicked on.
#3 Only checks light levels for ores and hides them if they are in total darkness. Fastest engine mode.
#4 (default) Turns all stone AND ores without adjacent transparent blocks into iron ore above height 20, and diamond ore below. Turns chests without adjacent adjacent transparent blocks to stone.
#5 Randomly turns stone without adjacent transparent blocks into Ore. Slighly more process intensive then 4.
enginemode=4
#The id of the block the majority of your world's ground consists of. Should be 1 for Stone unless you have a custom worldgen.
maingroundblock=1
#Checks for exposed ores after explosions if true. If you have a plugin for disabling block damage from creepers, depending on how the plugin is written in might save processing power to disable this.
checkexplosions=true
#Hides chests in all engine modes by turning chests without adjacent transparent blocks into stone until uncovered
hidechests=true
Commands (Useful for Testing)
All these commands are Op only.
/otco - Lists commands
/otco-reload - Reload the configuration file. Keep in mind that you won't see changes until more chunks are sent to your client!
/otco-configs - Lists loaded configuration files and whether they are being used for a world
/otco-toggleopdisable - Toggle the obfuscation being disable for Ops temporarily. You have to edit the configuration to change it permanently.
/otco-resendmychunk - Resends the chunks around where you are standing to your client.
/otco-reloadmychunk - Saves and reloads the chunk you are standing in.
Because some of you have asked
Any amount appreciated! (And I'll be sure to provide more in detail support when you need it!)
评论 0
登录后参与评分
还没有评论,来抢沙发吧