Periods eaten when placed after an emote target keyword

[Iota]

Periods seem to be eaten when placed after an emote target keyword in a multi-sentence emote.

Code Select Expand

emote leans against ~bar. She glances at ~dude.

yields

Code Select Expand

The fat-faced lass leans against a long wooden bar She glances at the muscular dude.

[tortall]

I've noticed that too.

Also, when using sing(maybe recite too) it cuts out apostrophes, which can make the words look weird. Like when you're trying to say we'll, it comes out well. Two different words.

[Mood]

Last post by tortall
in Re: Periods eaten when p...
on Today at 07:02:58 PM

I read this, and mentally gagged.

[Winterless]

Or you could just... make it so it doesn't do that.

Code Select Expand

>em leaning against ~bar, @ glances at ~dude

Leaning against a long wooden bar, the fat-faced lass glances at the muscular dude.

[RogueGunslinger]

Part of the new code that allows for multiple keyword? Like "l dude.man" or "tell ~tall.muscular Hi."

[Fathi]

Part of the new code that allows for multiple keyword? Like "l dude.man" or "tell ~tall.muscular Hi."

I remember the missing periods from back when I rolled up my first PC.

Fortunately, the test was negative. <3

[SMuz]

Hmm.. I never use two periods in an emote. An emote is a sentence; if I need two of them, I put them in two emotes.

[Archbaron]

Part of the new code that allows for multiple keyword? Like "l dude.man" or "tell ~tall.muscular Hi."

I remember the missing periods from back when I rolled up my first PC.

Fortunately, the test was negative. <3

<3