From 83eb80ce05d2f267751ae55f0f8f4dfb70fc580c Mon Sep 17 00:00:00 2001 From: hippoz Date: Tue, 16 Mar 2021 01:44:44 +0200 Subject: [PATCH] Update 'resources/Docs/DOCS.md' --- resources/Docs/DOCS.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/resources/Docs/DOCS.md b/resources/Docs/DOCS.md index 723c77c..11664be 100644 --- a/resources/Docs/DOCS.md +++ b/resources/Docs/DOCS.md @@ -81,7 +81,7 @@ JSON data format: Example: ```json -3@{"content":"i hate you","channel_id":"totally real channel id"} +3@{"content":"i hate you","channel":{"_id":"totally real channel id"}} ``` ## 4:EVENT\_NEW\_MESSAGE @@ -112,7 +112,7 @@ Example: *Auth required, Server to client* -Sent by the server after YOO\_ACK, and otherwise when the entire status needs to be updated. If only one user's status changes, use EVENT\_CHANNEL\_MEMBER\_UPDATE. +Sent by the server after YOO\_ACK, and otherwise when the entire status needs to be updated. Usually, this will be sent only once, and when subsequent user status updates need to happen, EVENT\_CHANNEL\_MEMBER\_UPDATE should be sent. JSON data format (this ones tough): Contains a JSON object, where each key is a channel id and each property is an array of [user presence objects](#user-presence-object).