FearTheReaper
Help support development of FearTheReaper:
Fear the Reaper is the next step to the Graveyard plugin and is authorized by the original author, McSpazzy. Fear The Reaper makes some feature adjustments, and additions:
- Allows players to spawn at the closest graveyard
- No longer has update checking or stat tracking
- Now integrates with Dynmap for graveyard symbols
- Still supports spawn-groups
Commands:
- /gy closest
- Tells the player what the closest spawn-point is that they have permission for.
- /gy info
- tells the player information about the closest graveyard
- /gy list
- lists all spawnpoints and where they are located
- /gy tp
- teleports the player to the closest spawnpout
- /gy tp <name>
- teleports the player to the named spawnpoint
- /gy message <message>
- changes the message text for the closest graveyard
- /gy reload
- reloads the configuration for the graveyards
- /gy group <group>
- changes the spawngroup of the closest spawn
- /gy add <name>
- adds a new spawn point at the players current location
- /gy delete <name>
- permanently deletes the spawn pout with the given name
Permissions:
- graveyard.closest
- allows a player to spawn at graveyards
- graveyard.spawn.all
- Adds the player to the default spawn-group so they can spawn at any default graveyard
- graveyard.spawn.*
- Allows the player to spawn at any spawn-group
- graveyard.spawn.<spawn-group>
- allows the player to spawn at an <spawn-group> that they decide.
- graveyard.command.user
- Gives the player all the normal 'user' commands
- graveyard.command.closest
- graveyard.command.info
- graveyard.command.list
- graveyard.command.admin
- gives the player all the 'admin' commands
- graveyard.command.add
- graveyard.command.tp
- graveyard.command.message
- graveyard.command.reload
- graveyard.command.group
- graveyard.command.delete
@Sithdown
you probably need to turn something off in MV. FearTheReaper just detects the respawn and teleports the player. MV probably does something similar to this. I'd check their options to see if it can be disabled, if not, I'll look into adding an override directly
I can't seem to make it work. When a player dies, the message of the graveyard appears, but player respawns always on the world spawn (using multiverse-core).
Are them incompatible? Is there any config to override world spawn? (No error messages in console)
@Sleaker
If you need me to test it, ill be happy to =P
@darkcloud784 yah made some changes in the latest dev to try and fix it.
@Sleaker
I actually thought it might be something to do with dynmap marker locations. mainly because the plugin does work even though it throws the error. It just doesn't show up on our dynmap at all.
@darkcloud784
this is a bug in Bukkit's load process at the moment. I'll see if I can just use a scheduler so it doesn't happen.
2012-03-06 23:59:14 [SEVERE] Error occurred while enabling FearTheReaper v1.0.2-b16 (Is it up to date?) java.lang.NullPointerException at org.dynmap.bukkit.DynmapPlugin.getMarkerAPI(DynmapPlugin.java:507) at com.herocraftonline.fearthereaper.ReaperMarkers.<init>(ReaperMarkers.java:39) at com.herocraftonline.fearthereaper.FearTheReaper.onEnable(FearTheReaper.java:63) at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:215) at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:336) at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:365) at org.bukkit.craftbukkit.CraftServer.loadPlugin(CraftServer.java:342) at org.bukkit.craftbukkit.CraftServer.enablePlugins(CraftServer.java:324) at net.minecraft.server.MinecraftServer.t(MinecraftServer.java:422) at net.minecraft.server.MinecraftServer.a(MinecraftServer.java:409) at net.minecraft.server.MinecraftServer.init(MinecraftServer.java:223) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:477) at net.minecraft.server.ThreadServerApplication.run(SourceFile:490)
Perfect :-)
@Sleaker
Is the #12 stable?
@radarwolf
fixed in dev build already I just need to not be lazy and update on here.
http://ci.milkbowl.net/job/FearTheReaper/ - if you need it soon.
How can i fix this?(I use 1.1 - R4)
@Sleaker
Thanks for the response! I'll get onto the PEX Team!
All issues related to PEX will need to be solved via PEX. I do not do anything in this plugin but issues player.hasPermission() - if PEX is not working for this very simple task I suggest you report it to the PEX developer. It is in no way related to FTR.
There is a mild issue at startup that I missed where it errors trying to load points. Simply adding one should alleviate this error on startup.
I was hoping for a quick fix because I posted so soon after the Plugin creation. Sleaker also seems really on the ball, but I really would like to test this plugin ASAP for our server.
I'm using PEX and I don't intend to change away from that.
pex seems to be broken sometimes for me, i don't know why. i changed to bperms and no problems.. but i liked pex so much
anyway im getting some errors, the ""is it up to date?"" thing, could be fun if it works
I have the same problem I used the graveyard.command.admin as well as graveyard.* and i am OP, so i should have access.
using pex 1.18 with bukkit 1.1.R4
I've set the permissions, and I just don't seem able to add a Graveyard.
I just get told the command constantly. I'm curious if I am just being stupid, or this is something with the plugin. I'm trying:
/gy add Dun'Modan Graveyard
Both just return the command listing: /gy <list | add | delete | tp | closest>