Bard Melodies
 

Do they work? I'm trying /melody song1 song 2 song3

doesn't seem to be working, any suggestions?

I play on Storm Haven.


Best Regards,
Dave

not implimented.

Is is possible to get it implemented?? would that require a DB change or a recompile of the world?

they have to be codded in- which means recompiling the server files

Have to figure out how it works first.. which I haven't, I wanted to implement it a while back. My guess is it was probably handled client side and we just aren't sending the spell packets in the correct order for it to work.

First, a bard will memorize their songs. Then, they'll type /melody # # #. (I'm honestly unsure of the limit, but I believe it to be three.

This will continually cast those songs in the order typed, allowing the bard to focus on something other than singing, and sparing them some carpal tunnel =P

From the stand-point of use, it kind of works the same way as /autofire; you're looping something that used to be done manually. I figured that /melody would follow not long after that. Then again, I'm sure that it's quite different from a programming stand-point :)

I'll see if I can dig up a more detailed explanation of how melody works, though; I never want things taken just at my word if I can do something to provide solid proof.

Thanks for looking into this, K :)

There was no effective limit to /melody. You could string a ton of songs together in any order with it.

e.g. /melody 1 2 3 1 2 4 1 2 5

/melody was primarily effective in this extended manner because a rank or two of Mastery of the Past (or one of those style AAs) was bugged to grant bards immunity from fizzles to all songs (tee hee).

Normally, /melody is interrupted by fizzles, stuns, etc events that would interrupt songcasting. /melody could also be halted by the use of /stopsong or by tapping a song gem. I'm not sure how much of that functionality rests within the client and how much within the server, though.

I was already aware of how it worked from a conceptual pov!

/melody 1 2 3 4 sends the same packet to the client as casting a spell in slot 1 so I dunno, I'm guessing it's handled client side but the packets we send for spells aren't in a correct order or something.

Of note is that bardsongs don't seem to be pulsing on the client side. Songs that would normally generate quite a bit of spam (e.g. selo's accelerando) show one message on the first tick and then nothing -- yet remain refreshed throughout the time the bard is singing it.

Going to look into the casting business and see what might be up

Are there any plans to implement this sometime soon?

Bah, melody was horrible! Twisting was great...it kept the eccentric bards busy so they were the least likely to speak in a group. :)

Until this was added, most bards eventually quit due to carpal tunnel.

If anyone is actually working on this, please add the option to disable the melody feature.

LOL..It does work good for running and regenerating though. I also would just chant and selos and run around in circles. Could just about solo forever like that.

/melody is client side, once working you wouldn't be able to disable it.