Recently, something changed. It was on the Lusternia-end because this did not happen to my characters in Aetolia/Achaea/Imperian. Anyhoo, I -really- hate this change and I was wondering what exactly it is...

Prior to the change, anything I entered an alias that was not locally echoed (and whereas I can changed non-stacked commands with my client between locally echoed and otherwise, I cannot change stacked commands via aliases), it was displayed on a new line. For example, this is how my former clot (which clotted 5 times when I typed clot once) alias appeared:

3381h, 3613m, 3020e, 10p ex-clot
You do not bleed my friend.
You do not bleed my friend.
You do not bleed my friend.
You do not bleed my friend.
You do not bleed my friend.

This is how it looks now:

3381h, 3613m, 3020e, 10p ex-clot
You do not bleed my friend.
3381h, 3613m, 3020e, 10p ex-You do not bleed my friend.
3381h, 3613m, 3020e, 10p ex-You do not bleed my friend.
3381h, 3613m, 3020e, 10p ex-You do not bleed my friend.
3381h, 3613m, 3020e, 10p ex-You do not bleed my friend.

-----------------------------------------------------------------------------------------------

This completely screws up my system for some reason (plus, it turns into a prompt-spam nightmare). It is something I can live with but will require a great deal of modifying to fix (sadly, my cliient just utterly hates this)... anyhoo, I logged onto my characters in Aetolia/Achaea/Imperian and checked this (with the exact same alias) and it works as it used to work.

Oh... this happened right after Lusternia crashed the other day... is this here to stay? *begs for it to be changed back*

I don't care if it messes up people's systems... the new way, if universally true is ugly and hard for people to scan.

change it back.

I feel as if NOTHING should be on the same line as the prompt... ever *sniffe*

Lusternia didn't crash the other day, it was a Rapture update.

Which is presumably the problem.

And it's playing hell with JAVA, too. (I WANT MY TRIGS BACK. )

Are you sure it's not just you?

clot
clot
clot
clot
clot
clot
clot
clot
clot
clot
You do not bleed my friend.
2889h, 2867m, 3336e, 10p, 15590w ex-
You do not bleed my friend.
2889h, 2867m, 3336e, 10p, 15590w ex-
You do not bleed my friend.
2889h, 2867m, 3336e, 10p, 15590w ex-
You do not bleed my friend.
2889h, 2867m, 3336e, 10p, 15590w ex-
You do not bleed my friend.
2889h, 2867m, 3336e, 10p, 15590w ex-
You do not bleed my friend.
2889h, 2867m, 3336e, 10p, 15590w ex-
You do not bleed my friend.
2889h, 2867m, 3336e, 10p, 15590w ex-
You do not bleed my friend.
2889h, 2867m, 3336e, 10p, 15590w ex-
You do not bleed my friend.
2889h, 2867m, 3336e, 10p, 15590w ex-
You do not bleed my friend.
2889h, 2867m, 3336e, 10p, 15590w ex-

That's more or less the problem. Even with gags, it is a spam nightmare. I went to do my alchemy thing and typed in a reflex and about had a stroke because it looked so freakish and crazy with prompts every line.

We got "upgraded" to a new version of Rapture which is the reason for the chaos on Saturday and some of you are having problems with the java client. If there's still a problem that you think may be related, please message Roark.

Upgraded my foot. Oh well, no one's fault probably. *tries to remember if he bothered Roark about this one already* *...bothers again just in case*

If the alias/trigger/etc locally echoes then it is fine. For example, let's assume "You bleed X health" triggers you to clot 5 times.

3381h, 3613m, 3020e, 10p ex-clot
You do not bleed my friend.
3381h, 3613m, 3020e, 10p ex-clot
You do not bleed my friend.
3381h, 3613m, 3020e, 10p ex-clot
You do not bleed my friend.
3381h, 3613m, 3020e, 10p ex-clot
You do not bleed my friend.
3381h, 3613m, 3020e, 10p ex-clot
You do not bleed my friend.

However if the alias doesn't locally echo (like RoA Client, Java, etc)

You end up with this:

3381h, 3613m, 3020e, 10p ex-clot
You do not bleed my friend.
3381h, 3613m, 3020e, 10p ex-You do not bleed my friend.
3381h, 3613m, 3020e, 10p ex-You do not bleed my friend.
3381h, 3613m, 3020e, 10p ex-You do not bleed my friend.
3381h, 3613m, 3020e, 10p ex-You do not bleed my friend.

And as you can see, this present a great deal of prompt-spam -and- it screws up a lot of triggers/reflexes/etc (which while can be fixed, the spam cannot).

Hmmmm... odd. Looks like it's time to switch to Zmud, Narsrim, instead of RoA Client.

I -hate- Zmud. RoA Client is so "made for stupid people like me" who like to be able to do everything in 3 clicks with some copy-pasting. *whines*

I hear MM2k is pretty good. It's a lot like RoA client, I'm pretty sure.

Estarra,

Is there /any/ chance we will get un-"upgraded"... if not, I guess it is time to start making a Zmud system *slits wrists*

Strange, I've been getting that since day one, way back in Open Beta. I often get actions appended to the end of my prompt when I cache in several commands simultaneously.

The fix to this is to get your client to check for the GA signal. See if your client mentions anything about 'Telnet Go Ahead'.

I'm just about positive Rapture has always had the GA, though.

Well, we can't go back to the old version of Rapture, but we are looking into the issue about the echo.

Simple solution, don't use echo! Cuts down all your input commands by half and is significantly better for Mages with illusions.

Are You folks looking into the issue about the JAVA aliases/triggers too? :/ *hope*

Actually, this is the problem.

With echo off, the action appends to the prompt instead of being on the next line as you can see in my example above. Whereas I have the echo on for most commands, you cannot force an echo for stacked commands in some clients.

Are you referring to the the fact that the responses are accompanied by a prompt, or are you referring to the response coming at the end of the prompt?

Edit:

Yeah, I'd say that your client isn't picking up on the Go Ahead. This suggests you've made some change to your client options lately. I'm assuming you don't have a linebreak appended to your prompt. There's a hidden signal, the 'Go Ahead', appended to the end of each block of sent text, regardless of whether there's a linefeed. To see it in action, add a linebreak to your prompt. That should get your triggers to work properly, though at a cost of yet more spam.

Ideally, of course, you'd have your client recognize the Go Ahead signal.