FirstSpawn
FirstSpawn, control the new noobs
v1.7.0 | Source | Latest config
If you wan't to control the noobs joining for the first time on you server, then you need FirstSpawn!
FEATURES
- Spawn new players on a different place then normal!
- Make a holding cell, so players need to do something before they can leave!
- Completely customizable!
- Custom commands!
- Easy to set up!
- Extremely easy to use!
- Very few user commands!
- Supports Permissions!
GETTING STARTED
Setting up FirstSpawn is easy, but it is a little involved.
BASIC setup
- Stop your server.
- Download the jar-file from the bukkit page.
- Place the jar-file in your server's plugins-folder.
- Start the server again. This process will generate a config-file (config.yml) in the plugins/FirstSpawn folder.
- Join you server and stand where you and the new player to spawn.
- Type in the chat: /fs set. This will set you FSP (FirstSpawn Point). - Make sure you have the right permission!
- To finish type in the chat: /fs reload.
ADVANCED setup
The advanced setup is actually the basic setup with a custom spawnpoint is the player has a certain permission.
- Open the config-file (config.yml) in the plugins/FirstSpawn-folder.
- Set the SpawnPoint>Enable to true. - Enable: true
- Save the config-file and go back in the game.
- In-Game chose a position you want players with a certain permission to spawn.
- Type in the chat: /fs setspawn
- To finish type in the chat: /fs reload.
Permissions
Command | Aliases | Description | Permission |
firstspawn | fs | Teleports you to the FirstSpawn position | FirstSpawn.use |
firstspawn set | fs set | Set the FSP (FirstSpawn Point) | FirstSpawn.admin |
firstspawn setspawn | fs setspawn | Set the SpawnPoint | FirstSpawn.admin |
firstspawn version | fs version | Shows the current plugin version | FirstSpawn.admin |
firstspawn reload | fs reload | Reload the FirstSpawn Plugin | FirstSpawn.admin |
- | - | Let players always spawn on FirstSpawn point or if SpawnPoint is enabled. They will spawn there | FirstSpawn.hold |
TROUBLESHOOTING
If you are experiencing problems with FirstSpawn, please try to follow these simple steps before posting a ticket or posting a comment as it will make everything much, much easier for everyone in the troubleshooting and debugging process:
1. Check the server log
The first thing you must do is check the server log for any exceptions (don't know what an exception looks like? Click here). If the exception looks like the following, you are using tabs instead of spaces in your config-file (which is punishable by death):
[SEVERE] Could not load 'plugins\FirstSpawn.jar' in folder 'plugins': while scanning for the next token found character '\t' that cannot start any token in "<reader>", line 15, column 1: prefix: ^
If it doesn't look like that exception, just copy it into a pastebin or a pastie, and include it in your bug report ticket. Please don't post bug reports in the comments because that is rather anoying to read.
2. Try your setup on a fresh server
If at all possible, try setting up a local test server (don't know how? follow this guide), on which you install nothing but FirstSpawn. Now copy the config-file that you're using on your live server where you experienced the problem, and see if you can reproduce it. If not, you most likely have a conflicting plugin (read the next section).
3. Find possible plugin conflicts
Try removing all other plugins from your server. Do this by stopping the server, moving all the .jar files into a different folder than the plugins-folder, and then starting up the server again. If the problem persists, it's a problem with FirstSpawn, but if not, it's a conflicting plugin, and if so, try to add half of the plugins back at a time (binary search), and test every time you do, so you can figure out which plugin is causing the conflict.
KNOWN ISSUES
- Does not work with other spawn handling plugins like EssentialsSpawn.
AutoUpdate and Metrics
This plugin checks if there is a update available if the owner joins the game. You can disable this by setting AllowUpdateCheck to false in the config.
This plugin also uses MCStats Metrics to collect anonymous information. You can disable this by setting opt-out: true in the config of metrics. That is located in /plugin/metrics/.
LICENCE
FirstSpawn by TakeMeNL is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported Netherlands License
Based on a work at GitLab
@This_Guy_is_Pixelated You first need to do is setting the point what the FirstSpawn is. /FirstSpawn set . Then /FirstSpawn reload en verify that in the config all 0 are now long numbers. Except for SpawnPoint.
If this still doesn't work maybe you should make a ticked with some console info. That can help allot!
it didnt work for me when i type /firstspawn it says an internal error occuerd while performing this command
Thank you :)
@TakeMeNL
I know it isnt :) BUT.. even when players join for the first time (i delete the player file in the "world/players" folder, and the data from FirstSpawn, said player will still not spawn at the FirstSpawn locating.. but if i do /fs , it takes me right there :)
hope you understand, and hope you can help me out :p
@Jonasbilljensen
You know this plugin is not a spawn handler. If you join for the firsttime it will teleport you to the FirstSpawn after that you spawn at you world default spawn.
Hey there, im running this along with EssentialsSpawn, and i already set it to "lowest" prio. yet im still spawning at my "defualt" spawn point, which is on my roof.. which is rly annoying :(
i hope you will post and updated version soon that will allow us the use this with essentials :)
Jonas
@TakeMeNL
I am still having issues making it work, even with your suggestions. I've tested it on myself by removing my .dat files in both world and essentials. I can get it to spawn myself in the right location once, but once I reset all the files again, including removing the users.dat for firstspawn, I just get stuck with another random spawn location until I go /fs set /fs reload and do it all over again.
Essentials is already at lowest, and I have no other mods that would affect where I spawn.
Please note that if you install FirstSpawn plugin for the first time it will add all players that have been on the server to the ignore list . Users.dat. You can empty that file and all players will spawn on the FirstSpawnPoint if they login.
@TakeMeNL
Sweet. Having a fixed spawn point is something I've been trying to get to work for quite a while, since I made a small house to start in on the server, but now people just spawn on the roofs of the buildings around it instead of inside it. haha
@Trauron
Well i found a way to work with essentials. That update is coming tomorrow I think.
Whenever I go to use this plugin, the firstspawn isn't used and it continues to use the game's default or the server's/essential's default.
I'm currently using Essentials along with this plugin, so I don't know if they are interfering or not.
I've tried everything I can think of on my own to fix it, so I am looking for suggestions on seeing what might be interfering or how I might fix it. I've already tried changing the settings in config.yml for essentials for the starting spawn point. I tried setting it to firstspawn, default (the guest/new player group), and none to see if it would pick up on the firstspawn. None of it seems to work.
I am not sure what I can try at this point, so I'd appreciate any help on this matter.
@3ptO In the essentials config you only need to change the respawn-listener-priority: lowest or low. If there is no other plugin using starter kits. There is no problem. Essentials will, hopefully, handle the starter kits. While FirstSpawn teleports players.
What I can do. But tomorrow, make some adjustment to the plugin. Instead of disable essentials teleport, use the essentials teleport.
@TakeMeNL
Thank you for the prompt response. I will begin testing shortly...
I have set Essentials priority to lowest, however, will this interfere with starter kits?
@3ptO
If you give your natural players the permission "FirstSpawn.hold" they will always spawn at SpawnPoint (setting by /fs setspawn). You to enable that in the config.
Players that join for the first time go to FSP. (/fs set)
I don't know if it will interfere with factions. I looked at the source code of it. And I think you just need to test that. But! This is only if the player has "FirstSpawn.hold", if he hasn't that perm faction will teleport him home.
If you have questions just ask! That's why we are here.
To verify, giving the players FirstSpawn permission will always spawn players at fs upon death or rejoin? Also, would this interfere with the plugin Factions' ability to respawn faction players at /f home upon death? In other words, I want neutral players respawning at fs where as I want faction members respawning at /f home.
@0dayRUDE
There is a update for 1.4.7! :D
We will update as soon as possible thanks for heads up though
lets see an update for 1.4.6 :D
@Luzitano Ok no problem. I am glad to hear its working now.
And no I won't let this plugin down! ;)
Edit Forget it - its Crazy Login that keep tracks of IP - and when we join on other IP it recognizes i already did the 1st spawn and i log on normal Spawn,
O must say : do not let this plugin die :)