Orebfuscator 4.0.9

Details

  • Filename
    orebfuscator-4.0.9-SNAPSHOT.jar
  • Uploaded by
  • Uploaded
    May 2, 2016
  • Size
    79.57 KB
  • Downloads
    1,065
  • MD5
    deca2f0ab86e33a473d93f49eabddb86

Supported Bukkit Versions

  • 1.9

Changelog

Release notes

Sponsored by DevotedMC @ play.devotedmc.com (Join us!) we are proud to offer another release of Orebfuscator compatible with CraftBukkit/Spigot for Minecraft version 1.9.x.

This release has no compatibility with older versions of Minecraft, it will only work in 1.9 or later releases of CraftBukkit compatible servers. For 1.8, use Orebfuscator 3.0.6 (see releases for pre-builds).

This was compiled using Java 7.

Warning This is an Alpha release. Not everything has been tested at scale, and issues may remain. Please, please, open a new issue with as many details as you can provide if you encounter a problem.

New Features / Fixes

  • Fixed crash when chunk section (16 x 16 x 16) has more than 127 different block types

  • Implemented different "transparent block" lists for Engine Mode 1 and Engine Mode 2. For now only difference is with lava block, for mode 1 it is non-transparent, for mode 2 it is transparent.

  • Implemented possibility to specify which blocks are transparent and not in the config file, sections: TransparentBlocks and NonTransparentBlocks.

  • Fix which may have solved java.util.ConcurrentModificationException

  • Fix for phantom blocks (visible after chunk reloaded) when player is digging straight line on the chunk border. Details:
    It was happening because the player is not changing neighbor chunks (and therefore its hash code stayed the same) while mining, but since border blocks from another chunk might have been changed to air then some border blocks from "unchanged chunk" must be deobfuscated, but cache prevented this. Fix involved invalidating these "neighbor" caches.

Known Issues

Many internals were changed to address the java.util.ConcurrentModificationException reports; we cannot guarantee it is fixed, but we strongly believe the situation should be improved. We covet reports of either success or failure.

Next scheduled release will be May 8th, unless a critical bug is found and fixed.

We will continue to test the various engine modes and configurations, but we covet your input as well.

Unknowns

We do no yet have a ton of at-scale performance metrics. If you run a large server, we'd be especially grateful if you could share your timings report with us. In our smaller scale tests (around a dozen players) there did not seem to be any performance impact.