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

Discussion in 'Inactive/Unsupported Plugins' started by Timberjaw, Jan 21, 2011.

  1. Offline


    SpawnControl v0.8.3

    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

    • 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
    • Imports group spawns from

    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)
    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
    • /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
    • 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

    Known Issues:

    • None?

    • 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
    Michonne, Huddl, BadgerLove and 5 others like this.
  2. Offline


    bug issue

    i was running your plugin fine then it broke

    so i downloaded a different "home" when i saw that you updated yours i downloaded it.(deleted all traces of other plugin)
    now whenever i die i get sent directly to spawn without clicking the respawn button when you die. and also (related to this i think) if you die by fire then you are still on fire when you spawn and continue to take damage.
    i dont know what version of bukkit this is because for some reason i cant find the link to the download site(fail on my part)
    but i downloaded it febuary 3rd if that helps(i updated both bukkit and craft bukkit)

    i know its the plugin because i diabled it and started it again

    other plugins

    world guard, world edit, border guard, general, ichat, the jail bad player one, LWC, myWarp, noon, permissions, and deathmatch

    please fix this i love your plugin and spawning is much more precise than generals
  3. Offline


    Dying and returning to spawn without clicking the respawn button isn't actually a bug. It's unfortunately the only way I was able to get respawn-on-death to work right now due to a Bukkit bug with player teleporting and the lack of a player spawn or health change hook. This will change back to the expected behavior whenever these issues are resolved.

    As for the fire issue, that was a known issue in v0.3.2 but was fixed in v0.3.3 (for me, at least!). My last check of the correct extinguish behavior was on CraftBukkit 218. Up through 239 at least, you can get your build number by using the /version command. You want to look for the part that looks like '-b239'. If your version is newer than that, the build number may or may not be available.

    Bukkit download site is here:
  4. Offline


    so are u going to update for the new builds soon or should i just deal with it or get an older version of craftbukkit?
    --- merged: Feb 5, 2011 8:01 AM ---
    btw thank you for making this plugin
    --- merged: Feb 5, 2011 8:02 AM ---
    and i mean the fire when i say update
  5. Offline


    I'm looking into the fire issue (again). I'm running on 239 now and updating to handle the onCommand stuff. I'll definitely be trying to keep SC up to date. Many builds don't break anything though. :)
    --- merged: Feb 5, 2011 8:22 AM ---
    Updated! v0.4 is updated to CraftBukkit 239. Now uses OnCommand.

    @huntj88 I couldn't reproduce the fire issue, but maybe rebuilding with 239 took care of it. Download v0.4 and see if it's fixed for you. :)
    --- merged: Feb 5, 2011 8:23 AM ---
    Can someone with Essentials tell me if SpawnControl gets along better with it now that they're both using OnCommand?
  6. Offline


    If i want to set the groupspawn for my outlaw group i tried:

    /setgroupspawn [Outlaw] (case-sensitive)
    /setgroupspawn [outlaw]
    /setgroupspawn Outlaw (case-sensitive)
    /setgroupspawn outlaw

    But it just tell me the Syntax i should use:

    Command: /setgroupspawn [group]

    Using Bukkit 239
  7. Offline


    Bug confirmed. Will fix.
    --- merged: Feb 5, 2011 6:23 PM ---
    Updated! v0.4.1 fixes the broken command issue.
  8. Offline


  9. Offline


    It looks like you're trying to use the MyHome /home AND the SpawnControl /home simultaneously.
  10. Offline


    ok ofund it myhome and spawncontrol conflict
  11. Offline


    still having fire issues with v0.4.1

    im just going to update bukkit and craft bukkit
    --- merged: Feb 5, 2011 9:06 PM ---
    k that fixed it. btw your plugin still works with craftbukkit 252 and bukkit 114 in case you wanted to know
    --- merged: Feb 5, 2011 9:07 PM ---
    edit: nvm it only didnt catch on fire after spawn the first time
  12. Offline


    Could you test if this is compatible with 252?

    EDIT: @huntj88 is this now fixed or not?
  13. Offline


    Although the spawn location changed, the original spawn location still appears to be protected from editing except for ops. Is there a way to have the spawn chunk follow with the changed global spawn?
  14. Offline


    the spawning works and all but i still catch fire occasionally if i die by fire
  15. Offline


    @huntj88 Haven't been able to reproduce the fire issue again yet but I will keep trying.

    @ganzor There is, I believe, but it may conflict with other plugins. I'll put it on my list of things to add, and probably make it optional behavior.
  16. Offline


    I removed the /spawn options from plugin.yml for the other spawn plugins I'm running (essentials and myhome) and no longer have any issues with this plugin. If you are able to do that it would be awesome - right now I just put brick all over the area so my users know they can't build there.
  17. Offline


    would it be possible to have multiple global spawns? with players dying reviving at the closest spawn?
  18. Offline


    ledhead900 amazing fix, do you think you could edit it so it takes out /warp so MyWarp pluggin works too? Truely amazing.

    -EDIT nevermind i just did it myself based on your concept. Thank you so much!!
  19. Offline


    I have installed this and can confirm it works, however the "precise" spawn point seems to be less than precise... unless I am doing something wrong.

    Using the /spawn command I go EXACTLY where I set the spawn point, however upon death players can spawn anywhere within 15-20 blocks of the designated spawn point.

    Any idea why this is happening?

  20. Offline

    Raymond Doerr

    I can't seem to use the /sc_config command, what am I doing wrong?

    I type in; /sc_config behavior_death 2 and I just get "Couldn't read value".

    Any help would be great, i'm totally stuck :(
  21. Offline


    Did you add the command to the permissions config.yml file?

    Nevermind, I am having the same issue...

  22. Offline


    Confirmed. Will have a fix up in a moment.
    --- merged: Feb 6, 2011 10:03 AM ---
    Updated! v0.4.2 fixes the /sc_config issue.
  23. Offline


    Awesome stuff Timberjaw, will see if setting behavior_death to 3 (since by deafult it seems to be set to 1) fixes the inaccurate respawning.

    --- merged: Feb 6, 2011 10:19 AM ---
    OK, the sc_config bug is now resolved, however the spawn point still is not behaving as one would expect.

    I have created a /setspawn which works GREAT if you use the /spawn command.... but when players die they seem to spawn in a random location in close proximity to the /setspawn coordinates.

    What am I doing wrong?

  24. Offline


    @Sol are you using any other plugins that implement /spawn or /setspawn? Essentials, General, etc.

    When you die, do you see the respawn window (where you have to click a button to respawn)? If you do, something is preventing SpawnControl from getting the death event.
  25. Offline


    I am not using General or Essentials. I am only using Permissions, Healthy, Guestbook, and some MOTD plugin.

    The respawn button is not appearing when I die, so the auto respawn is working... however the spawn point is not accurate. :/

    Everyone who is testing this on the server, happens to be on the OPS list, if that matters?
    Also, when anyone else dies there is no RESPAWN button, but when I die, there is! Whhhaa?

    --- merged: Feb 6, 2011 10:33 AM ---
    OK, so I decided to open the spawncontrol.db file in notepad, and noticed the behavior_death option is still set to 1, even though I commanded it in game to 3, and it confirmed the change. I tried to manually edit the file in notepad which then corrupted it and caused the server window to spew all kinds of errors like crazy.

    I'm to the point of DERP

    I have also tried modifying the behavior_join command to 3, yet players still seem to login at the last place they were... it's like the data is not parsing to the server or something?

  26. Offline


    Bug confirmed. I think I'm the DERP here. ;)

    In other news, I was also able to reproduce the fire issue again. Seems like it happens if the server is lagging (either due to lots of players or because the server is working overtime to load the spawn area chunks after the player dies).

    Try the attached v0.4.3-TEST file and see if it sorts out the respawn issue.

    Attached Files:

  27. Offline


    OK sick as, I'll give it a go now then and report back.

    Still seems broken... the area that the player can spawn in seems smaller now (maybe 8-10 blocks instead of 15-20) but it's not 100% accurate.

    We have a spawn "area" where we would prefer players to spawn inside of. Currently they often appear on top of trees, our outside of the perimeter. :/

    It seems to now work properly for behavior_join, but it's still broken for behavior_death

    So, a recap:
    - Works fine with /spawn command
    - Now works fine with behavior_join
    - Still broken with behavior_death

    *ON A ROLL*
    On a possibly related note... now suddenly we have "ghost pigs" that appear. Some people see them, others don't, and nobody can kill them. They disappear on a relog, but shortly afterwards will appear again usually in plain view of the player. These "ghost pigs" only appear around the spawn area.

  28. Offline


    Updated my fix for Essentials - Compiled it against ver 170 "Dev build" < "current latest as of typing this" of Essentials
    --- merged: Feb 6, 2011 1:02 PM ---
    Ghost pigs "Client sides animal spawn" not caused by this impossible check your craftbukkit version, It can happen sometimes and it happens a lot if u spawn them with a command of some sorts.

    as for the spawn issue are by any chance using the plugin Essentials as well ?
  29. Offline


    It still won't work with essentials. (Sethome -> Behavior_Death = 1)
    Maybe it woulb be better, if the commands where Pluginspecific like /sc_sethome XXXX and /sc_home XXXX
    So the essentials/generals commands can be deactivated.

    Edit: It's necessary for me, cause i need the other functions of essentials like playerlist,item,give,time and esspecially the logintext. Is there a alternative without a /setspawn /spawn /home /sethome functionto deny conflicts with SC? :)
  30. Offline


    No, have already mentioned which plugins I am using and Essentials is not one of them, so I'm afraid an incompatibility is out of the question in this case. Also, we do not spawn anything on the server I am currently running... we are purely survival only so we have no commands of any sort (apart from /setspawn now of course) and do not spawn animals or monsters of any kind.

    Also using latest build of Craftbukkit (259).

    So yeah, not sure why it's not working properly or why the ghost pigs (it's pigs only, and they only happen in the spawn area) suddenly appeared. If I disable this plugin, the ghost pigs go away. Something is calling something else, somewhere...

  31. Offline


    hmm that sure is a really strange sideeffect I have not noticed it all yet on the same build btw.

Share This Page