That makes me sad. :(

Well, Melody is an activiated ability, so if your a bard, and dont want to use it, you simply dont use it. Just like if a ranger wants to fire every shot, he never has to /autofire

Would be nice if you could disable the use of /melody if you wanted a more "authentic" feeling. As a bard who played since 1999 I rarely used melody after it was implemented...I of course had twisting ingrained in my memory. Once I fell asleep during an RZ raid in time and woke up...fingers still twisting...apparently I kept all 4 songs up the entire fight while asleep for about 10 minutes.

As far as the client goes...there are several bugs with singing songs...they lock up occasionally preventing you from twisting. Also whenever you twist every pulse actually removes the song and then re adds it like it overwrites itself as a buff...so I imagine this is controlled serverside in some respect...I imagine that the serverside is waiting for a command that the song successfully played before going onto the next song (i.e. if you had high ping times melody rates would be different based on lag levels)...based on how songs are handled I imagine they are emulated to be much like spells instead of like songs. The fact that /melody sings the first song gives the impression that it is waiting for a response from the server to stop singing that one and start singing the next that it is simply not getting.

As far as adding it *purely* client side I'm sure its possible, as macroquest allegedly had a feature that could do it...it would simply look for the casting dialogue and when it disappeared (the song was sung) it would stop the song and move onto the next one. However, if someone develops this, it would be available to anyone who downloaded it.

Occasionally when singing songs everything will lock up and it won't let me start singing other songs but a song will keep playing...won't let me do anything until I start singing that song again then it will unlock...I'm guessing this has to do with responses from the server about song activity...i.e. confirming that it got a song started/stopped...which aren't getting reported properly which is whats causing the problem client side...this is also what I would guess is causing the problem with /melody...some response saying yes we got that song request yes we gave you song effect yes we got that song stopped yes we're starting the next song etc...don't know too much about the programming just best diagnosis I can give with what I do know...

~MrGPAC

I'm going to bump this....not specifically for /melody. I can twist fine, however It's hard to twist at ALL when the songs lock. My songs tend to lock fairly often...enough to make people I'm grouping with think I'm weaving with my nose :P

Has there been a fix for this? I'm thinking there hasn't....but then again I remember bard code being a nightmare

Isn't #melody working for this on emu ?

Yeah, #melody has replaced /melody on EQEmu.

Ok, sorry I searched (I really did too ;P) and couldn't find any commands like that. I'll be sure to pass it on to some other bards who just figured it was broke. Is there a list somewhere that would have commands like #melody that would not be available on live? I'll look again just incase I missed it.

What about the whole song locking thing? I quoted Gegan above because he nailed the same problem I'm having with songs locking...it's been driving me nuts! Here's the description of the problem again:

Thanks again for the help!