With screenwidth 80, Achaea wraps long lines of text at 80 characters. So a line like "You see exits leading north, northeast, east, southeast, south, southwest, west, northwest, and in (closed door)." will be wrapped to look like:
QUOTE
You see exits leading north, northeast, east, southeast, south, southwest, west,
northwest, and in (closed door).
With screenwidth 0, Achaea doesn't wrap text at all. The example above would all be a single line. Now, zMUD can also wrap the text instead of Achaea. With screenwidth 0 in Achaea, and zMUD wrapping at around 80 characters, it would look the same to the person reading it as screenwidth 80.
Now, the benefit of using screenwidth 0 and letting zMUD wrap the text, is that zMUD triggers still see the wrapped text as a single line. With screenwidth 80, here's what the trigger would look like to match that exits line I used above:
CODE
#REGEX {^You see exits leading north, northeast, east, southeast, south, southwest, west,$} {}
#COND {^northwest, and in \(closed door\)\.$} {}
That would match the first line, and then match the second if it followed the first. With screenwidth 0, it's much simpler:
CODE
#REGEX {^You see exits leading north, northeast, east, southeast, south, southwest, west, northwest, and in \(closed door\)\.$} {}
Also, to make Acropolis work with screenwidth 0, you'd have to change any trigger that matches multiple lines to instead match a single line. I'm not familiar with Acropolis, so I couldn't give any specific information on how it would need to be changed.