Topic: Surprise

Posted under Tag Alias and Implication Suggestions

The bulk update request #4648 is pending approval.

create implication surprise_sex (1188) -> surprise (40103)
create implication surprise_kiss (1046) -> surprise (40103)
create implication surprise_buttsex (731) -> surprise (40103)
create implication surprise_transformation (89) -> surprise (40103)
create implication surprise_oral (39) -> surprise (40103)
create implication surprise_attack (31) -> surprise (40103)
create implication surprised_expression (14058) -> surprise (40103)
create implication surprised_face (922) -> surprise (40103)
create implication surprised_look (540) -> surprise (40103)
create implication surprised_eyes (143) -> surprise (40103)

Reason: Surprise request

Watsit

Privileged

surprise is too vague and generic, to me. surprised_face, surprised_look, and surprised_eyes should be aliased to surprised_expression since they're all basically the same thing (alternatively, surprised_eyes could be aliased to wide_eyed).

For everything else, I think they're separate enough actions to not need to be grouped under a generic surprise term. They may also be better named to unexpected_* since surprise_* denotes the response of the victim (they're "surprised" that something happened), but in some situations, the victim may not yet be aware and thus not (yet?) surprised. For example, an image of someone attacking another character from behind, the attacker about to hit and the victim completely unaware. There's no expression of shock or surprise from the attack, but it would appear to be an unexpected attack.

Anytime I read 'surprise buttsex' I always start hearing spy from tf2 singing that song...

But I mostly agree with Watsit.

  • 1