Inactive [TP] MyHome v2.3 [BukkitDev, 1.3.1-R1]

Discussion in 'Inactive/Unsupported Plugins' started by Spathizilla, Apr 17, 2011.

  1. Offline


    MyHome v2.2
    Release Date: 1st March 2012
    Yes, MyHome 2.2 works on 1.2.3, Try it.

    Recommended Craftbukkit Build: 1.1-R4+

    Permissions Support:
    MyHome can use Permissions 2, Permissions 3, PermissionsEx, GroupManager, bPermissions, bPermissions2 plugins or the built-in SuperPerms to manage permissions and in some cases, user/group settings also.

    Economy Support:
    Supports iConony 4, iConomy 5, iConomy 6, BOSEconomy 6, BOSEconomy 7, EssentialsEco and MultiCurrency to allow charging for using MyHome commands. This is provided via Register

    Getting Help & Feature Requests:
    Please use the MyHome DevBukkit ticket system to report bugs and submit feature requests. There is also a forum where you can ask questions which are not ticket suitable.

    ChangeLog v2.2:

    Important: You will need to re-generate your config file as it has completely changed.
    • Fix: SuperPerms now correctly allows ops to run commands (when enabled)
    • Fix: Decreased the sensitivity of movement detection
    • R5: Updated to new event listeners
    • Localization: German Translations: Thanks to Maxs
    • Localization: Updated Russian Translations, Thanks to MisterFix
    • New feature: Only allow /home to be used within x blocks of their home point
    • Per user/group distance node: myhome.distance.home
    • New feature: Table name in the database can be changed
    • bPermssions 2 support
    • More cleanup and optimization
    • New config layout - remake your config! [New config.yml]
    New per user/group node:
    * myhome.distance.home - Maximum blocks away from their /home point that /home will work.

    Older changes (open)

    2.1b only: Fixed non PEx plugins failing because I am an idiot
    2.1a only: Fixed an NPE when using SuperPerms

    Important: Be sure to update the permissions if you allow players to bypass the economy costs.
    • A massive permissions overhaul to make things more reliable
      • bPermissions support added
      • SuperPerms support added
    • Feature Localizations (english, spanish and danish so far)
    • Feature: Some commands (like deleting homes) works via console
    • Bug Fix: Zero second timers no longer block in laggy servers
    • Bug Fix: Beds cannot /sethome if the user doesnt have that permission
    • Lots of cleanup (you wont see this bit).
    • Permission Change: Economy "free" permissions no longer included under myhome.home.*
    Permissions changes:
    (*) - Allow /sethome and /home usage for free
    ( - Allow /sethome usage for free
    ( - Allow /home usage for free

    Added /sethome which can be enabled in the config (Config: allowSetHome = false)
    The new /sethome uses the same permission as /home set so no extra permissions needed.
    Added a cooldown for setting the home position (Config: coolDownSetHome = 0)

    v1.9.4c - Unreleased (fixed with a symlink on the webserver):
    Fixed the update url going to lib/lib.

    Updated SQLite download urls.

    Added Manifests to JAR to fix lib issues

    Forked plugin from 1.9.3
    Fix for onPlayerJoin changes in Bukkit
    Sergey95, Hopium, Phaedrus and 3 others like this.
  2. Offline


    Why PermissionsEX don't work?


    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: May 13, 2016
  3. Offline

    City Builder


    Our users can't seem to use either /sethome or /home When they try it simply tells them that using /sethome sets the home position if enabled in the configuration file.

    Here is the configuration file:
      compassPointer: true
      allowSetHome: true
      respawnToHome: true
      bedsCanSethome: 0
      bedsDuringDay: true
      enableBypassPerms: false
      loadChunks: true
      opPermissions: true
      locale: en
      useColors: true
      enabled: false
      enableFreePerms: true
      globalSetHomeCost: 0
      globalHomeCost: 0
      costByPerms: false
      additionalCosts: false
      globalCoolDown: 0
      globalWarmUp: 0
      globalCoolDownSetHome: 0
      coolDownNotify: false
      warmUpNotify: true
      timerByPerms: false
      additionalTime: false
      abortOnDamage: 0
      abortonMove: false
      applyDistanceLimits: false
      enableDistanceBypassPerm: true
      distanceByPerms: true
      additionalDistance: false
      globalMaxDistance: 0
      downloadLibs: true
      sqliteLib: true
      mysqlLib: true
    I cut out the last part with the info for connecting to our mysql database for obvious reasons.

    We're using bpermissions for our permissions and have added both of the nodes that are needed.

    Only admins seem to be able to use both of the commands without problem, but not any of our member or sponsor group which both have the proper node permissions in the bpermissions group file.

    Startup server log shows no errors for myhome what so ever. All shows normal startup.

    I must be doing something wrong somewhere but not sure what.

    Could somebody please help me with this.

    Thank you
  4. Offline


    Those are not the only permissions you need.

    I'm guessing you only saw the two that were changed in MyHome 2.1?

    You'll probably want:
    - myhome.home.basic.*
    - myhome.home.soc.*
  5. Offline

    City Builder

    Yes your guess would be correct. Thank you for the link.
  6. Offline


    Is it possible for this plugin to convert homes from CommandBook to this plugin? I would love to change over for the homes portion but I have over 560 homes saved with CommandBook on my server - it would cause problems if I just deleted them all
  7. Offline


    Do you mind posting your groups.yml ? I am having the same issue and cannot get MyHome working with bPermissions.
  8. Offline


    For 1.1-R-4, the only glitch is that when someone does /home, whether it being to a friends house or their's, they go invisible. Hopefully this gets fixed sometime. [gold]
  9. Offline


    Please make sure your plugin is ready for R5 - Thank you! :)

    It also seems to not be working with the latest version of bpermissions (as of 2/20/2012)
  10. Offline


    On my server ops can't do /sethome or /home set it only says /sethome - sets the home position if enabled in the configuration please help!
  11. Offline


    Please make sure your plugin is ready for R5
  12. Offline


    Please update This plugin to Current this is honestly 1 of my favorite plugins Along with mywarps My server will die with out these two plugins Cause no others compare So please update
  13. Offline


    Just so people stop posting tickets/here about it. MyHome 2.2 has been readied for R5 and just needs testing with it (when its done) and has bPermissions2's new api implemented.
  14. Offline


    thx, what about mywarp?
  15. Offline


    Yeh I did that too at the same time.
  16. Offline


    Since minecraft 1.2 came out today and people will be using the non RB builds.. Enjoy MyHome 2.2
  17. Offline


    you might want to update creaturebox Spathizilla i like useing the creatureboxes in stead of me spawning a hole bunch of mobs please and thank you
  18. Offline


    There is a dev version of it out for 1.1-R6 while they work on the 1.2-R1 RB.
  19. Offline


    Please update to 1.2.3-R-1 as soon as possible!!! great plugin thank you
  20. Offline


    That doesnt exist yet :p
  21. Offline


  22. Offline


    What happened with the option to set home by sleeping in a bed?
  23. Offline


    Neither does that :p

    Its still in the config.
  24. Offline


    Please! Update to Craftbukkit 1.2.3!
  25. Offline


  26. Offline


    the guy who makes bpermissions has kindly compiled a working version for 1.2
  27. Offline


    Thanks so much for linking me
  28. Offline


    No problem at all us server owners/trolls need to stick together!
  29. Offline


    lol! It even seems to be the version 2.2 jar I compiled and is on devbukkit...
  30. Offline


    Dirty bpermissions Dev !
  31. Offline


    Yeh well I guess its easier to just say "its a mc1.2 version" than say "its a 1.1-R6 version BUT IT WORKS FOR 1.2"

Share This Page