Standard Person Commands

These are the commands PSYC person entities may want to implement:


_request_do...related variablesequivalent command
_action_whatever_focus/action
This command lets the person entity do a chat action, like _request_do_action_hug would virtually hug someone.
_add_friend_nick_person or _person, _trustee/friend
_cast_method, _amount_friendivity/cast (= /friendcast)
_clear_friend_nick_person or _person/cancel
_clear_log/logclear
_enter_group/enter
_enter_home(too psyced specific)/home
_examine_person _trustee _tag _format/examine /surf
_follow/follow
_help/help
_invite_person _focus/invite
_leave_group/leave
_list_peers/show *
_list_peers_JSON/show data
_list_places/list
_list_places_public/places
_list_users_public/people
_message_person, _group/tell and /
This sends a message to either a _person or a _group.
_presence_degree_mood _degree_availability
_degree_automation _description_presence
/availability /mood and many more
_quit/quit
_register_password/register
_remove_friend_nick_person or _person/unfriend
_retrieve
Generates a _status_storage with _application variables.
_save/save
_set_key _value/set
_show_log_amount _match _parameter/lastlog
_status/status
_store_application*
Stores all variables of the _application family in the entity storage. SHOULD also handle profile settings.
_subscribe_group/subscribe
_subscribe_permanent_group/subscribe
_time_boot/uptime
_unsubscribe_group/unsubscribe
_wake_person/wake

Presence with PSYC clients

In PSYC, clients are in charge of setting and resetting presence states on behalf of their users. That means, that a client will probably want to transmit a _request_do_presence soon after logging in and before logging out using _request_do_quit. Quitting does not automatically send offline presence. This only happens when the client loses contact to the server abnormally.