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
I search a plugin who set only first spawn point, found this, give a try but :
When i start your version 1.7.0 in bukkit/spigot 1.8.0R01
i have this log
Plugin don't create default config file right and don't read them after ?
i have this in config file :
No command working, i have test /fs set and after /fs reload but no changes...
Of course i'm op on server.
@Layania You know what, that a good idea! Secretly i worked on a new 1.8 version. I'm sort of rewriting the plugin so it will work with other plugins and such. Also, 1.7.0 should still work.
someone can take this project ? :)
Very usefull if we don't use essentials
As many of you all know, 1.8 will be out soon.
Because of the new "changeble" name introducing the UUID.
I need to rewrite this plugin. I had a version thats working for 1.7.5 but it won't be long...
But i will upload it.
When will the latest 1.7 update be available?
@Cattasraafe
Yes i notice it yesterday when updating the plugin.
The plugin didn't check if you had enabled the SpawnPoint option regardless of what you want. The 1.7 version should fix this! Bringing the update ASAP!
Hey there been hosting with this for a bit now to control where new folks to my server spawn. The only draw back was that it forced existing members to the spawn after I had it going. That was not terrible but kind of annoying, but the part that is vexing me is that some people after they die are getting sent the the FirstSpawn Spawn point... you got any idea what might be causing this? Other than this I've had no issues.
@TakeMeNL
Awesome! And thank you for your quick reply! :D
@bounce_raff
I haven't fullt tested it, but yes it should work in 1.6.4 and 1.7
Does this work with 1.6.4?
@think420 No it won't conflict.
Hello,
I have FreeTeleport installed in my plugins, which has a command for /setspawn and /spawn
Will they conflict?
@gepardo43 Hi there,
It apears to me that the respawn location is null or the world is not existing. Please try /fs setspawn to give the player a location to spawn OR remove the permission : FirstSpawn.hold
I hope this helps you
@Emmerella Yes it was on my todo list but I added it here to. This will be in the next release.
@TakeMeNL
This error appears in console on 1.6.2 builds
Hi, I was wondering if there was a way to add more than one custom command? Like one to teleport players to the regular spawnpoint instead of the first spawnpoint?
@Kwumsu The permissions are case sensitive. As far i checked everything is working
The Permissions aren't working
@edric12 Thanks for posting!! As i see it, you didn't setup the plugin right. Please ensure that SpawnPoint and FirstSpawnPoint are set correctly
2013-04-08 13:50:20 [SEVERE] Could not pass event PlayerRespawnEvent to FirstSpawn v1.6 (b84-git-d3d35108)
org.bukkit.event.EventException
at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:427)
at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62)
at org.bukkit.plugin.SimplePluginManager.fireEvent(SimplePluginManager.java:477)
at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:462)
at net.minecraft.server.v1_5_R2.PlayerList.moveToWorld(PlayerList.java:420)
at net.minecraft.server.v1_5_R2.PlayerList.moveToWorld(PlayerList.java:377)
at net.minecraft.server.v1_5_R2.PlayerConnection.a(PlayerConnection.java:1133)
at net.minecraft.server.v1_5_R2.Packet205ClientCommand.handle(SourceFile:30)
at net.minecraft.server.v1_5_R2.NetworkManager.b(NetworkManager.java:292)
at net.minecraft.server.v1_5_R2.PlayerConnection.d(PlayerConnection.java:110)
at net.minecraft.server.v1_5_R2.ServerConnection.b(SourceFile:35)
at net.minecraft.server.v1_5_R2.DedicatedServerConnection.b(SourceFile:30)
at net.minecraft.server.v1_5_R2.MinecraftServer.r(MinecraftServer.java:580)
at net.minecraft.server.v1_5_R2.DedicatedServer.r(DedicatedServer.java:225)
at net.minecraft.server.v1_5_R2.MinecraftServer.q(MinecraftServer.java:476)
at net.minecraft.server.v1_5_R2.MinecraftServer.run(MinecraftServer.java:409)
at net.minecraft.server.v1_5_R2.ThreadServerApplication.run(SourceFile:573)
Caused by: java.lang.IllegalArgumentException: Respawn world can not be null
at org.apache.commons.lang.Validate.notNull(Validate.java:203)
at org.bukkit.event.player.PlayerRespawnEvent.setRespawnLocation(PlayerRespawnEvent.java:35)
at com.DutchMasterServer.firstspawn.PlayerListener.PlayerRespawnEvent(PlayerListener.java:41)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:425)
... 16 more
2013-04-08 13:50:21 [INFO] Darcai lost connection: disconnect.endOfStream
"There are more plugins which are based on the same idea"
well, I CANNOT AGREE.
now, the bukkit 1.5.1 r0.1 beta released. so it is now minecraft 1.5.1 era. A lot of so-called "xxxx spawn" and "spawn xxxx" plugins, they do NOTHING with default bukkit server player spawnpoint. they are just '/spawn' command teleportation or warp plugin.
they cannot change the default death-respawn point for bukkit server player, either. e.g. change player1, player2, player3 and player4's death-respawn point to world_nether or world_the_end.
they also cannot change the default spawnpoint for server new comers(for their 1st appearing position in server) to world_nether, or world_the_end, but they still call their plugins with the name "spawn".
the only plugin with the similar idea to yours, what i saw is, RightOnSpawn, now it supports bukkit 1.5.1.
so, I am quite happy to see another plugin author who also has the idea about overriding/controlling the "default server player generating position" plugin.
:D
-=-=-=-
firstspawn v1.6 for cb1.5.0 TESTed with linux ubuntu 11.10 desktop + spigot 1.5.1 r0.1 b755, it also WORKS as with bukkit 1.5.0 dev. only one thing to be careful with is, the server-manager must configure the permission node correctly for normal-users and OPs, or it does not work(even OPs).
and it can handle multiworld, i set the "/fs set" position to overworld, world_nether, and world_the_end, all works.
but on spigot 1.5.1 r0.1 build 755, there would be some error lines reported in the console. but actually, the target user spawned correctly at the modified position.
hope there would be a fix for these error info in the console, due to they are really long, many lines^_^
similar to RightOnSpawn, it could not control the player death-respawn point modification.
so, for now the work-around is, use multiverse-core 2.5 beta, that plugin supports player death-respawn point modification, (supporting multiple worlds, supporting different worlds use single one death-respawn point in one specific world), so use firstspawn plugin + disabled firstspawnoverride: 'false' with multiverse-core to control spawn and respawn point in one bukkit 1.5.1 server.....