WoW Petopia Community

@Mania:
So... apparently it's possible for users with incoming IMs disabled to send IMs. This makes it really hard to respond to them, if even to say "hey, you're not allowing any responses". Any chance of either not permitting users with IMs disabled to send IMs in the first stuff, or at least throw up a big warning along the lines of "you've got incoming IMs disabled - the user(s) you're sending this to won't be able to respond"?


And apropos this:

@Slickrock: That sounds most peculiar. The worst I've encountered is that I had to dismiss my pet and resummon it for RCL to refresh properly. You can also try a /reload - that causes RCL to be reinitialized completely. If that doesn't fix it, and there aren't any error messages in your chat window, then I'd suggest you raise a ticket over on WowAce for me, and ideally include information on which version you upgraded from (and to - was it the latest beta you grabbed, or the latest release?), your configuration settings and anything that might help me reproduce the problem.

I've had that happen. Couldn't respond to someone who PMed me and asked me a question. Even created a thread entitled "ATTENTION : <name>" but he didn't see it.

I'd vote for players being unable to PM at all unless they have incoming PMs enabled, except to/from Moderator. Otherwise it can also be abused for harrassment.

On the poultry forum I live on, they have it set so that people cannot send a pm to someone who has it disabled. However, if you have it disabled and you send a pm, the person you pm can pm you back.

Celi wrote:On the poultry forum I live on, they have it set so that people cannot send a pm to someone who has it disabled. However, if you have it disabled and you send a pm, the person you pm can pm you back.

I like that idea.

Howdy!

The version that I downloaded was whatever the Curse client gave me, didn't look to see if it was beta or not.

I did fix the problem by deleting the files in the WTF/server/charcter folder that pertained to RaidChecklist. After that, it worked fine. Perhaps there was too great a spread between the versions, and something in that cache file got messed up.

Glad to hear it got resolved. I'm a bit puzzled why it'd act up in the first place though - I've tried being careful to support upgrades seamlessly. >.<

Wait is a IM a PM? I'm lost :/

Probably PM. You'll notice in Slickrock's post that the PM button is missing