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
@bukOhTwo
Well the funny thing is that the update server is just a very simple Version file on GitHub.
I will change it but for most time it just work good, maybe your provider had some miner issues? As I sayed I will change the way update is handled because it not the best solution I think. So keep a eye on the github changelog if I update it there will be a automatic build that you can download at the DMS - CI (Link above)
@TakeMeNL
No, not even a crash log. The only thing it leaves is the can't connect to update server or something along those lines. It looks to be the same problem as Kyle's. Literally brought the whole thing to a halt because it couldn't reach the update server.
@bukOhTwo
That is very sad to hear... Did you get a error log?
This completely crashes my server. It attempts to look for an update, but it can't find the server.
@bobbysmithyy
As it sayes on the download page.
In order to work with Essentials, please change the 'respawn-listener-priority' to lowest.
'respawn-listener-priority: lowest'
@kyle0440
When I am back from my Holliday I will fully test and modify FS .
Sorry if it's not working properply, please make a ticket for it to remind me
This plugin isn't functional with servers using Essentials. Looks as though the essentials spawn point overrides the first spawn point.
The server sometimes crashes when people spawn at the firstspawn, and the chunk doesn't always load if it's not already loaded.
@pur3strb1t
FirstSpawn doesn't support any other command then /FirstSpawn and /fs
So there is no code for it
Hey, I got a question what is the code for the /spawn or /home
@broluigi
Oke that may help xD
For now I have no idea. If you have essentials, I haven't fully test it yet.
When I am back home I will fully test it.
Also, make a ticket for me to reminder! With all information.
@TakeMeNL
sorry, i didnt know i had to tell you this but.. the order in which you see that code is upside down- (my console is a multicraft one)
@broluigi
I you have a cracked server. In my opion this is not my plugin.
Also some code is missing, because a error doesn't start with [Server] INFO at.
Try looking in your server log for the whole code. Else I can't help you.
what would this mean?
@Bobbosells32
Sorry it takes a log time to approve xD
its now Under Review :D
It's telling me there's a 1.5 update but I dont see it >.<
@evilmidget38 Thank you, but in the early days there was no stable bukkit permissions.. There are the new ones now that are good, but i wait for the 1.3 update to update.
Why are you using Vault for permissions? You know Bukkit has built in permissions-api for permissions. It's simply if (player.hasPermission("some.random.permission")){ stuff }
You don't need vault for permissions, only for things like economy and groups.
@xDrapor Oke, as some of you know, essentials has a newbspawn / new player spawn system. WHY would you use FirstSpawn instead? They are both almost TE same. Only FirstSpawn can players respawn at a specified point with one permission. But that's it. I will put up a vote.
@TakeMeNL
Set the Join listener to a higher priority than essentialsspawn?
@HeroJunky @pjrueda Oké i will do very detailed tests with FirstSpawn and EssentialsSpawn.
I hope i can report a new version with support to Essentials.