Walraven // Forums // Thread 679
recognize wiz command to add something to your recognition list w/o forcing somebody to introduce - would also work for cities a, allaryin, 2003-05-19 13:39:23
recognize wiz command to add something to your recognition list w/o forcing somebody to introduce - would also work for cities and such when those are implemented
command?, malap, 2003-05-19 15:31:46
I've been using @me add_recognize("whomever")
bah, allaryin, 2003-06-25 22:11:57
point is to have a command to do it w/o having to make the manual call, you know that :P
How about a player command?, acius, 2003-07-03 12:31:46
It'd be kind of nice to make it possible for players to 'recognize old man as gerry' or something like that. We could either allow that to fail ("no, that is not his true name") or we could tweak things so that you can use a nickname for them -- nicknames could be useful, especially if true names are necessary for some spells later on.
This would allow for more RP-ish introductions than the introduce command does.
This would allow for more RP-ish introductions than the introduce command does.
Me likey, allaryin, 2003-08-08 09:11:39
sounds good.
Nicknames, then?, acius, 2003-08-08 11:29:00
If we allow nicknames:
* We need to modify find_player() and find_living() to check for nicknames. This isn't too bad, since they're simul_efun's.
* We need to change the data structure for storing recognition.
We could save quite a lot of memory by tweaking recognition to use a bitfield, except this would require several hours of coding, and we have *buckets* of memory. So we probably won't.
It seems as though we're going to need both a real name->nickname mapping and a nickname->real name mapping, since we're going to need to do lookups both ways, and both need to be fast.
* We need to modify find_player() and find_living() to check for nicknames. This isn't too bad, since they're simul_efun's.
* We need to change the data structure for storing recognition.
We could save quite a lot of memory by tweaking recognition to use a bitfield, except this would require several hours of coding, and we have *buckets* of memory. So we probably won't.
It seems as though we're going to need both a real name->nickname mapping and a nickname->real name mapping, since we're going to need to do lookups both ways, and both need to be fast.
hrm, malap, 2004-07-09 11:37:14
It'd also have to happen in all_present() -- stuff like follow/unfollow all would need this.
Important question: are you allowed to have multiple nicknames for each real name?
Important question: are you allowed to have multiple nicknames for each real name?
or, sora, 2004-07-09 14:13:02
Multiple realnames for each nickname?
Conflict?, athenon, 2004-09-06 14:49:54
Scenario:
Bob logs in.
I recognize Bob as Steve.
Steve logs in.
What happens if Bob, Steve, and I are in the same room?
Bob logs in.
I recognize Bob as Steve.
Steve logs in.
What happens if Bob, Steve, and I are in the same room?
nicks/recognize, zaecus, 2004-09-06 17:11:36
I think I've seen both nicks and recognize used elsewhere. You could only recognize someone if you knew their actual name, and you had to know someone to set a nick for them, I think.
Anytime you used the nick, it automatically replaced the nick with the other person's name.
I recall this causing problems in two ways: You couldn't easily interact with someone whose name was the same as a nick you'd already assigned, and you couldn't nick someone who hadn't given you their name in some way, meaning the tall, dark-robed, fierce-eyed man could not be nicked to "DarthLoser". The next person you saw with that description would be assumed to be DarthLoser, even if they simply looked alike.
Yes, mistaken identity is a part of life, but that could get painful fast. If the nicks worked with spells and such but not with descriptions, that'd still be good. That way, you'd see that description, type "kill darthloser" and the following exchange might occur:
You See: That person doesn't seem to be here. Perhaps the person you were attacking just looks a lot like him.
They See: A large, bald, tattooed man lunges at you with a greataxe. At the last moment, he breaks off his attack and stares at your face in confusion. It looks like he thought you were someone else.
The nick vs real name problem, though, I have no idea on.
Anytime you used the nick, it automatically replaced the nick with the other person's name.
I recall this causing problems in two ways: You couldn't easily interact with someone whose name was the same as a nick you'd already assigned, and you couldn't nick someone who hadn't given you their name in some way, meaning the tall, dark-robed, fierce-eyed man could not be nicked to "DarthLoser". The next person you saw with that description would be assumed to be DarthLoser, even if they simply looked alike.
Yes, mistaken identity is a part of life, but that could get painful fast. If the nicks worked with spells and such but not with descriptions, that'd still be good. That way, you'd see that description, type "kill darthloser" and the following exchange might occur:
You See: That person doesn't seem to be here. Perhaps the person you were attacking just looks a lot like him.
They See: A large, bald, tattooed man lunges at you with a greataxe. At the last moment, he breaks off his attack and stares at your face in confusion. It looks like he thought you were someone else.
The nick vs real name problem, though, I have no idea on.
that defeats the point, sora, 2004-09-07 13:19:20
What if steve refuses to give me his name? I'll need some way to bite my thumb at him, or have someone 'follow' near him. That's whatI want a nickname command for.
Hrm., zaecus, 2004-09-07 18:58:38
Yes, I seem to have left some out.
As I recall, the reason elsewhere for not nicknaming someone you don't know was that they might not want you to be able to easily identify them--every dark haired man looks alike until the one you nicknamed Steve walks into the room: Steve enters the room. (whatever his actual name is.
So, in my ramble, I was suggesting being able to give a nick to anyone, but it doesn't change their description (dark haired man). If you type "l dark haired man," though, you'd see his character description followed by the line "You recognize him as Steve."
With or without looking, you could type kill Steve. If it wasn't Steve, then the preceding post would be my suggestion for how mistaken identity might be handled.
Complex as heck, and probably a decent reason for anyone who's actually doing the coding to run screaming from this thread as fast as possible.
As I recall, the reason elsewhere for not nicknaming someone you don't know was that they might not want you to be able to easily identify them--every dark haired man looks alike until the one you nicknamed Steve walks into the room: Steve enters the room. (whatever his actual name is.
So, in my ramble, I was suggesting being able to give a nick to anyone, but it doesn't change their description (dark haired man). If you type "l dark haired man," though, you'd see his character description followed by the line "You recognize him as Steve."
With or without looking, you could type kill Steve. If it wasn't Steve, then the preceding post would be my suggestion for how mistaken identity might be handled.
Complex as heck, and probably a decent reason for anyone who's actually doing the coding to run screaming from this thread as fast as possible.