Random Tiny CODE Wants

[X-D]

I was going to say, that is easy to fix, either have it simply not work if face hid, Or, and this would be more fun IMO, have it work, But if the PC lowers hood, uncovers face, for any reason, the keyword goes away for the other person.


Being able to keyword all your raiding partners with hoods up is useful, but no reason they should stick...besides, then you could re-use them.

I know if I was a byn sarge, I'd be wanting to use Larry, Curly and Moe...alot.

[Reiloth]

I was going to say, that is easy to fix, either have it simply not work if face hid, Or, and this would be more fun IMO, have it work, But if the PC lowers hood, uncovers face, for any reason, the keyword goes away for the other person.


Being able to keyword all your raiding partners with hoods up is useful, but no reason they should stick...besides, then you could re-use them.

I know if I was a byn sarge, I'd be wanting to use Larry, Curly and Moe...alot.

Actually, that's a really good point. If your Rogue is smart enough to change clothes, people won't be able to recognize him for his crimes by tagging them with a temp keyword.

[musashi]

Sounds good to me. I hope that idea makes it into 2.arm as well.

[jhunter]

The ability to assign keywords to pcs/npcs just like you can for mounts ONLY that they do not work for other people.

Example:

Blue-man says his name is frank.  Frank is not a keyword.  You addkeyword blue frank.
Now blue-man has the keyword frank to you only.  Frank would still not work for anyone else.

We are calling these private keywords in Arm 2. It is the way most keywording will work, except for visible sdesc keywords.

I'm a little worried about abuse issues with private keywords.

Take for example a situation in which a person who got robbed discretely keywords their completely cloaked/hidden/I'll kill you if you look at me robber. Then whenever they see a new PC walk into the bar back at the city they "l robber" and see if it pings.

It would be a simple case of code abuse and it would be easy enough for the staff to look at the logs and bust them on it if such happened.

[musashi]

It would be a simple case of code abuse and it would be easy enough for the staff to look at the logs and bust them on it if such happened.

This alone doesn't do it for me. I know staff would surely do that, but they couldn't save your character.

The person would be punished, but the damage would already be done.

[SMuz]

Code Select Expand

> list prostitute
the tall, muscular prostitute has the following goods to trade:
01) a kiss for 10 obsidian coins
02) heavy petting for 24 obsidian coins
03) a striptease for 45 obsidian coins
04) kanking for 80 obsidian coins
05) backdoor kanking for 140 obsidian coins


[Barsook]

Code Select Expand

> list prostitute
the tall, muscular prostitute has the following goods to trade:
01) a kiss for 10 obsidian coins
02) heavy petting for 24 obsidian coins
03) a striptease for 45 obsidian coins
04) kanking for 80 obsidian coins
05) backdoor kanking for 140 obsidian coins


I dig that!

[Dar]

How about the next time there is a PC whore, you actually value her, instead of either ignoring them, or making it a challenge to get into their pants for free.

[Nyr]

How about the next time there is a PC whore, you actually value her, instead of either ignoring them, or making it a challenge to get into their pants for free.

Code Select Expand

>value whore
You'd probably have to pay a couple small to get him under some furs.


?

I am ok with this code want

[jhunter]

It would be a simple case of code abuse and it would be easy enough for the staff to look at the logs and bust them on it if such happened.

This alone doesn't do it for me. I know staff would surely do that, but they couldn't save your character.

The person would be punished, but the damage would already be done.

I suppose but I prefer to leave it possible for the twinks to show themselves and get weeded out. For every one that abuses something like that there are many who don't and that goes a long way in making me feel better about trusting the majority of players.

[Feco]

Sunslits to reduce vision indoors/in the dark.

Maybe you can't see out of the room you're in?

[DesertT]

whisper self

For those times that you want to mutter under your breath, but you want to afford someone the opportunity to hear you if they are listening.

[a strange shadow]

Sunslits to reduce vision indoors/in the dark.

Maybe you can't see out of the room you're in?

My suggestion: Limits visibility by one room, but allows you to see in the room you're in, even during blinding sandstorms.

So if you'd normally see 3 rooms, you only see 2, etc. The trade off is that you'd have an easier time navigating during actual sandstorms.

[Feco]

I don't think visibilty in the bright sun should be limited.  Just indoors/dark.  Just MHO.

[Qzzrbl]

I don't think visibilty in the bright sun should be limited.  Just indoors/dark.  Just MHO.

Well they do kinda wreak havoc on peripheral vision.

[Dar]

significantly nix scan if you're wearing sunslits maybe?

[RogueGunslinger]

Seems like a pointless addition.

[SMuz]

whisper self

For those times that you want to mutter under your breath, but you want to afford someone the opportunity to hear you if they are listening.

I proposed something like this a few years back, looks like it's not likely to happen (in Armageddon 1)

[Kol]

whisper self

For those times that you want to mutter under your breath, but you want to afford someone the opportunity to hear you if they are listening.

I proposed something like this a few years back, looks like it's not likely to happen (in Armageddon 1)

I'd quite like a mutter command...

Code Select Expand


Mutter Bloody knife ears
The annoying brit mutters softly

Or if your listen skill is high enough:

Code Select Expand


Listen
You overhear the annoying brit mutter softly "Bloody knife ears"

[Marshmellow]

Since the 'whisper self' vs 'mutter' debate broke out back when it did, I've been a proponent of 'whisper self'.  Why add another command instead of just increase the functionality on a command we already have?  This goes doubly when the command you're looking for basically duplicates that other command... but is just to self.

[Booya]

I would like to see Drum beat echo for multiple rooms and grow fainter as they reach out..

I submitted an object like this once - a war horn.  Thought it might be practical in coordinating battles.

I'd like to be able  to whistle, and it to be heard in adjoining rooms.

whistle two short sharp blasts

From the east, you hear someone whistle two short sharp blasts

More flexible, a 'signal' command:

signal (pounding the beater on  ~drum) two resonant drumbeats

shows to the room: Pounding the beater on her large hide drum, so and so does two resonant drum beats.
shows to every adjacent room: From the south/east/west/north you hear two resonant drum beats.

signal (bringing both thumbs to her lips, hands cupped) an owl-like hoot

shows to the room: Bringing both thumbs to her lips, hands cupped, so and so does an owl-like hoot
shows to adjacent rooms: From the north etc you hear an owl-like hoot

Maybe only people who were actively listening could hear it in adjacent rooms, and if you had mastered 'listen' you could hear it from even further away.

I love the thought of being able to do secret gang whistle codes in the 'rinth. Or co-ordinate hunts and/or raids with only sounds. 

[Barsook]

Signaling would work.

[Majikal]

For you to still be able to interact with a merchant npc when it happens to wander into the same room as a tattooist.

[Feco]

For you to still be able to interact with a merchant npc when it happens to wander into the same room as a tattooist.

[manipura]

For you to still be able to interact with a merchant npc when it happens to wander into the same room as a tattooist.

Yes please.