Drop Analysis
Every card in a drop, and how many people want it.
Reads every Karuta dropPremium
Loading Drop Analysis
Drop Analysis
Every card in a drop, and how many people want it.
Reads every Karuta dropPremium
Keqing reads each Karuta drop and replies with the wishlist count of every card, before anyone grabs. It can also ping roles for high-wishlist cards and members who opted in for cards on their Keqing wishlists.
I'm dropping 3 cards since this server is currently active!
↳ Replying to Karuta
♡467 Natsu Dragneel · Fairy Tail
♡38 Lucy Heartfilia · Fairy Tail
♡12 Happy · Fairy Tail
Local simulation, not a Discord connection. @itsdei wishes for Natsu and is not the dropper. Rank thresholds are ♡100/500/1,000. Print alerts and auto-star are illustrated separately below.
Cards stay in drop order, so the first line is the card under Karuta's 1️⃣. A card worth a look gets Keqing's crystal number and a bold name: one at your reply minimum, one printed under 1,000, or one that was pinged. The rest get the gold-and-white number. It reads personal drops and server drops, including a drop whose picture Karuta adds a moment later, and answers each drop once. There is no command to read a drop by hand: switch it on and Keqing answers every drop on its own.
#Turning it on
It's premium, and stays off until an admin opts in. Switch on Read Karuta drops on the Drop analysis page of the dashboard, or run adropanalysissettings on (adropwlsettings still works). Both need Manage Server.
If the server's premium ends, drop reading switches off and has to be turned on again after renewing.
#Settings
Run adropwlsettings alone to see every setting in Discord. The dashboard also has the main Drop analysis settings, but wisher pings and reply cleanup currently need the Discord command. The settings reply warns you when an option can't work yet, such as a ping role that was deleted. Changing these settings needs Manage Server.
adropwlsettings↳ Replying to itsdei
Manage Server and active premium are needed to enable drop reading. These sample commands change only this preview; member opt-in is a separate awishping on.
- Drop reading
- Command:
adropwlsettings on/off - Default: Off
- Command:
- Replies
- Command:
adropwlsettings reply all/highlight 250/silent - Default: All, at ♡100
- Command:
- Wishlist ping
- Command:
adropwlsettings ping 300/off - Default: Off, at ♡100
- Command:
- Ping player drops
- Command:
adropwlsettings pingplayer on/off, or Player drops in the dashboard - Default: Off
- Command:
- Personal wisher pings
- Command:
adropwlsettings wishers on/off - Default: Off; members must also opt in with
awishping on
- Command:
- Reply cleanup
- Command:
adropwlsettings cleanup 2m/off - Default: Off; accepts delays from 30 seconds to one hour
- Command:
- Wishlist ranks
- Command:
adropwlsettings rank 500 @Rare/rank 500 off/ranks off - Default: None
- Command:
- Print numbers
- Command:
adropwlsettings print off/emoji/on - Default: Off
- Command:
A number turns an option on with that minimum. Minimums run from 1 to 1,000,000, and 250, 1,500 or 1.5k all work. adws is a shorter name for the command.
#How much it says
- All: Every drop, every card, with how long it took
- Highlight: Only drops with a card at the minimum, listing just those cards
- Silent: No regular analysis reply. Pings can still send a reply, and auto-star still works
#Pings and stars
Automatic starboard posts have their own guide: Autostarboard.
- Wishlist ping pings the @Wishlist Ping role (or the role you picked with
awishwatch role) on the same reply when a card reaches the minimum, listing just those cards. It's sent even in Silent. Pausing Wish Watch pauses it too, and nothing is pinged until someone has joined the role withawishwatch. - Ping player drops decides which drops can ping: the wishlist ping, ranks, print pings and personal wisher pings alike. It starts off, so they notify on server drops only, since players already watch their own drops. A player's drop still shows wishlist and low-print highlights, without ping mentions. Switch it on to ping on player drops too. In the dashboard it's the Player drops switch, under the wishlist ping.
The reply is an embed, with each card's full name and series. Above it, every highlighted card gets one compact line: its number, wishlist, bold name, print emoji, then all the roles it earned together. Series and numeric prints stay in the embed. A mention inside an embed never notifies anyone, so role mentions stay on the compact lines. All highlights verified cards at ♡100 or more and visible low prints; the saved reply minimum applies only to Highlight. With Highlight, or Silent when a ping fires, the embed lists only the qualifying cards. Auto-star keeps working in quiet modes.
@itsdei is dropping 4 cards!
↳ Replying to Karuta
♡467 Natsu Dragneel @Wishlist Ping ♡467 Natsu Dragneel · Fairy Tail#Ping the people who wished
An admin runs adropwlsettings wishers on, then each interested member runs awishping on in this server. Both switches are needed, along with premium and drop reading enabled. A member can save their opt-in before the admin enables the feature.
Keqing matches each verified card against the member's Keqing character and series wishes, not Karuta's wishlist-count threshold. This can work alongside wishlist roles and ranks, including in Silent mode. Members can opt out with awishping off, check their servers with awishping status, or opt out everywhere with awishping clear. See Wishlist System.
- At most five wishers per card, and ten distinct wishers per reply, can be mentioned. A member matching several cards is mentioned only once.
- Each member can be pinged at most once per minute per server. The player who dropped the cards is not pinged for their own drop.
- Player drops only ping when Ping player drops is on. Unsure matches and cards with an unknown count never trigger wisher pings.
- If the wisher lookup is unavailable or too slow, the analysis goes out without those mentions rather than holding up the drop reply.
#Delete quiet replies automatically
Use adropwlsettings cleanup 2m to delete analysis replies two minutes after they are sent. Delays can run from 30 seconds to one hour, for example 30s, 2m or 1h. adropwlsettings cleanup off keeps replies indefinitely again.
Replies that ping are kept, including replies carrying personal wisher mentions or a server-drop ping, so the people notified can still find them. Cleanup removes Keqing's analysis reply, not Karuta's drop or a separate starboard post.
#Wishlist ranks
Give each wishlist tier its own role, up to five: ♡100+ pings @Common, ♡500+ pings @Rare, ♡1,000+ pings @Epic. Each card pings only the highest rank it reaches, so a ♡1,200 card pings @Epic alone, and members can join just the tiers they care about. Like the wishlist ping, ranks ride on the reply, keep pinging in Silent, and never count a card Keqing isn't sure of.
While any rank is set, ranks replace the wishlist ping: the dashboard hides the ping and its minimum, and they come back into force once the last rank is removed.
#Prints
Keqing also reads the print number on each card's plate. Print numbers decides what the reply shows: nothing, an emoji (sp for a print under 10, lp under 100, mp under 1,000), or the emoji plus the number.
Print alerts have their own setup guides: SP Ping for prints 1–9, LP Ping for 10–99, and MP Ping for 100–999.
#With the server drop ping
A Karuta server drop can already ping @Server Drop Ping. When both that alert and drop reading are on, Keqing sends one message instead of two: the server ping first, then the wishlist ping when a card reaches it, then the analysis.
I'm dropping 3 cards since this server is currently active!
↳ Replying to Karuta
Karuta is dropping 3 cards! @Server Drop Ping
♡467 Natsu Dragneel @Wishlist Ping ♡467 Natsu Dragneel · Fairy Tail ♡38 Lucy Heartfilia · Fairy Tail ♡12 Happy · Fairy TailThe server ping goes out even when the reply would otherwise stay quiet, such as Silent, or Highlight with no card at the minimum. If the analysis isn't ready within three seconds, Keqing sends the plain ping alone, so it's never lost.
#When Keqing isn't sure
#A count that needs refreshing
♡≈1,234 means Keqing matched the character, but its stored wishlist count has not been checked against Karuta in 14 days, or has no recorded check. Run a Karuta character lookup (klu) to refresh it. The reply includes a note explaining the marker.
This is different from ≈86%, which describes an uncertain character match. A stale count is still a verified character: its stored number continues to count toward wishlist thresholds, and staleness alone does not block pings or auto-star.
#An uncertain character match
A card Keqing can't match exactly shows the closest card it found, with how close the reading was, such as ≈86%. Below 60% it shows ♡? instead of a count.
↳ Replying to Karuta
♡467 Natsu Dragneel ♡467 Natsu Dragneel · Fairy Tail ♡0 Rizumu Suzuki · Gatchaman Crowds Insight ♡1 Dorothy West · PriPara · ≈86%
♡? Cooky · Idol Time PriParaNeither kind ever counts toward Highlight, a wishlist ping or an automatic star. Print alerts use the number read from the plate independently. Every unsure card is sent to Keqing's team, who check it so the next reading of that card is exact.