phaed420/PreciousStones — Issue #89: [Feature Request] 'custom-maxvolume' field flag
Author: zanetheinsane
Created: 2011-10-13 11:37:14+00:00
State: open

I would like to see a 'custom-maxvolume' flag that would allow you define the maximum volume for the cuboid instead of relying on the computation used in CuboidEntry.getMaxVolume(). In getMaxVolume() you would simply check to see if field.getSettings().getMaxVolume() is greater than 0 or some other non-initialized value and return that instead.

The rationale behind this is that if a player wanted to place a cuboid field next to another player's cuboid field currently the only way to do so is to make sure that their pstone is placed a number of blocks away equal to the radius+1 so that the fields don't overlap in the case of 'no-conflict:false' fields.

The problem with this is that in order to give players sufficient volume to design their cuboids you have to increase the radius (or height). A block with a radius a 20 would mean a player could wish to protect an area that is near another protected field (but outside of it) but may be unable to do so because they are unable to put down their pstone due to the radius-check, even though they may be technically able to design a cuboid that does not overlap the field. The only other solution is to design pstones with a small radius and rely on players having to place multiples of them, which seems like a very limiting solution.

With a maxVolume setting you could design a pstone with a radius of 0 but a custom maxVolume, allowing a player to place a pstone anywhere next to an adjacent field but still able to design a valid cuboid.

The only issue with this proposal is a bug I have submitted separately where finished cuboids aren't validated to make sure they don't overlap conflicting fields.