Inactive [GEN] SpawnControl v0.8.3 - Per-Player/Group Spawns (Now on DevBukkit) [1060]

SpawnControl v0.8.3​

Announcement:​

SpawnControl is being superseded by HomeSpawnPlus, a more advanced plugin that supports all of SC's features, and many more. Your homes and spawns can be imported directly from SpawnControl into HomeSpawnPlus.​

Feel free to contact me with questions/concerns/complaints.​

Tested with CraftBukkit 1060.

DevBukkit Page: SpawnControl
Bug Reports: SpawnControl Issue Tracker

Features:

• Per-player /home and /sethome
• Per-group /groupspawn
• Precise /spawn and /setspawn override
• Per-world global, group, and player spawns
• [NEW] Cooldowns for /home, /sethome, /groupspawn, and /spawn
• Optional respawn on death
• Optional respawn on join
• Toggles for home, groupspawn, and globalspawn features
• Imports player homes from spawncontrol-players.properties
• Imports group spawns from spawncontrol-groups.properties

Details:

This is a more full-featured release by far. Group spawns and global spawn are now supported. I'm detecting 'new' players (for global spawn) by checking their group (new players will be in Default) and looking for an existing home entry. If no home entry is found, the player will be teleported to the global spawn and their home will be set to the global spawn location. If someone has a better method for detecting this, I'd love to hear it.

The following permissions are available:

• SpawnControl.sethome.basic
• SpawnControl.sethome.proxy
• SpawnControl.home.basic
• SpawnControl.spawn.use
• SpawnControl.spawn.set
• SpawnControl.groupspawn.use
• SpawnControl.groupspawn.set
• SpawnControl.CooldownExempt.* (Sub-nodes: *, home, sethome, groupspawn, spawn)
• SpawnControl.config (for /sc_config [setting] [value])
• SpawnControl.import (for /scimportconfig and /scimportgroupconfig)

Dependencies:

• The Permissions (Phoenix) fork by TheYeti is optionally supported.
• Bukkit's native permissions are optionally supported.
• The BukkitPermissions group plugin is optionally supported.

Installation:

1. Download SpawnControl.jar and place it in your bukkit plugins folder

Optional Installation Steps (for Permissions support):

1. Download the Permissions plugin and install it
2. Add SpawnControl entries to your Permissions config as desired

Commands:

• /spawn - go to global spawn
• /setspawn - set the global spawn to your current location
• /home - go home
• /sethome - set your home to your current location
• /groupspawn - go to your group spawn
• /setgroupspawn [group] - set the group spawn for the specified group to your current location
• /sc_config [setting] [value] - alter a configuration setting

Settings:

• enable_home - Enables or disables /home and /sethome (0 = disabled; 1 = enabled) [Default: 1]
• enable_groupspawn - Enables or disables /setgroupspawn and /groupspawn (0 = disabled; 1= enabled) [Default: 1]
• enable_globalspawn - Enables or disables /setspawn, /spawn, and /globalspawn (0 = disabled; 1 = enabled) [Default: 1]
• behavior_death - Specifies the behavior when a player dies (0 = disabled - user returns to vanilla spawn; 1 = home; 2 = group spawn; 3 = global spawn) [Default: 3]
• behavior_join - Specifies the behavior when a player joins the server (0 = disabled - user spawns at last position; 1 = home; 2 = group spawn; 3 = global spawn) [Default: 0]
• behavior_spawn - Specifies the behavior of the /spawn command (0 = global spawn; 1 = group spawn; 2 = home)
• behavior_globalspawn - EXPERIMENTAL - Specifies the behavior when setting spawn (0 = does not override map spawn, 1 = overrides map spawn)
• cooldown_home [seconds] - Sets a cooldown in seconds for the /home command
• cooldown_sethome [seconds] - Sets a cooldown in seconds for the /sethome command
• cooldown_groupspawn [seconds] - Sets a cooldown in seconds for the /groupspawn command
• cooldown_spawn [seconds] - Sets a cooldown in seconds for the /spawn and /globalspawn commands

Downloads:

• SpawnControl.jar [Jar] [Jar - Direct Link]
• Source Code [Github]

Known Issues:

• None?

Changelog:

• 0.1 - First Bukkit release. Basic /home and /sethome support
• 0.2 - Group and global spawns, Permissions integration
• 0.3 - Working respawn on death; respawn on join (optional); configuration options
• 0.4 - Updated to use new OnCommand system
• 0.5 - Now uses PLAYER_RESPAWN; added basic multiworld support; added experimental (optional) globalspawn behavior; added missing /globalspawn command
• 0.6 - Proper multi-world support with per-world spawns
• 0.7 - Added command cooldowns; Permissions is now optional
• 0.8 - Fixed multiworld spawns; recompiled against CB #617; removed deprecated method calls
• 0.8.1 - Updated deprecated world loading method; tweaked spawn log message
• 0.8.2 - Switched cooldown time handling from server time to system time
• 0.8.3 - Added Hidendra's pull to support Bukkit's native permissions
• Full changelog

 

