Bukkit

@lathame

That is intentional- for admin purposes, it's often necessary to drop your wand. But I figured that was a really intentional thing to do that you probably won't do accidentally....

A config option to block it could be added if it's a big deal, but there does often come a point you'll want to look at someone else's wand or something :)

Magic 4.5 - Engineering, PreciousStones

A quick note on 4.5 - there is a new config option "precious_stones_enabled" (on by default). This makes it so any player who can build in a field can also cast any spell in that field, regardless of other region or field (anti-PVP) settings.

@LordBoos this may be of particular interest to you.

Some examples of how this can be used (paired with WGCustomFlags):

• Globally deny access to all engineering spells (players can still use them to build their homes)
• Globally deny access to the backup spell, players can backup + repair their homes

This also means that field intruders are at a disadvantage if the pvp flag is set on the field- they won't be able to use attack spells, but field members will.

If this all sounds like something you don't want, please make a note to change that config option after updating!

Otherwise, this update is mainly for Engineering magic- all engineering spells now have custom icons (all spells!!), there is a new brush selection mechanism, and a few spells (Blob, Shell) now have Engineering versions to upgrade to.

@lathame

Here is the most up to date list I have, though it's probably a little old:

https://github.com/elBukkit/MagicPlugin/wiki/Admins

You can always inspect the plugin.yml file for ALL the pnodes:

https://github.com/elBukkit/MagicPlugin/blob/master/src/main/resources/plugin.yml#L44

PNodes generally follow a consistent format- "Magic.commands.<commandname>" for commands, "Magic.cast.<spell>" for spells. I discourage using per-spell perms, but I know you were a fan of that last time around :)

@LordBoos

That would go in enchanting.yml - see the defaults here:

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

So basically put something like this in your enchanting.yml:

default:
  min_enchant_level: 10

I am thinking about raising the default of 5 up a bit.

@Moondog32

Magic is backwards compatible to 1.7

@LordBoos

Hah, yeah I was wondering how your players would take it. It is hard to find honest players these days :)

Well I'm glad it worked! Is your server public? I'd be curious to see what you've done!

@LordBoos

Oh, one more thing- if you have wands set to indestructible (the default), you should do the following from the console prior to shutting down to update:

magic clean ALL

The caps on ALL is important. This will clear any wands on the ground. Otherwise, they will remain indestructible (and won't despawn) until picked up and dropped again.

@LordBoos

Ok- well this will be a bit like a sledgehammer, but...

Latest dev build has a new config option- "wand_key".

So in config.yml, you could add

wand_key: magic

And all current wands will be "inert". I haven't tested this super thoroughly.. but if you're ready to destroy all the wands in the world, what's the worst that could happen? :D

@LordBoos

Well ... In short, no :(

I do have something in MagicWorlds - a "depopulate" command that will search for chests and remove wands, but it never fully worked - if your map is mostly square it might do the trick.

However, wands in players inventories or nether chests I can't access white they offline, so there's no way to clear them.

I think I could add a config option to let you change the "key" magic used to store wand data, which would render all current wands inert... That's all I can really think of offhand, though/