Simply enclose the name of the cards to search for in angle brackets <> as part of your
conversations to have Bastion fetch the card information for you! Example:
I sometimes make typos. My favourite monsters are <blue-eyes white dragon> and <Dork Magician>. I can't believe <GG EZ> is the name of a card!
This works in any type of channel, including forums, threads, and voice chats, as long as Bastion is in the channel. A maximum of THREE cards can be fetched per message, to avoid spamming.
Bastion must have all of its permissions to work properly.
If you do not want <> card search to be used in a channel, deny it the View Channel permission.
The card information is presented in the same Discord embeds as /search.
The embeds are localized to every official Yu-Gi-Oh! language. The default search and result language
for community servers is the server primary language in Discord settings, falling back to English if
the setting is not a Yu-Gi-Oh! language or it is not a community server. For more information, see
Other languages below.
If the message summoning Bastion is deleted within five minutes, Bastion will automatically delete its responses. This allows non-moderators to clean up after themselves.
Like /search, you can look up cards by their
password (the number printed in the bottom-left corner) or
Konami ID (the ID assigned to the card in the official card database).
If your search term is just a number, it will be treated as a password. Example:
The smallest password is <00002511>, but it used to be <10000>
If your search term starts with % and is followed by a number, it will be treated as a Konami ID. Example:
The smallest Konami ID is <%4007>
Note: # cannot be used for either option because it conflicts with internal Discord syntax for channel mentions.
Like /search, this uses the same locale setting.
The search term between the brackets are treated as the configured language, and by default,
the results will be in that language.
To change the input language, add it at the end after a comma. The result language will still be the configured language setting. Example:
J'aime <baguette du monde,fr>
To change both the input language and result language, add both at the end, separated by commas, in
the order <search term,input language,result language>. Example:
I wonder what the Japanese text is for <blue-eyes white dragon,en,ja>
For a full list of supported languages, see the above locale setting link.
Prefix or postfix the angle brackets with an R (case-insensitive) to search for Rush Duel cards
instead of OCG/TCG cards. 러 can also be used for Korean. Example:
I Maximum Summon r<Yggdrago the Sky Emperor>!
You can freely mix search categories, but the maximum of three still applies. Example:
<pot of greed>R <pot of greed> <aleister the invoker>
If your search term is just a number, it will be treated as a Konami ID because Rush Duel cards do not have passwords. Example:
R<15150>
Cross-language search works the same way. Example:
러<푸른 눈의 백룡,ko> <フュージョン,ja,ja>r
The /rush-duel command provides autocomplete on search and random selection.
These were included in the old <> search somewhat by accident.
A Slash Command for skills is planned in #446.
If you have feedback, please join the support server.
New <> card search runs on the new instance that also handles Slash Commands.
The old instance still handles some <> searches and legacy . chat commands.
<> will still trigger the old search functionality outside of threads and voice chats if the
search term contains ( or anime. This is to redirect searches for unofficial cards to
the old bot, since they are not currently included in new Bastion's data.
Certain servers do not have new <> card search at all due to frequent
searching for unofficial cards.
Old Bastion had a niche feature for server administrators to change the brackets used for card search. This was meant for conflict resolution with other bots and was very rarely used, and thus it is no longer supported. A few legacy servers have their setting baked in, to be deprecated.
- Old Bastion card search documentation
- Main GitHub issue where the new search experience was worked on
- GitHub issues for the Rush Duel search experience: #341 #468