Bukkit

@Atrelyu

I like the idea! But, sort of unfortunately, the Secure spell uses vanilla mechanics- in 1.8 Mojang added the ability to lock containers. It doesn't apply to doors or anything else.

You could use a similar mechanic with NPC's, though- at least for certain actions. I don't think the "command" trait supports item cost requirements but I could add that if it'd be useful (e.g. exchange item for a command). Denizens can do that out of the box, too, I think.

@Capehenrykid

Pastebin, please! Yikes- just delete the comment, please, I got what I needed.

Your problem is the PVP integration with MultiVerse- it looks like you have a bad MV config and the plugin is failing to load.

thread/WARN]: [Multiverse-Core] The world specified as the spawn world (null) did not exist!! [03:27:46] [Server thread/ERROR]: Could not pass event PlayerJoinEvent to Multiverse-Core v2.5-b691 org.bukkit.event.EventException at

@Capehenrykid

No- "An internal error has occurred" should never happen. There will be a corresponding error in your server logs that will help me figure out what's causing this- it will be something to do with the PVP integration of one of the plugins you've got.

If you could find that error (it will be a long Java stack trace) and put it on pastebin so I can see it, that would help a lot.

@Atrelyu

Well the thing with the "fill_wands" setting is it's kind of all or nothing. Once you have that turned on there's no way to make any other kind of wands.

I could probably make it better than that, so only certain wands get the "fill" behavior, but you could still have other one-off wands with specific spells, etc.

You can add vanilla enchantments to wands, like this:

https://github.com/elBukkit/MagicPlugin/blob/master/src/main/resources/defaults/wands.defaults.yml#L1325

@Kasamu

I've no idea, sorry, I've never used SkillAPI. I guess I assumed there was a way for it to give permissions or assign players to groups.

@Atrelyu

What I would suggest, if you want this completely SkillAPI/permission-driven, is to add the following to config.yml:

fill_wands: true

That will make it so, whenever a player gets a wand or holds a wand, it will contain all of the spells they have permission to cast (and remove any they don't).

You could then continue to use the Magic enchanting system, or sell wand upgrades, to add mana or whatever other wand properties- but the spells a player could cast and would see on their wand would be permission-driven.

For "why is /cast bad", refer to the example below I showed you for testing out a new "volley". If you let players use "/cast", they can not only "/cast volley", they could also "/cast volley repeat 100" - or, maybe a better example, "/cast nuke radius 10000". Don't try that one out for yourself :D

EDIT: Not to mention that the wand system is kind of the whole point of Magic ;) If you want players using /cast commands I think MagicSpells would be a better fit.

@Capehenrykid

Not being able to cast those spells at spawn or another player's faction, or a safe zone is expected.

Wilderness should be OK, if they can break blocks there it should be castable.

Try using "/magic check <playername>" on one of these players, while they are in the wilderness and holding a wand with one of the "non-castable" spells active. It will tell you a bunch of information about why they don't have permission. Might be something useful in there.

@Capehenrykid

If players don't have permission to build or break blocks, they don't have permission to cast spells that do so.

This can be overridden via configs, but it's generally a good idea to keep it this way, particularly on a Factions server- not really fair if players can grief other factions with magic.

If players can physically break a block but still can't cast those spells, then something is wrong.

@Atrelyu

I would not recommend giving players /cast under any circumstances! Magic is not meant to be used like that.... if you really, really want that I could add an additional permission to prevent adding parameters when command-line casting, otherwise it's going to be very dangerous. The /cast command is mainly meant for admins to use when playing around with spells to create new ones or tweak existing ones.

For instance:

/cast volley repeat 20

To test out more blocks thrown with the Volley spell ;)

The /cast command is also really useful in-game if you use the tab-completion. So, do "/cast volley <tab>" and it will tell you all of the available parameters for that spell.

@awswolf1

Yes to all of the above :)

Magic.cast.<spell> is the permission for each spell, so like Magic.cast.missile

Magic will use break/build and PVP checks for both Factions and GriefPrevention.

@Capehenrykid

Those are all spells that require build/break permission. Are you using WorldGuard, Towny, GriefPrevention, Factions, PreciousStones?