So by disabling the home commands in SpawnControl, that does nothing in terms of making it not conflict with another plugin that handles homes? Setting "enable_home" to 0 disabled the homes built in to SpawnControl but even after a restart didn't allow the other plugin to return to doing its job.

 

Correct. It just makes SpawnControl ignore the /home and /sethome commands.

If you want to allow another plugin to use those commands, you need to edit the plugin.yml file inside the SpawnControl jar file and remove the entries for the commands. Kind of a pain. CB doesn't give a way to unregister a command.

 

I get no config file :/ just a database one :?

 

The configuration settings are in the database. See the original post for configuration info.

 

Alright, thanks.

 

Hi, I actually seem to be having the opposite problem of Strebelsnecks'. That is, when anyone in the server dies, they respawn at the global spawn of the current world they died in. I realize this is what is supposed to happen, but I actually want players to respawn to the global spawn of the default world, despite what world they died in. I use the Nethrar plugin ( http://forums.bukkit.org/threads/tp...minecart-supporting-nether-portals-740.10874/ ) to create a nether world that players can use portals to travel to. The problem is, when they die, they respawn back in the global spawn of the nether, where ideally, I'd like them to respawn back in the default world. Is there some sort of setting I can adjust to amend this?

 

@PsychicDragonST It's planned for the next version

 

I added the plugin and it set the spawn point to Y: 0.0 X: 64.0 Z: 0.0 and I suffocate die and cant set the spawn point HELP

 

@Rockdude48 I don't know how you managed that, but try this: with your server OFF, make a backup of plugins/spawncontrol/spawncontrol.db, then delete that file. Restart your server and try to rejoin.

If you still have the same problem, there's something wrong with the world's built-in spawn point (it's at an unsafe location).

 

k thanks it workd

 

Cool, I'll be waiting patiently for the next release then. =)

 

This plugin rocks. I'm just wondering one thing. The compass is pointing to some random location that I don't even think was the original server spawn. It points to the same location, in the middle of a lake, for everyone. I tried "behavior_globalspawn" and reset the spawn, and it still points to this location.

I'm not sure if this is caused by this plugin, but if it is, could you please let me know what I have to do to fix the compass direction? Thanks.

 

@placeboing I believe compass locations are currently broken in Bukkit.

 

How can i make it so it's the exact spawn only when new players join? I don't wanna base this off of groups.

 

i just instaled spawn control but when players join they spawn att the global spawn and not at thier last location

nwm it's working now

EDIT by Moderator: merged posts, please use the edit button instead of double posting.

 

What do you mean?

 

I mean I want it so if a player has a newly created account in the world, it spawns at a certain location. I don't want it for everyone.

 

Where is everyone else supposed to spawn?

 

I want new players to spawn at the same place as everyone else without them spawning on top of a building or somewhere else.

 

@Guard1an I don't really understand what's not working for you. Using the default setup in SpawnControl, new players will spawn at global spawn. Everyone else rejoining the server will be at the same spot they were when they left. Existing players who die or use the /spawn command will be returned to the global spawn.

 

When new players join, they don't spawn at the location I want them too, they spawn randomly. However players that type the /spawn command spawn at the exact location.

 

@Guard1an Have those players ever been on your server while SpawnControl was installed? (on a past world or whatever) If so, SpawnControl won't see them as new, because it has a record of them.

 

No, I tried this with my own account. I deleted it and logged in, when that happened, I was spawned near the spawn location, but it was on top of my spawn building, it wasn't on the ground.

 

@Guard1an Deleted what? If you just remove your player dat file without removing your spawn entry from the SpawnControl db, you'll get the behavior you're describing (random spawn).

 

Alright it worked, sorry for bothering you, and thanks.

 

Im sorry if Im missing something here, but a config file isnt getting created for me when I restart my server after placing spawncontrol in the plugins file. I get the “spawncontrol” folder created, but all thats inside it is spawncontrol.db how do I get the config?

 

@mythcaptor The config is in the database (the db file). You can set config values from ingame with the /sc_config command (see the first post in this topic for full directions).

 

@Timberjaw

How do I make it so that /setspawn will save the direction I'm looking toward?
I want to spawn facing north, but no matter what I do, I spawn facing west.

 

It doesn't work for me
Even though I have permissions installed and working on other plugins it just keeps telling me:
[SpawnControl] Permissions system not enabled, using isOP instead

I've doublechecked the nodes several times but I can't get it to work
Permissions 2.7.3

 

I believe this is a server/CB limitation, but I'll look into it.

2.7.3 is working for me. It must not be installed correctly. Look for "[Permissions] version [2.7.3] (Phoenix) loaded" in your server log. If it's there, please use pastebin.com to share your entire startup server log.