[SEC] Orebfuscator 1.9.3 - Anti X-RAY [CB1.4.5-CB1.5.2]

yep its true i noticed it today on my server

1.4.6 is very slow. With 30 people online do not load chunks.

//edit
Where can I find a working link to 1.4.5?

Is there a way to tell who is using X-ray with this mod?

Some kind of log that I can read?

jeffro1001: No. The plugin does not DETECT x-rayers, it only makes their life hard by sending fake ore blocks.

And thats better than detecting X-rayers, because with fake ore you are basically PREVENTING X-rayers.
But the default config is not top-of-the-notch you need to tweak it a bit so you find a good balance between server CPU utilisation and anti-Xray.
Cranking it too high makes the server laggy, cranking it too low exposes your server to X-rayers. So you need to find a good point in-between, this depends on server hardware and maximum player limit setting.

Thanks.

Just so I understand..
Server CPU utilization has nothing to do with how many players are using the X-ray cheat?
Meaning, your server will work just as hard whether everyone connected is using X-ray, or no one is using X-ray?

Sorry guys, minor thread bug with 1.4.6

Please use 1.4.5 for now (hosted on bukkitdev)
I will fix and post 1.4.7 soon.

Please test 1.4.7! Attempted to fix the lag from 1.4.6.

My server don't support it, some user who don't use X-ray saw diamand instead stone.
More, my server lag so much, I have the "Can't keep up, did ...."

Reverting back to 1.4.5.

Reverting back to 1.4.5.

It turns out that the experiential feature is a little too resource hungry...

Code:

2012-05-07 22:09:58 [INFO] Connection reset
2012-05-07 22:09:58 [SEVERE] java.net.SocketException: Broken pipe
2012-05-07 22:09:58 [SEVERE]    at java.net.SocketOutputStream.socketWrite0(Native Method)
2012-05-07 22:09:58 [SEVERE]    at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
2012-05-07 22:09:58 [SEVERE]    at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
2012-05-07 22:09:58 [SEVERE]    at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
2012-05-07 22:09:58 [SEVERE]    at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
2012-05-07 22:09:58 [SEVERE]    at java.io.DataOutputStream.flush(DataOutputStream.java:123)
2012-05-07 22:09:58 [SEVERE]    at net.minecraft.server.NetworkWriterThread.run(SourceFile:103)
2012-05-07 22:09:58 [SEVERE] java.net.SocketException: Broken pipe
2012-05-07 22:09:58 [SEVERE]    at java.net.SocketOutputStream.socketWrite0(Native Method)
2012-05-07 22:09:58 [SEVERE]    at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
2012-05-07 22:09:58 [SEVERE]    at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
2012-05-07 22:09:58 [SEVERE]    at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
2012-05-07 22:09:58 [SEVERE]    at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
2012-05-07 22:09:58 [SEVERE]    at java.io.DataOutputStream.flush(DataOutputStream.java:123)
2012-05-07 22:09:58 [SEVERE]    at net.minecraft.server.NetworkWriterThread.run(SourceFile:103)
2012-05-07 22:09:58 [INFO] kinnaj100 lost connection: disconnect.endOfStream

Doesn't seem to be caused by this plugin.

@jeffro1001 : Nope. The server cannot "see" if the client is using X-ray, so the server CPU/RAM utilisation is exactly the same, regardless of if your server have 100 X-rayers of 100 slots, or if your server have 100 legit players of 100 slots.

If your server still getting X-rayers even tough you have Orebfuscation, and your server becomes laggy of cranking up the settings, I would suggest you lower the MaxSlots/maxplayers setting of your server. Better with 50 legit players than 100 X-rayers.

I have same problem with chunks. When I updated orebfuscator I don't remember which version it started lagging. Then I put out from server tried another clients nothing good. When I put orebfuscator to my server it doesn't load chunks just very small piece and that's all.

OK
Thanks for the explanation.

@lishid: Is your plugin compatible to "Nolagg"? Because if I am running Nolagg togather with OFC the server gets "java.lang.OutOfMemoryError: Java heap space" after a while. If I disable Nolagg or OFC everything is working fine.
Ha! Haven't read the whole FAQ ... shame on me! I was using 1.4.5 OFC and Nolagg 1.83.
Yesterday a new update for Nolagg may fixed the problem... I will check this


@sebastiannielsen:
For me its quite hard to understand what the different options at the config.yml are doing....even though I read the wiki.
I am using these settings right now:

Code:

ConfigVersion: 1
Integers:
  EngineMode: 2
  UpdateRadius: 2
  InitialRadius: 1
  ProcessingThreads: 4
  MaxLoadedCacheFiles: 64
  ProximityHiderDistance: 8
  ProximityHiderID: 0
  ProximityHiderEnd: 255
