Closed TogarUshindi closed 3 years ago
I think the second example has a softcoded @who
action that overrides the standard WHO action. In starterdb it is #37.
I had never noticed it, but yes, it does look like the code for that program intends to only show @ for the player issuing the command.
A case might be able to be made for showing @ for all if you're a Wizard, at least.
A case for making it visible to other players is that it allows other players to point out it's missing, and they might want to look into securing their connection. Sort of a way of saying "Hey, your shoe's untied. Might want to lace it." It's good information! Let's both parties know they're secure.
Just a note, on the other MUCK, I'm obviously not a wiz and can still see it, so maybe peek at their code?
Right, since it doesn't have that version of the softcoded command. I just saw that HLM has an update to remove that logic (and thus it potentially shows for all). A future update probably will change it in the starterdb programs, but you can get ahead of it by deleting line 81 and 83 of the program.
You can also remove or rename the @who
action.
I typically use WHO
actually, not @who
:) Whowhowhowhowho
If @who
is present, it is triggered from WHO
.
I'm on your freenode if you'd like to chat more realtime.
but you can get ahead of it by deleting line 81 and 83 of the program
Which one? wd
?
yes.
@wyld-sw Something I noticed.
That one muck you showed me the other day.
They all have
@
marks to show their connection is secure.However, mine does not. It only shows a
@
for the player's own connection. The other players' connections appear as non-SSL to that player.Perhaps a sign of faulty SSL implementation? Perhaps due to it being self-signed? Or something else perhaps? A fault in the code maybe?
Also noticed the space between idle time and
@
is not present on mine like it is on the other MUCK, and the "Doing" is much farther right.