Bukkit

@Oniromancie

Everyone gets wand access by default.

Try adding "-Magic.wand.use" to your default group. I *think* GM is smart enough to handle that, the explicit allow on the mage group should override.

If it doesn't, please let me know!

You can make wands limited-use with the "uses" parameter. You can use this in wands.yml to make limited-used templates, or in-game to modify an existing wand:

"/wand configure uses 50"

The wand will then self-destruct after 50 casts. It will tell you how many uses are remaining in the lore.

This isn't exactly "durability" in the Minecraft sense, but durability doesn't work on all item types so I don't use it for anything.

Sooooo - sort of, but not really just yet.

I use Shopkeepers on my own servers- I love it, and it nearly works great with Magic.

Unfortunately, Spigot doesn't natively support serializing custom item data, like the kind wands use.

I have a custom Spigot build I use, and I have submitted this custom item data patch as a PR to Spigot, my hope is they will accept it. If they do, a variety of plugins (like Shopkeepers, StarterKit- anything that saves items from an in-game item) will work with Magic.

Until then, I'm afraid your only options are dtlTraders, Essentials signs, and anything that can run a command. There's nothing else out there I'm aware of that does villager shops like Shopkeepers does.

It's a perfect fit for Magic, since I like this to be as vanilla-ish as possible- so I'm really hoping that patch gets accepted.

@kakawolf99

There are a few things that commonly keep Automata from working:

1. Command blocks need to be enabled in server.properties. Test: Manually place a command block and try it out, or use the flare_beacon schematic

2. You need to be somewhere with global build perms Test: Check if you're in a WG region, or a Faction, or a Towny plot, or a PreciousStones claim.

3. You need to aim at an allowed block type. To prevent automata from being too destructive or wrecking the economy, most common materials are restricted by default. (Lapis blocks or obsidian work fine) Test: Check the default configs: https://github.com/elBukkit/MagicPlugin/blob/master/src/main/resources/defaults/materials.defaults.yml#L315

4. The spell *could* just be broken, though it's working for me Test: "/wand add simulate3" and cast the Simulation 3D spell yourself. If this works, automata should work too.

I hope some of that helps! These are a bit tricky to get working since I've tried my best to make them safe. Or, as safe as something like this can be.

@joshep92

Magic dev build#608 (see Build Server link above) has Lockette integration.

Magic should no longer allow players to modify others' private chests (or doors, though I didn't test that part).

If you Shrink your own chest, it will still destroy it.

And, I can't vouch for all the "explody" spells. If you toss a TNT Grenade near a chest, it'll probably still explode it- you'd need to fall back on other forms of protection to prevent that. But the same goes for vanilla TNT.

@joshep92

One option I didn't think of at first, add the following to plugins/Magic/materials.yml :

indestructible: - chest

This will make all chests completely indestructible to Magic.

You've motivated me to add Lockette support, too, though :)

@joshep92

You would have to customize the configs to remove individual spells. For instance, put the following in plugins/Magic/spells.yml

shrink: disabled: true

To remove the "shrink" spell completely, including from existing wands.

That said, shrink is not supposed to dump chest contents, but it should destroy them. I integrate with a wide variety of protection plugins (WG, Factions, Towny, PreciousStones)- but unfortunately, not Lockette. I'll make a note to look into that.

In the meantime, this plugin is probably not going to be safe for you - there are a ton of spells you'd have to remove to prevent destruction if you're not using one of the supported protection plugins.

@t2yacool

Spigot 1.8 does not (currently) support adding glow to items. So the wands and spells no longer glow. I'm hoping this gets changed (I plan to submit a PR for it).

They should still function as normal, though- do they not?

Yes, the "damage" parameter works with a variety of spells. Some of them (like fireballs and TNT) use a "size" parameter instead. These don't do damage directly, but "size" controls the size of the explosion, which indirectly controls the amount of damage done.

So it depends on the spell class, but anything that does damage should be tweakable.

That is dtlTraders. I need to check to make sure that it still works as I don't use it anymore, but Magic does integrate with it and it should still be working.