Booleans:
  UseProximityHider: true
  UseSpecialBlockForProximityHider: true
  UpdateOnBreak: true
  UpdateOnDamage: true
  UpdateOnPhysics: true
  UpdateOnPiston: true
  UpdateOnExplosion: true
  UpdateOnHoe: true
  UpdateThread: true
  DarknessHideBlocks: true
  VerboseMode: false
  NoObfuscationForOps: false
  NoObfuscationForPermission: false
  UseCache: false
  Enabled: true
Lists:
  ObfuscateBlocks:
  - 14
  - 15
  - 16
  - 21
  - 54
  - 56
  - 73
  - 74
  DarknessObfuscateBlocks:
  - 52
  - 54
  ProximityHiderBlocks:
  - 23
  - 54
  - 58
  - 61
  - 62
  - 116
  RandomBlocks:
  - 5
  - 14
  - 15
  - 16
  - 21
  - 48
  - 56
  - 73
  DisabledWorlds:
  - themenwelt

My cpu load is round about ~25-35% even though the server is full (32 Players). So I think I could tweak it a bit that it would be harder for X-rayers and easier for legit players to find the right ores.
So increasing the UpdateRadius would one option to make it legit players easier to find ores around them... thats clear. But I do not understand why I should increase the InitialRadius. How could this give legit players an advantage or X-rayers an disadvantage?

Thanks for answering
GrillGuth

Increasing UpdateRadius to more than 2 usually doesn't improve much. It will be more taxing on network bandwidth though, and can help x-ray hackers slightly.

InitialRadius is used to initially obfuscate the world. You can think of it as how many layers of real stuff to show when the world is first sent to the player. Usually 1 is optimal, for speed, resources, and most protection. Increasing this will again, be ALOT more taxing on server resources and help x-ray hackers slightly.

These values should only be tweaked if most of your players are experiencing block lag. But if that's the case, you should consider upgrading network bandwidth

i make a and b
some problem

user and admins report the Problem independent


i use too Nolagg package

Code:

ConfigVersion: 1
Integers:
  EngineMode: 2
  UpdateRadius: 2
  InitialRadius: 2
  ProcessingThreads: 1
  MaxLoadedCacheFiles: 64
  ProximityHiderDistance: 8
  ProximityHiderID: 0
  ProximityHiderEnd: 255
Booleans:
  UseProximityHider: true
  UseSpecialBlockForProximityHider: true
  UpdateOnBreak: true
  UpdateOnDamage: true
  UpdateOnPhysics: true
  UpdateOnPiston: true
  UpdateOnExplosion: true
  UpdateOnHoe: true
  UpdateThread: true
  DarknessHideBlocks: true
  VerboseMode: false
  NoObfuscationForOps: true
  NoObfuscationForPermission: true
  UseCache: true
  Enabled: true
Lists:
  ObfuscateBlocks:
  - 14
  - 15
  - 16
  - 21
  - 54
  - 56
  - 73
  - 74
  DarknessObfuscateBlocks:
  - 52
  - 54
  ProximityHiderBlocks:
  - 23
  - 54
  - 58
  - 61
  - 62
  - 116
  RandomBlocks:
  - 5
  - 14
  - 15
  - 16
  - 21
  - 48
  - 56
  - 73
  DisabledWorlds: []

Try disabling cache with "/ofc disable cache"

uhm... I just got word from one of my players that.. well, this plugin is completly broken.

first off, he gave me this screenshot, which he said was taken approximately 3-5 days ago.
http://oi48.tinypic.com/oqww7d.jpg

This shows the plugin... well, not working in the slightest. Now, i cant verify that this is on MY server, nor that it was actually from a few days ago (because the config i used prior to this actually may have looked like this)

im gonna do some testing of my own. He says hes running CJB's mod and was able to completly bypass orebfuscator.

for reference, this is the configuration i have been using that would be active during the time frame that he claims the screen was taken
http://pastebin.com/1BXkMRqW

Welp, im off to install CBJ's mod and test on my test server.

Preliminary apologies if this is just a wild goose chase, in no way do i mean to insult your work

Though before i submit this, there is a good chance he revealed the ores prior to taking the screenshot, and wants me to remove orebfuscator (because that was a point he was making) so he can hop off CBJ's and get on one that isnt killed by noCheat+


... i sincerely hope thats not the case D:

nvm. its working fine. :l

we have testet no changes

Did you ask everyone to relog after disabling cache?

i will remove the folder an try it again

Ok just a quick question. why don't you turn all ores into stone instead of all stone into ore?

it does.

theres multiple engine types.

User See still hallucinations

Go with Engine mode 1.

ok i wait on Admins to Testing

Whenever i relog after turning ofc on no chunks are loading! help?
For all my players!

CB version, OFC version, plugin list, configuration file (please pastbin).