diff options
| author | Brettflan <dsr@fenrisoft.com> | 2011-02-03 06:35:36 -0600 |
|---|---|---|
| committer | VictorD <victor.danell@gmail.com> | 2011-02-03 22:07:34 +0100 |
| commit | 2f2bc28915f6b71e818c195e0e8e004bdf228ccd (patch) | |
| tree | f203fe1873c9eef59e3df6659146668047ca5ea5 /pom.xml | |
| parent | dde3f5b47416106afea9a941154b49f680efcdb9 (diff) | |
| download | craftbukkit-2f2bc28915f6b71e818c195e0e8e004bdf228ccd.tar craftbukkit-2f2bc28915f6b71e818c195e0e8e004bdf228ccd.tar.gz craftbukkit-2f2bc28915f6b71e818c195e0e8e004bdf228ccd.tar.lz craftbukkit-2f2bc28915f6b71e818c195e0e8e004bdf228ccd.tar.xz craftbukkit-2f2bc28915f6b71e818c195e0e8e004bdf228ccd.zip | |
Fixes placement cancellation of single-step blocks, such as in protected areas like the spawn area.
The first line edited fixes it so other blocks placed on a single-step block aren't considered (only single-step blocks), and so that they're only considered when placed on the top face of the existing single-step block.
The second section of changed code keeps the final world.setTypeIdAndData() call from being incorrectly applied if it was indeed a single-block placed on an existing single-block.
Best way to test before and after is to put a bunch of single-step blocks in the spawn area as an Op, then de-Op yourself and try placing more blocks (single-step and otherwise, for example I also tested dirt blocks) on the sides and tops of the ones which you previously added as an Op.
Diffstat (limited to 'pom.xml')
0 files changed, 0 insertions, 0 deletions