-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@lock/interact [REF: Job 98] #10
Comments
Comment #1 originally posted by brazilofmux on 2006-09-08T20:51:37.000Z: On Wed Jul 21 10:50:26 2004, Brazil commented: The lock name is INTERACT? Should I be looking at Rhost for this? |
Comment #2 originally posted by brazilofmux on 2006-09-08T20:52:12.000Z: On Wed Jul 21 11:13:41 2004, Lolly added: Actually, PennMUSH uses interact, not quite sure about Rhost, I think Rhost is like |
Comment #3 originally posted by brazilofmux on 2006-11-28T04:40:55.000Z: <empty> |
Comment #4 originally posted by brazilofmux on 2006-12-27T20:51:29.000Z: <empty> |
Comment #5 originally posted by brazilofmux on 2007-12-18T03:55:37.000Z: <empty> |
Comment #6 originally posted by brazilofmux on 2009-11-29T16:00:09.000Z: <empty> |
Original issue 7 created by brazilofmux on 2006-09-08T20:51:04.000Z:
On Wed Jul 21 07:49:20 2004, Lolly suggested:
Can you, like other codebases, add an interact lock so that people can
block speech and chatter from pointless objects, people, or anything
capable of speech and chat?
[REF: Job 98]
The text was updated successfully, but these errors were encountered: