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

MyHome v2.2​

Download MyHome v2.2​

Download MyHome (Static Jar URL)​

Release Date: 1st March 2012​

Yes, MyHome 2.2 works on 1.2.3, Try it.​

​

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-​

Installation | Configuration Options | Commands & Permissions | Support / Bug Reports​

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-​

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) Older changes (close)

v2.2b:
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:
(myhome.econ.free.*) - Allow /sethome and /home usage for free
(myhome.econ.free.sethome) - Allow /sethome usage for free
(myhome.econ.free.home) - Allow /home usage for free

v2.0.1

v2.0a:

v1.9.5:
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.

v1.9.4b:
Updated SQLite download urls.

v1.9.4a:
Added Manifests to JAR to fix lib issues

v1.9.4:
Forked plugin from 1.9.3
Fix for onPlayerJoin changes in Bukkit

 

What version of bukkit are you running? Have you tried updating the permissions plugin (version 2.7.2 is the latest). Is 1.9.x of Home, 1.9.5?

Is /t home a typo? Because if not, that's where you're going wrong.

 

yea it was a typo.... But: Thanks for the fix! i had permissions 2.7.1, updateing to 2.7.2 fixed it! don't know what changed, but thank you very much!!

 

Haha no problems, glad you got it working.

 

Just wondering if you were looking to make this multi-world compatible? The latest Essentials now provides this functionality which could be very helpful if combined with this great plugin.

 

It already is multiworld compatible. If you set your home set in world2 and then /home from world1, you'll be taken to world2's home.

 

Sorry, I meant have a home set per-world. This is the functionality I was describing.

 

Recommend: MySQL support!

 

I'm using CB 740, this version of MyHome 1.9.5.. The server loads Myhome without errors (even says 58 homes loaded).. typing /home does nothing, not even an error. The command doesn't log into the console/log.

I use SpawnControl, but the /home feature is disabled. EssentialsHome is not even in the directory, so no conflict there.

What happens when /home just does *nothing*? How do I fix this please!?

Oh yeah - I just migrated servers, too. It worked fine on the previous, but not on the new one? This is the only plugin that doesn't do anything, even though it's loaded fine.

 

Can you do so you have a home per-world?

 

Server log snip and permissions snip would be helpful.

 

As requested:

Code:

    Default:
        default: true
        info:
            prefix: ''
            suffix: ''
            build: true
        inheritance: null
        permissions:
        - myhome.home.basic.delete
        - myhome.home.basic.home
        - myhome.home.basic.set
        - myhome.home.soc.invite
        - myhome.home.soc.list
        - myhome.home.soc.others
        - myhome.home.soc.uninvite
        - mywarp.warp.basic.warp
        - mywarp.warp.sign.warp
        - mywarp.warp.soc.give
        - mywarp.warp.soc.invite
        - mywarp.warp.soc.private
        - mywarp.warp.soc.public
        - mywarp.warp.soc.uninvite
        - mywarp.warp.welcome

Code:

2011-05-08 23:27:23 [INFO] [MYHOME]: 58 homes loaded
2011-05-08 23:27:23 [INFO] [MYHOME] Permissions enabled using: Permissions v2.7.2
2011-05-08 23:27:23 [WARNING] [MYHOME] 'Help' isn't detected. No /help support.
2011-05-08 23:27:23 [INFO] [MYHOME] MyHome 1.9.5 enabled

 

It is on the list.

I guess since there is demand for this I'll have to look at adding it (with a config option to disable it too). I dont know whether /home should only warp you to the home within that world and not allow world to world teleporting. Opinions?

EssentialsHome was discontinued and re-merged with Essentials itself. Do you have a current 2.2.x version of Essentials?

No errors at all even on console?

 

Could you add setting the home with beds?

 

Would this be any time they got into bed or you have to be in a bed to /sethome?

 

Any time... so people can only set home when they have a bed in their home. (Of course I wouldn't give the the set permission)
Like it's implemented in Essentials.

 

You could try loading the server without the myhome plugin, then put it back in and change the listed permissions to myhome.home.basic.* and myhome.home.soc.*

See if that makes any difference, what other plugins do you have?

 

hello
i get this error
[SEVERE] Nag author: '<NoAuthorGiven>' of 'MyHome' about the following:
onPlayerJoin has been replaced with a new signature, (PlayerJoinEvent)

 

You're using what is now a very outdated version, update.

 

I get 0 errors in the console and before i uploaded the directory, exact structure, to the new host, myhome worked perfectly, which is baffling..

I do have Essentials 2.2, however, in the Essentials config I have /home and /sethome hard disabled (not even admins have this)

I have an enormous amount of plugins, but never had a conflict before. Can't see how it would affect them, considering my previous host (go-networks), myhome worked fine, and with my new host (hostrainbow), which has an exact copy of the directories, doesnt.

I will try to load server without myhome and redo permissions.. just cuz nothing else works

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

 

Random I know, but do the folders have the same permissions (CHMOD File permissions) on the new host as they did on the old host? Just in case it's restrictive and preventing you from accessing the files needed? Not sure if it would though, still may be worth checking though since nothing else seems to be sorting it.

 

All folders are set to 755.

 

Ok, just thought I'd ask as it's something people tend to forget to check when changing between hosts.

 

I gotcha.

It's so weird. Nothing has changed. Same Craftbukkit, same mywarp, same myhome... warps work flawlessly, but myhome didn't like the transition? I even re-downloaded the jar to make sure it wasnt corruption.. no dice. ><

 

I'm having the problem of /home [name] command for my players to go to other peoples houses. I have bukkit 740, the latest MyHome and permissions 2.7.2. When my players do /home [name] they just get a message saying they don't have permissions

Permissions nodes:
permissions:
- 'lockette.user.create.*'
- 'iConomyChestShop.shop.buy'
- 'iConomyChestShop.shop.sell'
- 'AutoRepair.repair'
- 'AutoRepair.info'
- 'AutoRepair.access'
- 'craftbook.*'
- 'general.spawn'
- 'myhome.home.basic.*'
- 'myhome.home.soc.*'
- 'general.player-info'

 

I'd say only allow per-world /home setting. Or even an option to toggle the behaviour? For example I have a creative and a "vanilla" world, so warping to homes between worlds would have the same effect as using a portal, so not really of use. Also allows people to quickly use "/home" without worrying about specifying which.

 

When people create a home it defaults to private. They have to type '/home public' for other non admins to visit.

@Spathizilla any chance that could be changed so we could select in the config perhaps whether to default to public or private? Just sometimes people forget to make their home public.

 

Khamseen is correct, homes are made private by default so only the owner and admins (with the right permissions) can visit them. I guess it shouldnt be too hard to add that config flag so homes are created as public automatically.

 

I find that /home is used for many purposes. Some of my players use it for their HQ. Some use it for their building sites. Others use it for whatever their present project is. The presence of a bed isn't always a good idea. They may want to have one site for respawning and another for /home. Therefore, if you were to add this I would recommend making it an option, not the default.

Sorontar

 

I haven't read through the full thread in a bit so this may have already been answered but any chance for iConomy support for this so that we can charge for /sethome and /home command usage?

 

It would never be the default and would have a config option for it.

Added to the list