I made this little plugin to fix new players getting stuck in walls or spawning on roofs, etc. and dying when they first log into the server.

It works by running a command after a configurable amount of ticks when players log in for the first time (or they don't have a player file).

I thought I should upload it here in case someone might find it useful. I couldn't find anything to do what I wanted so here it is.


The config.yml file should be automatically generated for you the first time you start your server with the plugin in your plugins folder and add any new variables on plugin updates with their defaults.

ticks: 20
The number of ticks to wait before running the command.

command: spawn
The command to run after waiting the number of ticks.

  • Will replace any occurances of PLAYERNAME in the command with the player's name.
  • If you want to use a command with spaces then enclose it with single quotes:
    command: 'some command'

Note that if you use spawn as your command you should have a plugin that provides that command or it won't work.

runas: player
Enter player or console to choose to run the command as the player or as console.

span: 5000
The number of milliseconds the player must have been logged in to avoid the command being run when they join.

prevent_new_logins: false
Stops new players from logging in.

prevent_message: "New players are not currently allowed to login. Please try again later."
The message to display to players who are prevented from logging in.


/ffl prevent <on|off>
Turn on or off the preventing of new players from logging in. Default: off (new players can login by default)


Gives access to use /ffl prevent <on|off>

Gives all FixFirstLogin permissions. (currently useless)


You must login to post a comment. Don't have an account? Register to get one!

  • Avatar of madtomic madtomic Sep 20, 2014 at 05:55 UTC - 0 likes

    very nice plugin! thanks!

  • Avatar of ryvix ryvix Apr 27, 2014 at 04:43 UTC - 0 likes

    FixFirstLogin v1.3

    • Compiled against Bukkit 1.7.9 with Java 1.7
    • Added the ability to prevent new players who have never logged in before from logging in.
  • Avatar of Serilum Serilum Nov 19, 2012 at 21:09 UTC - 0 likes

    Thank you for the plugin!

    McCombat a hardcore server whereas the only rule is no hacked client.

  • Avatar of DruidKiria DruidKiria Aug 27, 2012 at 03:07 UTC - 0 likes

    @ryvix: Go

    Awesome! Thank you very much! This solved everything!

  • Avatar of ryvix ryvix Aug 24, 2012 at 17:27 UTC - 0 likes

    @DruidKiria: Go

    I just uploaded version 1.2.1 which lets you replace PLAYERNAME in the command with the player's name.

  • Avatar of ryvix ryvix Aug 24, 2012 at 16:57 UTC - 0 likes

    @DruidKiria: Go

    Ah I see. I will add a variable to replace the players name.

  • Avatar of DruidKiria DruidKiria Aug 24, 2012 at 16:53 UTC - 0 likes

    @ryvix: Go

    I though of that, but I have two spawns, one for first time players (with rules, so it's kinda important), and one for old players, more practical.

    HSP has /setspawn and /setfirstspawn, but only /spawn, and no /firstspawn. The issue is if i put the command as spawn, ALL players are going to spawn on first spawn point on death.

    Really don't know what to do! I guess it's better to set one spawn for everyone while I can't fix it.

  • Avatar of ryvix ryvix Aug 24, 2012 at 16:08 UTC - 0 likes

    @DruidKiria: Go

    Ah I see, you want <player> to be replaced with the player's name. I probably could make it replace something with the player's name in there. Right now it doesn't do that.

    However, does HomeSpawnPlus have a /spawn command which sends the player to spawn? If so you could just leave the config as default and see if that works.

  • Avatar of DruidKiria DruidKiria Aug 24, 2012 at 12:43 UTC - 0 likes

    @ryvix: Go

    Excellent! I had to download it. This thing is bothering me so much. But yet, I couldn't fix it. Looks like console is not doing the command. I have this as my config.yml:

    ticks: 20 command: 'warp <player> spawn' runas: console span: 5000

    Is it because of the command? I have HomeSpawnPlus installed, which also didn't helped fixing this issue, is that it?

  • Avatar of ryvix ryvix Aug 24, 2012 at 11:01 UTC - 0 likes

    @DruidKiria: Go

    Yes, it will run a command after a configurable number of ticks when a player joins the server. Once the player has been logged in for a total span of time (5 seconds by default) then it will no longer try to run this command anymore.

    For example, if a player joins but sees they are in a wall and immediately logs out within 1 second their total logged in time should still not be more than 5 seconds and if they come back and stay longer than the number of ticks the command should be run as long as after the number of ticks is up it still hasn't been 5 seconds.

    It could also work if a player gets disconnected when trying to log in the first time, or takes a second to actually finish logging in, etc. then once they stay connected longer than the number of ticks configured in the config, as long as they have not been logged in for a total span of 5 seconds altogether then the command will run.

    It may seem like overkill to have the number of ticks before the command runs and the total time they should be logged in before deciding not to run the command but in my testing this is how it was necessary for it to actually work properly.

    The default values probably should work fine but I've only tested it on a couple servers so they are configurable if anyone wants to tweak them. Experimentation might be necessary.


Date created
Jun 19, 2012
Last update
Apr 27, 2014
Development stage
  • enUS
GNU General Public License version 3 (GPLv3)
Curse link
Recent files