OtherDrops 2.8b.573
CraftBukkit 1.7.9 (no idea build number)

message.radius
Doesn't appear to be following the distance set in the configuration file.
If it were possible to set a custom radius for this, that would be lovely but I see no where that is possible either.

This is what I'm talking about it not following:

= Misc ==

= Override explosion cap (normally capped at max power 100f to avoid crashing server)
override_explosion_cap: false
= Action radius - radius to consider for message, potioneffect, sound, damage & pset actions
action_radius: 50

As far as a configuration display/setup when the user creates one, I'm afraid I'm not much help there... Outside of (message.radius: "message here"/{radius defined}) I can't think of anything that would be simple enough. Unless you did (custom.radius: {radius defined})

Will test message.radius. Custom radius isn't possible yet, still thinking
about best way to do custom radius per message but could add a global
custom radius in the meantime.

On 26/06/2014 12:25 pm, "Foxtail" [email protected] wrote:

OtherDrops 2.8b.573
CraftBukkit 1.7.9 (no idea build number)

message.radius
Doesn't appear to be following the distance set in the configuration file.
If it were possible to set a custom radius for this, that would be lovely
but I see no where that is possible either.

—
Reply to this email directly or view it on GitHub.

Unless there's already a global custom radius, I may have already added
this? :)
On 26/06/2014 1:16 pm, "Zarius Tularial" [email protected] wrote:

Will test message.radius. Custom radius isn't possible yet, still
thinking about best way to do custom radius per message but could add a
global custom radius in the meantime.

On 26/06/2014 12:25 pm, "Foxtail" [email protected] wrote:

OtherDrops 2.8b.573
CraftBukkit 1.7.9 (no idea build number)

message.radius
Doesn't appear to be following the distance set in the configuration
file.
If it were possible to set a custom radius for this, that would be
lovely but I see no where that is possible either.

—
Reply to this email directly or view it on GitHub.