Quote from Siguza:
Since Spigot is still standing and Sponge is slowly getting somewhere, I'm not exactly sure what to do with my plugins, but I'll stick around.
I think I will port most of my plugins to Sponge, but some (like NBTLib) will hopefully not be necessary anymore.
For now, I've set all my projects to "inactive", except for VirtualPack, which I will keep compatible with Spigot, until I ported it to Sponge. If you really want to see any of my other plugins updated to Spigot, just comment on its project page.
Edit every attribute of your mob spawner - using commands and/or templates.
How to use
- Download NBTLib and move it to your plugins folder.
- Download the iSpawner.jar and move it into the plugins folder.
- Start your server.
|true or false
|Whether to check for updates or not.
Note 1: The actual command is "/ispawner", but there's the a short version: "/isp"
Note 2: Red arguments have to be given, blue ones can be omitted (depending on what you're doing)
|Show the help
|Show the version of iSpawner
|Execute this command and click
a block to start a session.
|/isp start (world) (x) (y) (z)
|Start a session in world world at
|End the session and discard changes.
|End the session and apply changes.
|/isp set (path) (type) [value]
|Set an NBT tag to a certain value.
Important: If type is list, compound
or "-" (= delete tag), you don't need
to give a value, otherwise you do.
|/isp import (name)
|Import the file
|/isp export (name)
|Export the current spawner
|/isp export override (name)
|Export and override
|Print all the data of the
|Show all possible NBT types.
|Allows the use of iSpawner commands
|Allows to edit spawners directly via commands
|Allows to import templates
|Allows to import every template
|Allows to create templates from spawners
|Allows to overwrite existing templates when exporting
|Notifies you of new iSpawner versions
|Full iSpawner access
Development builds of this project can be acquired at the provided continuous integration server. These builds have not been approved by the BukkitDev staff. Use them at your own risk!
[ Dev Builds ]
Is of course always appreciated. :)