@Makarios Ever since the server move, gmcp room events seem to be super inconsistent when they arrive compared to the next room's message, whereas previously they were always before any visible message. Was this intentional, or an oversight? And any chance it's going to be fixed back to the way it was?
@Ahmet did you turn compression off recently? I know that the point in time when gmcp is received/processed is different with mccp on and off. I don't if that's a mudlet quirk though.
@Keneanung Oh that's beautiful. I've had compression off for ages though, guess I just noticed the issue recently. It's been breaking a good number of my scripts in the past week or so. Super frustrating. Thanks!
I hate compression. If you send a gmcp request with it turned on, you have to wait for the next prompt or send some kind of input to receive the update. With compression off, th e gmcp update is sent/received immediately.
I am retired and log into the forums maybe once every 2 months. It was a good 20 years, live your best lives, friends.
At least room gmcp seems to be at the end of a room description, if the room description is large enough to be sent in two packages, room gmcp is in the second package.
Mudlet seems to process gmcp before visible text.
With compression on, mudlet waits for the complete desc before uncompressing and processing, thus gmcp is at the beginning of a received block.
With compression off, processing happens immediately, meaning room gmcp is somewhere in the middle of the desc block.
Trying to make some nice charts in a help file. The problem is, the majority of the gaps formed from spaces disappear. I might have said that all large groups of spaces get reduced to just one space, but that's not true: there are some lines that still work. I've double check that there are no tabs, just spaces (ascii x20). The compression only happens most times, and I've been able to discern no rule as to why it would for the lines it does on those and not the others.
Achaea's HELPs, journals, and letters all inherently wrap text at 72 characters, (I'm pretty sure news posts have a different character limit, it's why everyone's fancy ASCII wedding invitations come out awful.) and when it wraps a line, it deletes any repeated white-space characters. If you make sure no line exceeds 72 characters, it doesn't wrap any text, and so it doesn't eat your white-space formatting, which is why it seems inconsistent. I keep a notepad file with a line of 72 dashes for this reason; I'll c/p it at the top of the editor, and use that to gauge how long each line can be until you need to manually return the cursor so Achaea won't blow up your formatting.
Achaea's HELPs, journals, and letters all inherently wrap text at 72 characters, (I'm pretty sure news posts have a different character limit, it's why everyone's fancy ASCII wedding invitations come out awful.) and when it wraps a line, it deletes any repeated white-space characters. If you make sure no line exceeds 72 characters, it doesn't wrap any text, and so it doesn't eat your white-space formatting, which is why it seems inconsistent. I keep a notepad file with a line of 72 dashes for this reason; I'll c/p it at the top of the editor, and use that to gauge how long each line can be until you need to manually return the cursor so Achaea won't blow up your formatting.
i recently updated the mapper and now room numbers do not display correctly. anyone else encounter this problem and know how to fix it? this is what it looks like..
You know the following relevant rooms:
Shadows of Nature (
edit: nevermind, restarting mudlet solved the issue.
i recently updated the mapper and now room numbers do not display correctly. anyone else encounter this problem and know how to fix it? this is what it looks like..
You know the following relevant rooms:
Shadows of Nature (
edit: nevermind, restarting mudlet solved the issue.
what major and minor traits are recommended for an intelligent spec magi?
Major: Brilliant, Quick-witted (or Nimble if you're purely going 1v1/prep magi), then a third of your choice (Either sitcky Stirrups or Health Inspector is pretty good)
Minor: Blissful Ignorance, then whatever the hell you want
what major and minor traits are recommended for an intelligent spec magi?
Major: Brilliant, Quick-witted (or Nimble if you're purely going 1v1/prep magi), then a third of your choice (Either sitcky Stirrups or Health Inspector is pretty good)
Minor: Blissful Ignorance, then whatever the hell you want
what major and minor traits are recommended for an intelligent spec magi?
Major: Brilliant, Quick-witted (or Nimble if you're purely going 1v1/prep magi), then a third of your choice (Either sitcky Stirrups or Health Inspector is pretty good)
Minor: Blissful Ignorance, then whatever the hell you want
Meticulous care for a minor, too.
And Clean freak. Tsol'teth made y'all smell something awful today.
Comments
GMCP documentation: https://github.com/keneanung/GMCPAdditions
svof github site: https://github.com/svof/svof and documentation at https://svof.github.io/svof
Mudlet seems to process gmcp before visible text.
With compression on, mudlet waits for the complete desc before uncompressing and processing, thus gmcp is at the beginning of a received block.
With compression off, processing happens immediately, meaning room gmcp is somewhere in the middle of the desc block.
GMCP documentation: https://github.com/keneanung/GMCPAdditions
svof github site: https://github.com/svof/svof and documentation at https://svof.github.io/svof
Anyone else manage to fix this headache?
Here:
------------------------------------------------------------------------
edit: nevermind, restarting mudlet solved the issue.
Just curious
Minor: Blissful Ignorance, then whatever the hell you want
I always take knife thrower anyway for bombs.