All translations
Jump to navigation
Jump to search
Enter a message name below to show all available translations.
Found 22 translations.
Name | Current message text |
---|---|
h Arabic (ar) | * Sent to announce one’s Discord information from the MUD and receive an official server invite URL (if any). * User strings, if supplied, should be in the form of <username>#<identifier> as per Discord standard. * The ‘private’ field exists for the case that a game decides to provide a directory, but the user still wishes to provide their username for bot integrations or other purposes. This MUST be respected by the game. * Body: <code>{ user: "person#1234", private: true }</code> |
h ar-EG (ar-EG) | * Sent to announce one’s Discord information from the MUD and receive an official server invite URL (if any). * User strings, if supplied, should be in the form of <username>#<identifier> as per Discord standard. * The ‘private’ field exists for the case that a game decides to provide a directory, but the user still wishes to provide their username for bot integrations or other purposes. This MUST be respected by the game. * Body: <code>{ user: "person#1234", private: true }</code> |
h German (de) | * Sent to announce one’s Discord information from the MUD and receive an official server invite URL (if any). * User strings, if supplied, should be in the form of <username>#<identifier> as per Discord standard. * The ‘private’ field exists for the case that a game decides to provide a directory, but the user still wishes to provide their username for bot integrations or other purposes. This MUST be respected by the game. * Body: <code>{ user: "person#1234", private: true }</code> |
h Greek (el) | * Sent to announce one’s Discord information from the MUD and receive an official server invite URL (if any). * User strings, if supplied, should be in the form of <username>#<identifier> as per Discord standard. * The ‘private’ field exists for the case that a game decides to provide a directory, but the user still wishes to provide their username for bot integrations or other purposes. This MUST be respected by the game. * Body: <code>{ user: "person#1234", private: true }</code> |
h English (en) | * Sent to announce one’s Discord information from the MUD and receive an official server invite URL (if any). * User strings, if supplied, should be in the form of <username>#<identifier> as per Discord standard. * The ‘private’ field exists for the case that a game decides to provide a directory, but the user still wishes to provide their username for bot integrations or other purposes. This MUST be respected by the game. * Body: <code>{ user: "person#1234", private: true }</code> |
h en-GB (en-GB) | * Sent to announce one’s Discord information from the MUD and receive an official server invite URL (if any). * User strings, if supplied, should be in the form of <username>#<identifier> as per Discord standard. * The ‘private’ field exists for the case that a game decides to provide a directory, but the user still wishes to provide their username for bot integrations or other purposes. This MUST be respected by the game. * Body: <code>{ user: "person#1234", private: true }</code> |
h en-PT (en-PT) | * Sent to announce one’s Discord information from the MUD and receive an official server invite URL (if any). * User strings, if supplied, should be in the form of <username>#<identifier> as per Discord standard. * The ‘private’ field exists for the case that a game decides to provide a directory, but the user still wishes to provide their username for bot integrations or other purposes. This MUST be respected by the game. * Body: <code>{ user: "person#1234", private: true }</code> |
h es-ES (es-ES) | * Sent to announce one’s Discord information from the MUD and receive an official server invite URL (if any). * User strings, if supplied, should be in the form of <username>#<identifier> as per Discord standard. * The ‘private’ field exists for the case that a game decides to provide a directory, but the user still wishes to provide their username for bot integrations or other purposes. This MUST be respected by the game. * Body: <code>{ user: "person#1234", private: true }</code> |
h Finnish (fi) | * Sent to announce one’s Discord information from the MUD and receive an official server invite URL (if any). * User strings, if supplied, should be in the form of <username>#<identifier> as per Discord standard. * The ‘private’ field exists for the case that a game decides to provide a directory, but the user still wishes to provide their username for bot integrations or other purposes. This MUST be respected by the game. * Body: <code>{ user: "person#1234", private: true }</code> |
h French (fr) | * Sent to announce one’s Discord information from the MUD and receive an official server invite URL (if any). * User strings, if supplied, should be in the form of <username>#<identifier> as per Discord standard. * The ‘private’ field exists for the case that a game decides to provide a directory, but the user still wishes to provide their username for bot integrations or other purposes. This MUST be respected by the game. * Body: <code>{ user: "person#1234", private: true }</code> |
h Italian (it) | * Sent to announce one’s Discord information from the MUD and receive an official server invite URL (if any). * User strings, if supplied, should be in the form of <username>#<identifier> as per Discord standard. * The ‘private’ field exists for the case that a game decides to provide a directory, but the user still wishes to provide their username for bot integrations or other purposes. This MUST be respected by the game. * Body: <code>{ user: "person#1234", private: true }</code> |
h Korean (ko) | * Sent to announce one’s Discord information from the MUD and receive an official server invite URL (if any). * User strings, if supplied, should be in the form of <username>#<identifier> as per Discord standard. * The ‘private’ field exists for the case that a game decides to provide a directory, but the user still wishes to provide their username for bot integrations or other purposes. This MUST be respected by the game. * Body: <code>{ user: "person#1234", private: true }</code> |
h Dutch (nl) | * Sent to announce one’s Discord information from the MUD and receive an official server invite URL (if any). * User strings, if supplied, should be in the form of <username>#<identifier> as per Discord standard. * The ‘private’ field exists for the case that a game decides to provide a directory, but the user still wishes to provide their username for bot integrations or other purposes. This MUST be respected by the game. * Body: <code>{ user: "person#1234", private: true }</code> |
h Polish (pl) | * Sent to announce one’s Discord information from the MUD and receive an official server invite URL (if any). * User strings, if supplied, should be in the form of <username>#<identifier> as per Discord standard. * The ‘private’ field exists for the case that a game decides to provide a directory, but the user still wishes to provide their username for bot integrations or other purposes. This MUST be respected by the game. * Body: <code>{ user: "person#1234", private: true }</code> |
h pt-BR (pt-BR) | * Sent to announce one’s Discord information from the MUD and receive an official server invite URL (if any). * User strings, if supplied, should be in the form of <username>#<identifier> as per Discord standard. * The ‘private’ field exists for the case that a game decides to provide a directory, but the user still wishes to provide their username for bot integrations or other purposes. This MUST be respected by the game. * Body: <code>{ user: "person#1234", private: true }</code> |
h pt-PT (pt-PT) | * Sent to announce one’s Discord information from the MUD and receive an official server invite URL (if any). * User strings, if supplied, should be in the form of <username>#<identifier> as per Discord standard. * The ‘private’ field exists for the case that a game decides to provide a directory, but the user still wishes to provide their username for bot integrations or other purposes. This MUST be respected by the game. * Body: <code>{ user: "person#1234", private: true }</code> |
h Russian (ru) | * Sent to announce one’s Discord information from the MUD and receive an official server invite URL (if any). * User strings, if supplied, should be in the form of <username>#<identifier> as per Discord standard. * The ‘private’ field exists for the case that a game decides to provide a directory, but the user still wishes to provide their username for bot integrations or other purposes. This MUST be respected by the game. * Body: <code>{ user: "person#1234", private: true }</code> |
h sv-SE (sv-SE) | * Sent to announce one’s Discord information from the MUD and receive an official server invite URL (if any). * User strings, if supplied, should be in the form of <username>#<identifier> as per Discord standard. * The ‘private’ field exists for the case that a game decides to provide a directory, but the user still wishes to provide their username for bot integrations or other purposes. This MUST be respected by the game. * Body: <code>{ user: "person#1234", private: true }</code> |
h Turkish (tr) | * Sent to announce one’s Discord information from the MUD and receive an official server invite URL (if any). * User strings, if supplied, should be in the form of <username>#<identifier> as per Discord standard. * The ‘private’ field exists for the case that a game decides to provide a directory, but the user still wishes to provide their username for bot integrations or other purposes. This MUST be respected by the game. * Body: <code>{ user: "person#1234", private: true }</code> |
h yd (yd) | * Sent to announce one’s Discord information from the MUD and receive an official server invite URL (if any). * User strings, if supplied, should be in the form of <username>#<identifier> as per Discord standard. * The ‘private’ field exists for the case that a game decides to provide a directory, but the user still wishes to provide their username for bot integrations or other purposes. This MUST be respected by the game. * Body: <code>{ user: "person#1234", private: true }</code> |
h zh-CN (zh-CN) | * Sent to announce one’s Discord information from the MUD and receive an official server invite URL (if any). * User strings, if supplied, should be in the form of <username>#<identifier> as per Discord standard. * The ‘private’ field exists for the case that a game decides to provide a directory, but the user still wishes to provide their username for bot integrations or other purposes. This MUST be respected by the game. * Body: <code>{ user: "person#1234", private: true }</code> |
h zh-TW (zh-TW) | * Sent to announce one’s Discord information from the MUD and receive an official server invite URL (if any). * User strings, if supplied, should be in the form of <username>#<identifier> as per Discord standard. * The ‘private’ field exists for the case that a game decides to provide a directory, but the user still wishes to provide their username for bot integrations or other purposes. This MUST be respected by the game. * Body: <code>{ user: "person#1234", private: true }</code> |