Skip to main content

Search GiselleBot's commands and docs.

Try /ban, or start with / for commands only.

Press Ctrl K anywhere in the dashboard to open this.

Azur Lane Integration

This module has a few commands that report on Azur Lane, a side-scrolling shoot 'em up mobile game from the Chinese developers Shanghai Manjuu and Xiamen Yongshi, released in 2017 for iOS and Android.

The game was released in 4 regions:

  • CN (Chinese)
  • JP (Japanese)
  • KR (Korean)
  • EN (English/Global)

Commands

/azurlane status

Command Syntax

/azurlane status [region:{en/jp/cn/kr}]

Command Description

Checks the status of Azur Lane's game servers. Omitting region defaults to en, the English servers.

The Chinese region prints 2 embeds, one for the Android servers and one for the iOS servers. The other regions share servers between the 2 platforms.

Permissions Needed

Examples

/azurlane status
/azurlane status region:cn

Server Status Live Feed

The Azur Lane Server Status Feed watches server availability for any region and posts to one or more of the webhooks configured in your Discord server when something changes.

See also

The feed posts through Discord webhooks, so you need to know how they work. See this official guide for an introduction.

By default the feed mascot is the Azur Lane ship San Diego, and the feed messages are Azur Lane-themed.

The full list of feed messages and monitored transitions is in this Google Spreadsheet.

Each message ends with a list of hashtags that users can filter on. They give:

  • The region code the message refers to: #cn #en #jp #kr
  • The region's current status as a technical status tag: #gateway_error #full_offline #partial_offline #operational
  • One or more server name tags for the affected servers: e.g. #avrora #lexington ...
  • The quote ID (see the Azur Lane Server Status Feed Sentences Google Spreadsheet) for the region status transition and/or server status transition: e.g. #r_01 #r_02 s_02 ...

Azur Lane Status Feed Example

Feed management (dashboard)

Note

You start, edit, list and remove status feed webhooks from your server's Azur Lane page on the dashboard. The settings below still apply; only where you configure them has changed.

Warning

Discord webhooks currently do not authenticate the messages sent to them. Anyone who knows a webhook URL can, with some effort, use external tools to forge a message with any content and post it to that webhook.

Feed fields

  • Webhook URL: the Discord webhook the feed posts status transitions to. Set once when creating the feed - pasting a new URL later requires deleting and re-creating the feed.
  • Regions: a checkbox filter for Azur Lane server regions (cn, en, jp, kr). Leave all unchecked to match every region.
  • Filter Words: a whitelist of words or phrases that a status transition's quote text or hashtags must contain (or, with the "Exclude Matches" checkbox, must not contain) before it is posted; Filter Mode below combines them. Enter one word or phrase per line - there is no comma-separated list and no quoting syntax, so a multi-word phrase like full offline is just its own line. Matching is case-insensitive and works on partial words. Leave empty for no filter.
  • Filter Mode: OR (any filter word matches) or AND (every filter word must match).
  • Exclude Matches Instead of Including Them: turns the Filter Words whitelist into a blacklist.
  • Custom Header: replaces the default message template posted above each status transition (max 1024 characters). Supports the dynamic tags below.
  • Webhook Display Name: overrides the webhook's posted username (max 32 characters). Leave blank to keep the webhook's own name.
  • Do Not Overwrite the Webhook's Username / Avatar: two independent checkboxes that keep the webhook's own posted username and/or avatar instead of the module's automated ones.

Permissions needed on the dashboard: Manage Webhooks (server-side)

Note

Custom headers can be formatted as embeds with a specific syntax. Both GiselleBot and Discord are strict about it, and special characters break it easily, so embeds as a header are not recommended and not supported. Use them at your own risk. If you want to try, this embed generator can help (click "Enable webhook mode" at the bottom of the page).

Custom headers support these dynamic tags, replaced at run time:

  • %region%: the region name, capitalized (e.g. Chinese, English, ...)
  • %region_code%: the region code, uppercase (e.g. CN, EN, ...)
  • %timestamp% or %timestamp_utc%: the status transition time in UTC, with format YYYY-MM-DD HH:mm:ss (UTC).
  • %timestamp_iso%: the status transition time in UTC, as an ISO8601 string.
  • %timestamp_pst%: the status transition time in PST, with format YYYY-MM-DD HH:mm:ss (PST).

Timestamp tags accept a custom time zone. Replace the utc part with either:

  • A different valid IANA time zone identifier (e.g. America/New_York, Europe/London).

  • An UTC offset in the form [UTC/GMT](+/-)(hours)[:][minutes], for example:

    • %timestamp_Europe/London%
    • %timestamp_America/Los_Angeles%
    • %timestamp_Japan%
    • %timestamp_PST8PDT%
    • %timestamp_+0800%
    • %timestamp_-10:30%
    • %timestamp_UTC+2%

The quote text, including its hashtags, is appended after every header.

Default header: Shikikan shikikan, San Diego here with an important message for you from the %region% territory!

Default webhook display name: "Azur Lane Status Feed :: Offered by GiselleBot"

See also

Full migration mapping for these commands: Migration Guide.