Configuration

Set the item ID for the Thor hammer with Hammer.itemID. Set whether left or right click with Hammer.leftclick

Globals: These affect all powers, and are a convenient way to turn on/off some features without having to change the discrete config items for each and every power section on config.yml.

• Generic.enableDurability controls whether there is any durability impact. If set false, all power durabilities are ignored. Default ON.
• .enableCooldown controls whether or not each power has an enforced cool down period before it can be used again. Default ON.
• .enableTargeting supposed to make placed mobs target the nearest player, but current Bukkit API call setTarget() doesn't work. Default off.
• .enableCrafting enables crafting of Mjollnir (and in the future, power-tool crafting). Default ON.

Each power has a config node in which you can set the following:

• durability: impact to item durability when used. Each power has a different default value
  • Listen for the magic vacuum clap when the hammer is used up.
  • If you configure an item that is not a tool (ex. bone) and durability use is enabled, one of the items will be "used up" (i.e. disappear) with one use.
    • only one of the stack is used up, so you can hold up to 64 "charges" of the power.
• cooldown: seconds to wait before using that power again. Chat message sent to player with remaining delay. Different defaults also set.
• range: max allowable range of that power. Default: 256
• item: the item/tool that can exercise the subject power without needing a permission or a /thor command.
  • Requires a string name of a Bukkit Material. Since in 1.7 use of numbered IDs will go away, had to add this.
  • added some commonly used alternatives for the Bukkit Materials.
  • For the moment , still support itemID and if there is an itemID configured but not item, that will override the default item.
  • Version 1.75/3.1 had default items for some powers, for example right-clicking with an iron_spade would teleport you. If you are simply upgrading. those old itemIDs will have been written to your config.yml and will be retained.
  • If you want to disable these "power tools", delete both the item and itemID lines, if present.

• meta node allows configuring special characteristics for the tool
  • name: set a name for the tool.
  • enchants: allows setting enchantments. If present, a list underneath of enchantments and levels is expected
    • before colon, a Bukkit Enchantment name is expected. If not recognized, it will be ignored
    • after colon, the integer level of the enchantment. If beyond allowed levels, it will be silently ignored by Bukkit
    • see default config to get a better understanding.
  • lore: if present, a list of strings is expected below and will be added to item lore
    • for example what that looks like, see above crafting picture
    • each string must be prefixed by '-' for proper YML formatting.
    • Again, see default config to get a better understanding.
• recipe node allows configuring a crafting recipe that will construct the configured item including all its meta
  • Underneath, it must include either a shape and ingredients node, or a quantities node
  • quantities configures a shapeless recipe.
    • each item under here must be a Bukkit Material name, or alternative, followed by a colon and a integer quantity
    • can only include up to 9 total
    • Again, see default config to get a better understanding.
  • shape defines the shaped recipe by character keys
    • shape must be a list of three strings of three characters each
    • each character corresponds to a Material to use; if a character is given but not found in ingredients, recipe will not work.
  • ingredients: defines the Materials used in above shape
    • each item under here must be a Bukkit Material name, or alternative, followed by a colon and a single character
    • unused ingredients will be ignored, with a warning
    • Again, see default config to get a better understanding.

The creature spawning powers each have extra options:

• quantity: Amount of that creature to spawn with one click.
• targetingRange: Radius to search for nearby entities to target.

The explode power has an extra item:

• explode.power to set the size of the explosion. FYI, a creeper is 3.0.

The arrows power users a similar arrows.quantity config for how many arrows are spawned, at a rate of 2 per second. This is demonstrated in this video. If you have good aim, all arrows can hit.

The groundpound power uses a similar power config. It sets how many blocks from the center where the blocks are boosted with their peak height. Full radius of the groundpound is twice the power. Of course, the higher the power, the greater the boost.

• groundpound.power to set power and size of groundpound. Default is 5.0

Check your Thor/config.yml file to edit. It will be created with default values if it doesn't exist.

Defaults

Defaults set the Hammer to a stone axe, and enable durability. Some powers have default tools, and some have crafting recipes.

Defaults in 4.5.1 for arrows includes a crafting recipe to make an enchanted bow.

Note that default also has 0 cooldown for arrows resulting in the barrage of LOTS of arrows with multiple clicks or holding mouse down, as shown at the end of this video

For full defaults, see this page.

Permissions

The following are permissions that Thor offers. Using a Permissions plugin is not required, but allows you to grant discrete powers for use with Mjollnir. Note that use of a Power Tool does not check any permissions.

• thor.* gives access to all Thor powers
• thor.<power> gives access to using Mjollnir via the thor <power> command.
  • e.g. *thor.lightning gives access to "thor lightning" command.
    • But if in your config.yml lightning.item is set, use of that item ignores permissions
  • all other powers are similar to lightning, above.
  • that means there are a lot of permissions, power-specific.

• thor.list allows player to list who has a thor power (set by /thor command) or has used a power (by itemID).
• thor.give allows player to give himself the Thor hammer

thor help and thor stop have no permissions and anyone can run them.

Current default is only Op has all permissions.