Disable Respawn Screen
This simple Bukkit plugin removes the re-spawn screen on player death. While still treating it as a death for other plugins (for Example scoreboard death counts will still trigger). In additions users still drop their inventories and lose all experience as if a natural death had occurred. This plugin also respects Keep inventory Game rule, ie if it is enabled the user keeps their inventory.
How does it work
On death you will re spawn instantly without being prompted to click re-spawn.
Commands
At present this plugin does not have any commands.
Permissions
At present this plugin does not have any Permissions.
Configuration
At present this plugin does not have any Configuration. Just drag and drop into the plugins directory and it should enable.
Video
Thanks to IngrownPenguin for this video showcasing DisableRespawnScreen
Thanks to AbsintoJ for doing a Portuguese video showcasing DisableRespawnScreen
Source
The plugins source can be found at https:github.com/aet2505/DisableRespawnScreen
Comments, criticism and pull requests welcome.
Donations
To anyone who wishes to donate please click the button below.
This is very much appreciated but by no means expected.
after i remove this plugin i still see it in the /plugins but collord red
how to romove this plugin in total :/
i find some bug ,please fix it for example you rideing horse and the zombie kill you ,and then you respawn ,but zombie will hit you too i don't know how to talking about that , i think you can try,thank you
@Adondriel
Is this the case when the NPC that combat log creates is killed?
This is as a result of that plugin's NPCs sending the playerDeathEvent which causes my respawn method to trigger.
Unfortunately because Combat Log does not have an API or is open source I cannot adapt my code to create a fix for you. It might be worth asking the author of combat log for some advise and I will have a think. I am sorry I cannot do more to help and thanks for using my plugin.
When i use this with, http://dev.bukkit.org/bukkit-plugins/combatlog/
it creates inanimate npcs when someone combat logs.
Could we have some sort of custom noticable text that appears to the user when they respawn, that could be ajusted to whatever you wanted it to be in a config?
@owenwant
Glad you like it
Awesome plugin man :) ..very helpful :D
@therealspoljo
Was much simpler than I first thought. PM'd you some info.
@aet2505
No need to hurry :P Im using Spigot #1030 (1.6.2)
@therealspoljo
I'm too good to you. :P
Will start work on it tonight / tomorrow and will PM you the version when I am done. It shouldn't take me too long to do but will have to fit in around another project I am working on.
EDIT: Forgot to ask which bukkit version are you running?
@aet2505
That would be awesome! Thank you :)
@therealspoljo
I do not want to add this into the release version of the plugin as this would add a dependency which I don't use or want to enforce on players. However I can look at adding support and then sending you a copy of the plugin with this support. Let me know if you want me to look into doing a custom version with this support.
Thanks
Could you add support for CombatTag? Becuse I use their NPCs and after I kill a combat logger (NPC) it respawns him and fill my whole console with errors.
@MrEkinoxx
I am not sure what you are looking for. Do you mean a time until the person is respawned?
Please add a config time respawn thx
@IngrownPenguin
I have just started working on it. Should be uploaded to bukkit this evening and pushed to CI server tonight as well.
EDIT: Have just pushed changes and uploaded to Bukkit. Am having some issues with the CI server so for dev builds please PM me for information.
update for 6.2 coming?
V1.1.0 Has just been approved by Bukkit. This version adds support for version 1.6.1
@sonicwolfsspeed
Are you running in version Minecraft 1.6? If so version 1.0.0 will not support it. The latest Dev build (1.1.0) has been uploaded to Bukkit Dev and is waiting approval and that version does have 1.6.1 support. If this is not the issue could you send me a copy of any errors printed in the log so I can ensure it is fully fixed in the latest builds.
never mind i just took the dev build that works :D