When adding a world that is not the default world, and setting the ability to have pets in said world to true the plugin still refuses to allow pets in the added world.

This is what I have for my config file. I have added the world "skyworld" which is not the default world. When attempting to create a pet in the added world I receive the message "Pets are disabled in this world"

Send message that pet was loaded if -autoLoadSavedPets- is true
sendPetLoadMessage: true
worlds:
games: true
skyworld: true
enableWorldsByDefault: true

Strange. It works for me. Do they work in the "games" world?

Yes they work fine. I will try again when I get home from work and let you know.

On Sep 21, 2013, at 9:43 PM, "DSH105" [email protected] wrote:

Strange. It works for me. Do they work in the "games" world?

—
Reply to this email directly or view it on GitHub.

Make sure the world name is spelt correctly (including capitals).

Seems to be working fine now, though I have changed nothing.

Also, when selecting a pet using the pet selector in a world where pets are disabled it seems that the pet is not recognized, any changes you attempt to make to the pet are returned with You currently do not have a pet and you are also unable to remove it using any commands. To remove it I needed to unload the plugin, edit it out of the pet file, then reload the plugin...

Shouldn't the Pet be disabled anyway so that there is no instance online? I'm not sure I'm following exactly.

This still happening?

Oh, I have forgot to reply. Though I have noticed it. Everything seems a-okay though

Sent from my iPhone

On Sep 29, 2013, at 11:20 PM, "DSH105" [email protected] wrote:

This still happening?

—
Reply to this email directly or view it on GitHub.

Alright then. Reopen this if it starts to happen again.