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
Is there an option to turn off spawning at the closest graveyard?
@kahlilnc
In the config for essentials you can change the settings so that it isn't in charge of where people spawn, if you do this, it should work fine :D
@kahlilnc
if another plugin starts overriding your respawns you'll need to force their respawn functions off. I've verified that this plugin works fine with MultiVerse as we use it.
You should only ever be using 1 plugin to handle respawns.
Thank you for the latest update ! :D
@Blocker226
should have continued to work just fine, but I've uploaded a new version with an adjusted plugin.yml
Will there ever be an update to this?
@Sleaker
Dynmap is a required dependency? That's silly..
Edit: Reading previous posts I see you will be changing it in a dev build. Do you have that available yet?
@darkcloud784
hmm that's odd, like the icons are blank?
How do you set up spawn-groups groups so only one group are no allowed to spawn there ?
Ever since I updated dynmap to version 0.36.1 I've seen blank markers on the map. No errors, just the markers for the graveyards are blank.
The dependency DynMap wasnt fixed.
I deleted the dependency line in the plugin file. Now it loads, OK. I didnt test the whole plugin so i dodnt know if everything is working!
@Sleaker
Thank you
@TheRadarWolf
had issues with loading it in before, it's fixed in the development builds. I'll have a new version up soon.
Why is dynmap a dependency?
<3 FTR
@Sithdown
hmm I made a silly mistake on the loading thing, but it really shouldn't be an issue in 1.03 as I changed how it is handled.
@Sleaker
Didn't see your answer, thanks :)
It fixed itself for some time, but now it seems it's happening again. Gotta look on multiverse-core config then.
You're everywhere apparently, but yea came here cause graveyard's dead and dead. Sucks a bit bout the dynmap, also sucks a bit graveyard points weren't ported over but may just be a matter of copying files, will have to see.
Other than that nice on picking it up.
http://pastiebin.com/?page=p&id=4f6f5271179a0 :( is dynmap an actual forced dependency?