Wtf?

[Rhyden]

Other people have probably experienced this before.

Code Select Expand

emote ~sword first, @ charges.

translates into:

Code Select Expand

~sword first, the grey, long-eared wabbit charges.

Also,

Code Select Expand

say (~sword first, charging) What up, doc?

translates into:

Code Select Expand

your Sword-like carrot first, charging, you say in sirihish:
  "What up doc?"

I've already bugged it in game, I was just wondering if anyone else has noticed this before (and/or bugged it with me).

[ThirdEye]

I've noticed it...Not bugged it though.

[cyberpatrol_735]

I've noticed it...Not bugged it though.

Ditto, I just ignore it?

No need with arm 2.0 being worked on I figure.

[daedroug]

I believe that it's so that you can't go:

Code Select Expand

>emote ~bartender jumps up and down and screams at @
The burly bartender jumps up and down and screams at the annoying elf.
In other words it's to stop players from giving actions to NPCs when in all reality that shouldn't be able to.

[Rhyden]

Good point.

Maybe it could be made so that this could work just for items? Probably something for Arm 2.

[daedroug]

Yeah I always actually liked it better when muds had objects and people set as 2 different tags.

[Lizzie]

I just work around it.

em Her sword-like carrot first, @ charges at the wascally wabbit.

Just type out the thing in the front. As long as it\'s just an object and not a person it will work fine. If it\'s a person you could try adding the word \"with\" or \"while\" or give the first half a verb. Using the same example:

em Thrusting ~sword first, @ charges at the wascally wabbit.

or

em While ~sword thrusts in the air, @ charges....

etc.