Skip to content

Describe further the reply_id and emoji fields in Data struct of MeshPacket #813

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.

Sign up for GitHub

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

Open
andrewdavidmackenzie wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Describe further the reply_id and emoji fields in Data struct of MeshPacket #813

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions meshtastic/mesh.proto
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1107,13 +1107,15 @@ message Data {
fixed32 request_id = 6;

/*
* If set, this message is intened to be a reply to a previously sent message with the defined id.
* If this field is 0, this message is a new message and not a reply.
* If this field is non-zero, this message is a reply to a previously sent message whose id is reply_id.
* Reply messages can be a text reply (emoji == 0), or an emoji reply (emoji == 1).
*/
fixed32 reply_id = 7;

/*
* Defaults to false. If true, then what is in the payload should be treated as an emoji like giving
* a message a heart or poop emoji.
* If set to 0 this message is a normal text message, like a chat message.
* If set to 1 this message is an emoji reply to an earlier message, like giving a message a heart or poop emoji.
*/
fixed32 emoji = 8;

Expand Down
Loading