Need LSB Dev feedback on a bugfix/mechanic.

[UmeboshiXI]

#7830 (comment)

Basically my question is summarized in this post.

Specifically this:

Also interesting to note regarding retail behavior:

This song deletion behavior we see above with the bug happens on retail when you only have 2 max songs(The default with a >normal > instrument). I'm not sure if its a bug on SE's part but it does NOT happen once you have more than 2 max songs(3+).

When we fix the bug for OP:

Would we want to keep the deletion behavior when max song cap is 2. (Retail accurate but seems odd?)
OR
Would we want to standardize it with the fix for OP(Oldest song will not get deleted when newer songs are refreshed with song of same effect/tier)

[WinterSolstice8]

Thinking about it, I'm not sure there is a bug on retail

the 2nd bard has two song slots, and they are refreshing the 1st bards song (minuet), so minuet is refreshed but their oldest song is removed leaving 3 songs total, 2 from the 2nd bard and 1 from the 1st instead of 3 from one person without song

It seems to me it's a side effect of using bard songs badly rather than it being a bug? Because at that point it devalues bard swapping if it kept refreshing the other bards songs which I am guessing is intended by SE

[UmeboshiXI]

This can happen solo as well with no other BRDs involved. I'm just not sure why it would be different once you get modifiers that increase your song limits.

Example:(2 Song slots)(Retail Accurate): You cast Song 1, Then cast Song 2, then refresh Song 2 again. Result = Song 1 gets deleted. Song 2 gets reapplied.

But if you have something that gives you an extra song slot, this behavior does not happen anymore. Instead the song will simply refresh and no old effects get deleted(On retail).

If we want to keep the retail behavior for 2 slots then we can leave it as is and just fix the logic once you get have more than 2 song slots.

[WinterSolstice8]

With just one bard that sounds like a bug, that's really strange