Personally, I would find coding many things easier if there was a setting to disable server-side linebreaks where text wraps wround. i.e., let the client deal with the wrapping. Maybe something like CONFIG WRAPWIDTH OFF or CONFIG WRAPWIDTH 0. Personally, this would make things easier for me when coding to catch stuff and put it into a seperate space, or the like.

If anyone is passionately against this idea, say so. I don't see why anyone would be. Oh, and say if this woul dhelp with your coding as well.

I don't understand, isn't 250 long enough for you?

Ever looked at a verbose room description with wrapwidth 250?

On my zmud...

Centre of the Necropolis.
It is difficult to detect any features of the room, due to the powerful field of energy that is put out by the Megalith of Doom, absorbing all but the darkest of colours and dominating everything else in the room. The architecture of the room is
designed to accommodate the Megalith of Doom with a high dome that forms the entire ceiling. A circular series of steps descends three tiers down to the indentation in the centre of the room where the Megalith stands. Four archways lead out of the
room to the other areas of the Necropolis, where candles and other illumination can barely be detected through the powerful force of the Megalith. Rising up from cracks in the floor, the Megalith of Doom towers above everything here, polluting the
air with its foul fumes. Obfuscated by clouds of shadow, a pyramid of polished marble rises grimly through a pile of bones and rotting bodies. The subtle flows of nature culminate in this growing rose of blackness pulsing with divine radiance. A
sigil in the shape of a small, rectangular monolith is on the ground. A hunting trophy bearing Genevieve's head is proudly exhibited on a nearby wall. Sitting on its haunches, a bloodhound rests here. There are 5 Ur'Guard Grand Marshals here. The
Keeper of the Megalith stands here radiating a tainted presence. The body of a young rat lies here. A dead rat has been left here. There are 2 corpses of a black rat here. The body of a dead baby rat lies here. Xukeria, Chaotic Requiem is here. She
wields a worn lute in her left hand and a beryl encrusted coral wand in her right. Halamir is here. He wields a black ash lute in his left hand.
You see exits leading north, east, south, and west.


I solve the problem personally by changing it to the width of the screen, but that just means I only have slightly longer lines, not full ones.

A verbose room description, or a lengthy post can exceed 250 characters. Besides, if I set it to 250 then I have to resize my client window to ridiculous proportions just so I don't get linebreaks in odd places. The problem with massive linebreaks is that they will always cut off in the middle of a thing so it's kind of inefficient. No wrapping linebreaks at all would mean that they are all done by the client, so it wraps efficiently to your window size, and it's all treated as one line, code-wise, rather than as lots, making it easier to, say, send all CTs off to a seperate window.

Which is why you should just set it to whatever wrap size your resolution and window size will support. Mine is around 100 or so. I could change my resolution to huge but I like having the text a bit larger so I can see it easily.

I'd like this, actually. Would be nice.

It would also make it a _lot_ easier to capture warrior affliction lines...

Its not gunna happen, based on how rapture works. Sorry!

That's what they said about expanding it past 80, but that happened.

Of course, the fact that they only went to 250 instead of unlimited suggests that they're not going to come back to this question. Having 250 is already a huge huge huge step up.

You can get around this using regular expressions.

For example, instead of matching: "You have regained equilibrium."
Try this instead: "You( |\\n)have( |\\n)regained( |\\n)equilibrium\\."

It's messy to look at, but it works for me.

I'll have to play around with that. MUSHclient requires that you specify how many lines a particular trigger will match. So what I do for knight afflicts is just set 2, have
^.+you.+$^.+.+$


>_>
So not off topic...

I just gave up trying to match knight afflictions.
For me, having a nice neat 80 character wrapwidth was better than working out the combat triggers.

Well, my sources tell me that Achaea, and quite probably the Aetolia and Imperian as well, have implemented this. Don't mean to nag, but are we going to put it in as well?

Achaea has had it for quite a while now, which is why some people started asking for something similar here. It was sitting in the Rapture code for a while before they realized they hadn't finished it and put it to good use, so they decided to go ahead and get it done. The setting of your width to 0 is a special case, that tells Rapture to turn off the wrapping. The same thing should then be possible in Lusternia, but it has to be figured out how. I would be very interested in seeing it happen, even if just to make client-side word wrapping work 100%.

This really wouldn't be necessary if knight messages gave a line break after the weapon connects and when the affliction message starts. I have no idea how many people have gotten frustrated needing 5 triggers for the same affliction and decided it wasn't worth the effort to PvP in Lusternia, but it has certainly happened.

I agree that this formatting should rather be done on the client side. I've argued with both Avasyu and Dranor about it over at Imperian but they both said it couldn't be done (despite me pointing out that Achaea had it) and that there was no need for it. I've lost my interest in trying to debate for this feature though, ever since I switched to ILua where I made my own trigger parsing system and subsequently an unwrapper-system.

The main trouble isn't the actual wrapping though, it's how it wraps. In Imperian Rapture breaks the lines sometimes before a space (effectively removing that space) and sometimes after (leaving a trailing one). Some messages changed randomly between the two, some were always wrapped before the space and some always after. This makes it more tedious to make a pattern for - not harder, just more annoying. This also makes illusions alot less effective since their wrapping isn't done in the same manner and therefor could be spotted every now and then. I am, however, pleased to say that it looks to have been made consequent in Lusternia. Kudos to the devs if I keep on not finding this bug.

Concearning warrior afflictions. With the right set of regexp you shouldn't never need that many patterns. One for the actual affliction and perhaps a couple attack message patterns for illusion detection, which doesn't change between affliction. I haven't overly much experience with the warrior afflictions yet though, so I could very well be wrong.

I would like this as well. In Achaea it's easy, you just CONFIG SCREENWIDTH 0. I loved when that came out over there.

I don't know much about pk or illusions or anything, but I know when I copy something, and then paste it elsewhere, I have to edit it first because the formatting will be all messed up. That's the part that annoys me the most.

Triggering things with no wordwrapping would be far easier, I'll agree. There are ways to trigger just about anything with the wordwrapping on, however, even as random as it may seem. Apply the same logic to your code that you use in your head to figure out what's happening. That's how I deal with warrior attacks.

I want no warp linebreaks option too.. gee there should be a option for that!