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) | * Send this whenever you need to send new status data to the client * Icon name should be an array of strings to allow for multiple options, so as not to lock multiple clients into the same iconset or icon names. Clients should use the first icon named which is available. All icon names MUST be sent in lowercase. * Details will very often be disused by the client in favour of "Playing <Game Name>" * Discord rich presence party variables should be disused if both size and max are set to 0. * The starttime and endtime fields should be unix timestamps (seconds since epoch). The starttime field will show time as time elapsed since this time. The endtime field will show a countdown. * This should send a full state rather than a delta. * Body: <code>{ smallimage: ["iconname", "iconname2", iconname3"], smallimagetext: "Icon hover text", details: "Details String", state: "State String", partysize: 0, partymax: 10, game: "Achaea", starttime: "timestamp for start" }</code> |
| h ar-EG (ar-EG) | * Send this whenever you need to send new status data to the client * Icon name should be an array of strings to allow for multiple options, so as not to lock multiple clients into the same iconset or icon names. Clients should use the first icon named which is available. All icon names MUST be sent in lowercase. * Details will very often be disused by the client in favour of "Playing <Game Name>" * Discord rich presence party variables should be disused if both size and max are set to 0. * The starttime and endtime fields should be unix timestamps (seconds since epoch). The starttime field will show time as time elapsed since this time. The endtime field will show a countdown. * This should send a full state rather than a delta. * Body: <code>{ smallimage: ["iconname", "iconname2", iconname3"], smallimagetext: "Icon hover text", details: "Details String", state: "State String", partysize: 0, partymax: 10, game: "Achaea", starttime: "timestamp for start" }</code> |
| h German (de) | * Send this whenever you need to send new status data to the client * Icon name should be an array of strings to allow for multiple options, so as not to lock multiple clients into the same iconset or icon names. Clients should use the first icon named which is available. All icon names MUST be sent in lowercase. * Details will very often be disused by the client in favour of "Playing <Game Name>" * Discord rich presence party variables should be disused if both size and max are set to 0. * The starttime and endtime fields should be unix timestamps (seconds since epoch). The starttime field will show time as time elapsed since this time. The endtime field will show a countdown. * This should send a full state rather than a delta. * Body: <code>{ smallimage: ["iconname", "iconname2", iconname3"], smallimagetext: "Icon hover text", details: "Details String", state: "State String", partysize: 0, partymax: 10, game: "Achaea", starttime: "timestamp for start" }</code> |
| h Greek (el) | * Send this whenever you need to send new status data to the client * Icon name should be an array of strings to allow for multiple options, so as not to lock multiple clients into the same iconset or icon names. Clients should use the first icon named which is available. All icon names MUST be sent in lowercase. * Details will very often be disused by the client in favour of "Playing <Game Name>" * Discord rich presence party variables should be disused if both size and max are set to 0. * The starttime and endtime fields should be unix timestamps (seconds since epoch). The starttime field will show time as time elapsed since this time. The endtime field will show a countdown. * This should send a full state rather than a delta. * Body: <code>{ smallimage: ["iconname", "iconname2", iconname3"], smallimagetext: "Icon hover text", details: "Details String", state: "State String", partysize: 0, partymax: 10, game: "Achaea", starttime: "timestamp for start" }</code> |
| h English (en) | * Send this whenever you need to send new status data to the client * Icon name should be an array of strings to allow for multiple options, so as not to lock multiple clients into the same iconset or icon names. Clients should use the first icon named which is available. All icon names MUST be sent in lowercase. * Details will very often be disused by the client in favour of "Playing <Game Name>" * Discord rich presence party variables should be disused if both size and max are set to 0. * The starttime and endtime fields should be unix timestamps (seconds since epoch). The starttime field will show time as time elapsed since this time. The endtime field will show a countdown. * This should send a full state rather than a delta. * Body: <code>{ smallimage: ["iconname", "iconname2", iconname3"], smallimagetext: "Icon hover text", details: "Details String", state: "State String", partysize: 0, partymax: 10, game: "Achaea", starttime: "timestamp for start" }</code> |
| h en-GB (en-GB) | * Send this whenever you need to send new status data to the client * Icon name should be an array of strings to allow for multiple options, so as not to lock multiple clients into the same iconset or icon names. Clients should use the first icon named which is available. All icon names MUST be sent in lowercase. * Details will very often be disused by the client in favour of "Playing <Game Name>" * Discord rich presence party variables should be disused if both size and max are set to 0. * The starttime and endtime fields should be unix timestamps (seconds since epoch). The starttime field will show time as time elapsed since this time. The endtime field will show a countdown. * This should send a full state rather than a delta. * Body: <code>{ smallimage: ["iconname", "iconname2", iconname3"], smallimagetext: "Icon hover text", details: "Details String", state: "State String", partysize: 0, partymax: 10, game: "Achaea", starttime: "timestamp for start" }</code> |
| h en-PT (en-PT) | * Send this whenever you need to send new status data to the client * Icon name should be an array of strings to allow for multiple options, so as not to lock multiple clients into the same iconset or icon names. Clients should use the first icon named which is available. All icon names MUST be sent in lowercase. * Details will very often be disused by the client in favour of "Playing <Game Name>" * Discord rich presence party variables should be disused if both size and max are set to 0. * The starttime and endtime fields should be unix timestamps (seconds since epoch). The starttime field will show time as time elapsed since this time. The endtime field will show a countdown. * This should send a full state rather than a delta. * Body: <code>{ smallimage: ["iconname", "iconname2", iconname3"], smallimagetext: "Icon hover text", details: "Details String", state: "State String", partysize: 0, partymax: 10, game: "Achaea", starttime: "timestamp for start" }</code> |
| h es-ES (es-ES) | * Send this whenever you need to send new status data to the client * Icon name should be an array of strings to allow for multiple options, so as not to lock multiple clients into the same iconset or icon names. Clients should use the first icon named which is available. All icon names MUST be sent in lowercase. * Details will very often be disused by the client in favour of "Playing <Game Name>" * Discord rich presence party variables should be disused if both size and max are set to 0. * The starttime and endtime fields should be unix timestamps (seconds since epoch). The starttime field will show time as time elapsed since this time. The endtime field will show a countdown. * This should send a full state rather than a delta. * Body: <code>{ smallimage: ["iconname", "iconname2", iconname3"], smallimagetext: "Icon hover text", details: "Details String", state: "State String", partysize: 0, partymax: 10, game: "Achaea", starttime: "timestamp for start" }</code> |
| h Finnish (fi) | * Send this whenever you need to send new status data to the client * Icon name should be an array of strings to allow for multiple options, so as not to lock multiple clients into the same iconset or icon names. Clients should use the first icon named which is available. All icon names MUST be sent in lowercase. * Details will very often be disused by the client in favour of "Playing <Game Name>" * Discord rich presence party variables should be disused if both size and max are set to 0. * The starttime and endtime fields should be unix timestamps (seconds since epoch). The starttime field will show time as time elapsed since this time. The endtime field will show a countdown. * This should send a full state rather than a delta. * Body: <code>{ smallimage: ["iconname", "iconname2", iconname3"], smallimagetext: "Icon hover text", details: "Details String", state: "State String", partysize: 0, partymax: 10, game: "Achaea", starttime: "timestamp for start" }</code> |
| h French (fr) | * Send this whenever you need to send new status data to the client * Icon name should be an array of strings to allow for multiple options, so as not to lock multiple clients into the same iconset or icon names. Clients should use the first icon named which is available. All icon names MUST be sent in lowercase. * Details will very often be disused by the client in favour of "Playing <Game Name>" * Discord rich presence party variables should be disused if both size and max are set to 0. * The starttime and endtime fields should be unix timestamps (seconds since epoch). The starttime field will show time as time elapsed since this time. The endtime field will show a countdown. * This should send a full state rather than a delta. * Body: <code>{ smallimage: ["iconname", "iconname2", iconname3"], smallimagetext: "Icon hover text", details: "Details String", state: "State String", partysize: 0, partymax: 10, game: "Achaea", starttime: "timestamp for start" }</code> |
| h Italian (it) | * Send this whenever you need to send new status data to the client * Icon name should be an array of strings to allow for multiple options, so as not to lock multiple clients into the same iconset or icon names. Clients should use the first icon named which is available. All icon names MUST be sent in lowercase. * Details will very often be disused by the client in favour of "Playing <Game Name>" * Discord rich presence party variables should be disused if both size and max are set to 0. * The starttime and endtime fields should be unix timestamps (seconds since epoch). The starttime field will show time as time elapsed since this time. The endtime field will show a countdown. * This should send a full state rather than a delta. * Body: <code>{ smallimage: ["iconname", "iconname2", iconname3"], smallimagetext: "Icon hover text", details: "Details String", state: "State String", partysize: 0, partymax: 10, game: "Achaea", starttime: "timestamp for start" }</code> |
| h Korean (ko) | * Send this whenever you need to send new status data to the client * Icon name should be an array of strings to allow for multiple options, so as not to lock multiple clients into the same iconset or icon names. Clients should use the first icon named which is available. All icon names MUST be sent in lowercase. * Details will very often be disused by the client in favour of "Playing <Game Name>" * Discord rich presence party variables should be disused if both size and max are set to 0. * The starttime and endtime fields should be unix timestamps (seconds since epoch). The starttime field will show time as time elapsed since this time. The endtime field will show a countdown. * This should send a full state rather than a delta. * Body: <code>{ smallimage: ["iconname", "iconname2", iconname3"], smallimagetext: "Icon hover text", details: "Details String", state: "State String", partysize: 0, partymax: 10, game: "Achaea", starttime: "timestamp for start" }</code> |
| h Dutch (nl) | * Send this whenever you need to send new status data to the client * Icon name should be an array of strings to allow for multiple options, so as not to lock multiple clients into the same iconset or icon names. Clients should use the first icon named which is available. All icon names MUST be sent in lowercase. * Details will very often be disused by the client in favour of "Playing <Game Name>" * Discord rich presence party variables should be disused if both size and max are set to 0. * The starttime and endtime fields should be unix timestamps (seconds since epoch). The starttime field will show time as time elapsed since this time. The endtime field will show a countdown. * This should send a full state rather than a delta. * Body: <code>{ smallimage: ["iconname", "iconname2", iconname3"], smallimagetext: "Icon hover text", details: "Details String", state: "State String", partysize: 0, partymax: 10, game: "Achaea", starttime: "timestamp for start" }</code> |
| h Polish (pl) | * Send this whenever you need to send new status data to the client * Icon name should be an array of strings to allow for multiple options, so as not to lock multiple clients into the same iconset or icon names. Clients should use the first icon named which is available. All icon names MUST be sent in lowercase. * Details will very often be disused by the client in favour of "Playing <Game Name>" * Discord rich presence party variables should be disused if both size and max are set to 0. * The starttime and endtime fields should be unix timestamps (seconds since epoch). The starttime field will show time as time elapsed since this time. The endtime field will show a countdown. * This should send a full state rather than a delta. * Body: <code>{ smallimage: ["iconname", "iconname2", iconname3"], smallimagetext: "Icon hover text", details: "Details String", state: "State String", partysize: 0, partymax: 10, game: "Achaea", starttime: "timestamp for start" }</code> |
| h pt-BR (pt-BR) | * Send this whenever you need to send new status data to the client * Icon name should be an array of strings to allow for multiple options, so as not to lock multiple clients into the same iconset or icon names. Clients should use the first icon named which is available. All icon names MUST be sent in lowercase. * Details will very often be disused by the client in favour of "Playing <Game Name>" * Discord rich presence party variables should be disused if both size and max are set to 0. * The starttime and endtime fields should be unix timestamps (seconds since epoch). The starttime field will show time as time elapsed since this time. The endtime field will show a countdown. * This should send a full state rather than a delta. * Body: <code>{ smallimage: ["iconname", "iconname2", iconname3"], smallimagetext: "Icon hover text", details: "Details String", state: "State String", partysize: 0, partymax: 10, game: "Achaea", starttime: "timestamp for start" }</code> |
| h pt-PT (pt-PT) | * Send this whenever you need to send new status data to the client * Icon name should be an array of strings to allow for multiple options, so as not to lock multiple clients into the same iconset or icon names. Clients should use the first icon named which is available. All icon names MUST be sent in lowercase. * Details will very often be disused by the client in favour of "Playing <Game Name>" * Discord rich presence party variables should be disused if both size and max are set to 0. * The starttime and endtime fields should be unix timestamps (seconds since epoch). The starttime field will show time as time elapsed since this time. The endtime field will show a countdown. * This should send a full state rather than a delta. * Body: <code>{ smallimage: ["iconname", "iconname2", iconname3"], smallimagetext: "Icon hover text", details: "Details String", state: "State String", partysize: 0, partymax: 10, game: "Achaea", starttime: "timestamp for start" }</code> |
| h Russian (ru) | * Send this whenever you need to send new status data to the client * Icon name should be an array of strings to allow for multiple options, so as not to lock multiple clients into the same iconset or icon names. Clients should use the first icon named which is available. All icon names MUST be sent in lowercase. * Details will very often be disused by the client in favour of "Playing <Game Name>" * Discord rich presence party variables should be disused if both size and max are set to 0. * The starttime and endtime fields should be unix timestamps (seconds since epoch). The starttime field will show time as time elapsed since this time. The endtime field will show a countdown. * This should send a full state rather than a delta. * Body: <code>{ smallimage: ["iconname", "iconname2", iconname3"], smallimagetext: "Icon hover text", details: "Details String", state: "State String", partysize: 0, partymax: 10, game: "Achaea", starttime: "timestamp for start" }</code> |
| h sv-SE (sv-SE) | * Send this whenever you need to send new status data to the client * Icon name should be an array of strings to allow for multiple options, so as not to lock multiple clients into the same iconset or icon names. Clients should use the first icon named which is available. All icon names MUST be sent in lowercase. * Details will very often be disused by the client in favour of "Playing <Game Name>" * Discord rich presence party variables should be disused if both size and max are set to 0. * The starttime and endtime fields should be unix timestamps (seconds since epoch). The starttime field will show time as time elapsed since this time. The endtime field will show a countdown. * This should send a full state rather than a delta. * Body: <code>{ smallimage: ["iconname", "iconname2", iconname3"], smallimagetext: "Icon hover text", details: "Details String", state: "State String", partysize: 0, partymax: 10, game: "Achaea", starttime: "timestamp for start" }</code> |
| h Turkish (tr) | * Send this whenever you need to send new status data to the client * Icon name should be an array of strings to allow for multiple options, so as not to lock multiple clients into the same iconset or icon names. Clients should use the first icon named which is available. All icon names MUST be sent in lowercase. * Details will very often be disused by the client in favour of "Playing <Game Name>" * Discord rich presence party variables should be disused if both size and max are set to 0. * The starttime and endtime fields should be unix timestamps (seconds since epoch). The starttime field will show time as time elapsed since this time. The endtime field will show a countdown. * This should send a full state rather than a delta. * Body: <code>{ smallimage: ["iconname", "iconname2", iconname3"], smallimagetext: "Icon hover text", details: "Details String", state: "State String", partysize: 0, partymax: 10, game: "Achaea", starttime: "timestamp for start" }</code> |
| h yd (yd) | * Send this whenever you need to send new status data to the client * Icon name should be an array of strings to allow for multiple options, so as not to lock multiple clients into the same iconset or icon names. Clients should use the first icon named which is available. All icon names MUST be sent in lowercase. * Details will very often be disused by the client in favour of "Playing <Game Name>" * Discord rich presence party variables should be disused if both size and max are set to 0. * The starttime and endtime fields should be unix timestamps (seconds since epoch). The starttime field will show time as time elapsed since this time. The endtime field will show a countdown. * This should send a full state rather than a delta. * Body: <code>{ smallimage: ["iconname", "iconname2", iconname3"], smallimagetext: "Icon hover text", details: "Details String", state: "State String", partysize: 0, partymax: 10, game: "Achaea", starttime: "timestamp for start" }</code> |
| h zh-CN (zh-CN) | * Send this whenever you need to send new status data to the client * Icon name should be an array of strings to allow for multiple options, so as not to lock multiple clients into the same iconset or icon names. Clients should use the first icon named which is available. All icon names MUST be sent in lowercase. * Details will very often be disused by the client in favour of "Playing <Game Name>" * Discord rich presence party variables should be disused if both size and max are set to 0. * The starttime and endtime fields should be unix timestamps (seconds since epoch). The starttime field will show time as time elapsed since this time. The endtime field will show a countdown. * This should send a full state rather than a delta. * Body: <code>{ smallimage: ["iconname", "iconname2", iconname3"], smallimagetext: "Icon hover text", details: "Details String", state: "State String", partysize: 0, partymax: 10, game: "Achaea", starttime: "timestamp for start" }</code> |
| h zh-TW (zh-TW) | * Send this whenever you need to send new status data to the client * Icon name should be an array of strings to allow for multiple options, so as not to lock multiple clients into the same iconset or icon names. Clients should use the first icon named which is available. All icon names MUST be sent in lowercase. * Details will very often be disused by the client in favour of "Playing <Game Name>" * Discord rich presence party variables should be disused if both size and max are set to 0. * The starttime and endtime fields should be unix timestamps (seconds since epoch). The starttime field will show time as time elapsed since this time. The endtime field will show a countdown. * This should send a full state rather than a delta. * Body: <code>{ smallimage: ["iconname", "iconname2", iconname3"], smallimagetext: "Icon hover text", details: "Details String", state: "State String", partysize: 0, partymax: 10, game: "Achaea", starttime: "timestamp for start" }</code> |