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

 

@OkinKun That's cool (CommandBook). MV does handle respawn-on-death though. I spoke to rigby on IRC briefly. He said that feature will likely be removed in the next version.

 

Another glitch to report, using build 518..

Basically when a player joins the server for the FIRST time, they always spawn in the random 16x16 spawn location which the vanilla server sets by default.

Kinda annoying, because that means we can't setup a proper spawn for new users to see what we want them to see.

However, players who die, or type /spawn, are still returned to the Proper spawn, set by SpawnControl.

BTW, I've disabled ALL plugins which had any interaction with any spawn related features. At least to my knowledge.

 

@OkinKun Any messages in console when they first join?

 

Nope, nothing at all. =/
Not even the usual [SpawnControl] stuff.

However, if I type "/spawn", the console returns with:
16:21:09 [INFO] [SpawnControl] Attempting to send player NikoKun to spawn.
And that works just like it should..

Makes me wonder if the server is trying to take priority over spawning, when new users join.
I really hope this is fixable. =/

 

• The Permissions plugin by Nijikokun is required for SpawnControl to work.
• 0.7 - Added command cooldowns; Permissions is now optional

I see what you did there.

 

Strange. I'm doing a very simple onPlayerJoin check. If the player doesn't have a home, it counts them as new, sets their home to the global spawn, and spawns them there. Either it's not firing onPlayerJoin like it should, or it's somehow thinking they have a home already.

I'll do some investigation on my end and try to reproduce the issue.
[MERGETIME="1299624962"][/MERGETIME]

Hmm? No idea what you're talking about...the OP says Permissions is optionally supported.

 

First you tell that Permissions plugin is required, then you say it's optional.

 

@Juze look again...

 

Yup, that's more like it!

 

The JAR (standalone) download is not .7

the zip is

 

Updated. Thanks!

 

Well, I hope the spawning bugs I've been experiencing aren't just happening to me alone.. =/
Has anyone confirmed similar issues? Cause if not, then maybe I need to do even more digging around in the way my server is setup..

 

hmmm.....i dont get how u change the spawn point? like the point u go after ur dead...it does direct me to home/global spawn/group spawn point....it directs me to a place where i setted as home a long time ago...

 

Is there anyway to force SpawnControl to spawn you to your group spawn in another world?

For example, if you're running around in world "nether" and you die, spawn control forces you out of "nether" and respawns you in the "SixtyGig" world at your group spawn's spawn point?

I have a semi-complex "zone" system on my server mostly based on your plugin for core functionality, basically, every single player gets their own "build area" in a grid, and they're set to groupspawns instead of playerspawns so if more than one player wants to share an area they can. But it still gives me as the admin control over spawn locations. (We don't allow /sethome, etc.)

Problem is, I'd like players to be able to go into the nether freely via a plugin like MultiVerse. But when they die, SpawnControl attempts to sent them to their groupspawn in the nether (that doesn't exist) and then sends them to the globalspawn inside the nether no where near their portal.

I'd rather it yank them out of the nether and place them back in their group's zone when they die, then they can run into their portal and go recover their stuff.

 

I'm not sure if it's related to this plugin or not, but my players Compasses are pointing to the original server spawn instead of the global spawn that I set for them with this plugin. Any ideas on how to fix this?

 

with CB 522 and spawncontrol 0.7:
whenever a player dies in a seperate world (in this case nether that is set up with multiverse)
the player is respawned in the main world at a somewhat random place, usually near the vanilla spawn, but way up high or very deep in the ground...

 

Perhaps you have behavior_death set to 3 (respawn at /home on death)?
[MERGETIME="1299703752"][/MERGETIME]

I plan on extending the current behavior_death setting to allow per-world configuration of death behavior, including world-swap on death. So the answer to your question is 'not yet'.
[MERGETIME="1299703802"][/MERGETIME]

Will check it out.
[MERGETIME="1299703871"][/MERGETIME]

Multiverse currently interferes with SpawnControl's respawn process. Nothing I can do about it yet as far as I know, but MV may be removing some of its spawn functionality soon, so we'll see.

 

i tried altering MV's config file to make it not try to handle respawning.... is it possible that spawncontrol is not passing the world data along with coords??

 

SpawnControl is definitely passing world data. The issue is that MV catches the player respawn event regardless of settings. At least, that's what the MV author told me.

 

hmmm... Oddly enough, I booted up the server today, after cleaning out the player inventory files (which also resets their coordinates back to spawn).. And for a little while, users were spawning PROPERLY, in the spot I had set before.
But then I rebooted the server, and cleared those files again, so we'd all "first-spawn" again, but this time it was spawning us in the random vanilla spawn. -_-

So it was working properly for a few minutes, for no reason that I can tell, but after restarting it stopped working again. =/

 

I'll fire up a fresh test server and hash these out without MV, then with MV and see how it goes. Based on my discussion with Rigby just now, MV shouldn't be interfering if it's configured properly.

 

Well, I don't think MV is interfering at all... I disabled it a couple days back... As in, completely removed the plugin for my plugin folder, for now.
But yet I'm still having these issues.

So maybe it's some problem with Bukkit?

I still want to know if anyone else is having this same issue.. =/ Can anyone test it?

 

ah makes sense, o well guess i got another thing to add to my list of stuff that i'm waiting for, a fix for MV

unless you have any other sugestions for multi-world plugins that do not interfere with spawncontrol?

 

It may or may not be MV. I'm still investigating that. Will post here when I have anything new to report, of course.

 

Author,

Please support the auto-updating plugin CraftBukkitUpToDate. To do so please provide a permanent direct link to the author of CraftBukkitUpToDate.

The below is information they provide

Show Spoiler Hide Spoiler

My Plugin didn't supported, how i get it to work with CButD?
Give me a permanent link to your Plugin, i will add it. That's all no changes at your SourceCode or something else, all I need is a permanent link to the newest version of your Plugin. A good place for this is http://www.dropbox.com/ or for OpenSource https://github.com/.

I really enjoy using your plugin and would like to see it work well with the above listed 'updater' plugin.

 

the original post mentions "settings" but i don't know where one is supposed to edit those settings. the only file created by the .jar is a .db file with plot points for locations. I want to use EssentialsHome as some of my players have already set their homes with that, but use SpawnControl's multi-world spawning capabilities.

I was able to use an SQLite editor to change the variables, but disabling Home just disabled it completely. Did not defer it to another plugin. Oh well, I will give up EssentialsHome.

What I want to know is this...what is the difference between a global spawn and a spawn. Here's what I want to achieve: http://forums.bukkit.org/threads/world-for-new-players.7795/

 

Sent my permalink over.
[MERGETIME="1299775577"][/MERGETIME]

If you want to use EssentialsHome with SpawnControl, you need to open up the SpawnControl.jar file and edit the plugin.yml file inside to completely remove the /home and /sethome commands. This will prevent SpawnControl from receiving those commands.

 

Quick question: is there a config file for this? I see a bunch of stuff about options, but in the SpawnControl folder I only see a database file.

 

Config is in the database. Available configuration options are listed in the OP and set using the /sc_config command.

 

Awesome, thanks much.
[MERGETIME="1299953610"][/MERGETIME]