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
Hey mate im having a problem with the plugin:( Before use an autenticator plugin it was ok.. now using (CrazyLogin) i spaw at my /spawn and not on FirstSpawn (using this on Test Dummies) I have a tutorial so ppl when join 1st time do it.
Any solutions?
@dtschaedler If you have a permission system then give the players the perm: FirstSpawn.use
That all players can use the /fs command is a feature I need to make into it.
I am releasing a new version this day with some bug fixes en rewrites.
Can you make it so that non-OP players can use /fs. I want my world to have a single spawn for all players.
Well Mcferson the plugin gives owners a option to force people to a tutorial at there first login in a server after they did the tutorial and they die or something they will be teleported to the "normal spawn" which is at another location you can use it in other cases but this is the main reason.
Don't understand very well. What exactly does this plugin ? Do players first spawn on different places ? Can we define define these different spawn points, are they spawning randomly on one or other ? Is the point definitively the spawn point for the player ?
The lasted dev build has no spamming FS-Debug :D Build #70
Yayyyyyyy its updated THANK YOU SO MUCH!!!!!!! ill get it when i get home!!!! :D THANK YOU!!!!!!!!
@TakeMeNL
:D its alright, don't worry
@limeramen22
Hi there, sorry that its taking a long time, personal live is in the way....
Also my backend server has "crashed", so i cant update it until i repair.
What takes about 20 minutes from this post. I am VERY SORRY!
please upload the update, i need this before i can turn on my server again!
I will send all of you an PM if the new update is there.
Can you please let me know when you update it, too?
@TakeMeNL
Thanks! Reply when you have updated it :D
@limeramen22
Yeah I was also inplanting the customcommand feature.
I may be forgot to update the or so, I fixed it. But I didn't yet update the revision.
I am away for a couple of hours. I will after that commit the update
I tried the new dev build which did let all users connect now *fwew*, but now I can't do any firstspawn commands, it gives me that "and internal error prevented you from using this command" or something like that... I get this too:
[SEVERE] null org.bukkit.command.CommandException: Unhandled exception executing command 'firstspawn' in plugin FirstSpawn v1.5 (b65-git-a9740f15) at org.bukkit.command.PluginCommand.execute(PluginCommand.java:42) at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:168) at org.bukkit.craftbukkit.CraftServer.dispatchCommand(CraftServer.java:492) at net.minecraft.server.NetServerHandler.handleCommand(NetServerHandler.java:878) at net.minecraft.server.NetServerHandler.chat(NetServerHandler.java:825) at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:807) at org.getspout.spout.SpoutNetServerHandler.a(SpoutNetServerHandler.java:107) at net.minecraft.server.Packet3Chat.handle(Packet3Chat.java:44) at net.minecraft.server.NetworkManager.b(NetworkManager.java:276) at net.minecraft.server.NetServerHandler.d(NetServerHandler.java:109) at org.getspout.spout.SpoutNetServerHandler.d(SpoutNetServerHandler.java:173) at net.minecraft.server.ServerConnection.b(SourceFile:35) at net.minecraft.server.DedicatedServerConnection.b(SourceFile:30) at net.minecraft.server.MinecraftServer.q(MinecraftServer.java:581) at net.minecraft.server.DedicatedServer.q(DedicatedServer.java:212) at net.minecraft.server.MinecraftServer.p(MinecraftServer.java:474) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:406) at net.minecraft.server.ThreadServerApplication.run(SourceFile:539) Caused by: java.lang.NullPointerException at com.DutchMasterServer.firstspawn.FirstSpawn.onCommand(FirstSpawn.java:127) at org.bukkit.command.PluginCommand.execute(PluginCommand.java:40)
I'm using essentials, but I've never had this problem before, it just started happening a couple days ago.
@bukOhTwo
You mean on your server?
Well i have a dev build, if you want to try. I am testing it my self right now.
@TakeMeNL
I'm not using essentials. I think the only ones that deal with spawns are CommandsEX (tpa, back), CommandBook, and MultiHome.
Thank you all for the feedback!! And I will look onto it right away and made some changes.
To confirm, you are using essentials??
Yeah I get the same thing, some people can't connect to the server, it gets stuck on "downloading terrain" then gives the timeout error. when i dont have the plugin though, it works again. please update this to work, its a great plugin and I neeeeeed it to work!!!! My server is off at the moment.