The standard shop panel can use a title, description, embed color, author text, footer text, banner, thumbnail, author icon, and footer icon. Members browse it with the shop dropdown and page buttons.

Free servers can create up to 25 shop items, and each custom item can have up to 3 consume actions. Premium servers can create up to 500 shop items, and each custom item can have up to 5 consume actions.

Chat capping is part of Server Currency, not Leveling. It limits how many coins a member can earn from normal chat each day. Members can still talk after reaching cap, but they stop earning chat coins until the next day.

When a message qualifies, Naya rolls a reward percent between your minimum and maximum percent, then applies it to the daily chat cap. For example, with a 500 daily cap and a 5 percent to 15 percent reward range, each qualifying message can award about 25 to 75 coins, but never past the member's remaining daily cap.

The cap announcement template is sent when a member reaches the daily currency chat cap. It can be used for a simple public celebration or quiet activity log.

Example: {uid} just capped for today! Streak: {streak} days.

Leveling can be disabled while currency capping be enabled, or vice versa, or both can be enabled. Currency capping has daily coin limits, cap streaks, and cap bonuses. A cap streak ends if a member misses the daily currency chat cap for a day.

Chests can appear in selected channels and give members something occasional to claim. You can tune spawn channels, spawn chance, cooldown, guild-wide or per-channel cooldown mode, expiration time, whether expired chests are deleted, and the coin reward range.

Currency can also come from Guildboard check-ins, quizzes, trivia, and lotteries; Garden water and bloom rewards; Pet play, feed, and adventure rewards; quests; giveaways or events through staff rewards; autoresponder custom actions; and item actions that grant currency.

Items can require a minimum level, a minimum number of daily chat caps, minimum co-op reputation, minimum garden blooms, or one of up to 5 required roles. This is useful for prestige items, subscriber items, seasonal access, or shop categories that should feel earned.

Each server has its own inventory. Buying or earning an item in one server does not give it anywhere else. Custom items can be saved as collectibles or consumed later to run their attached actions.

Currency, XP, inventory, and pet actions can use weighted choices. Only one choice is awarded when that action runs. Higher weight means more common. Lower weight means rarer. This is useful for boxes, crates, event rolls, or rare subscription prizes.

Premium servers can connect item custom actions to dropdowns or buttons on the dashboard Embed Builder. This can be used for additional features - such as using modal for suggestions, anonymous confessions, occasional custom check in rewards with gacha chances for special items, and anything else.

Create a custom item such as announcement_ticket. Add modal.send with the announcement they want to post. Send the response to a staff review channel, or use a channel response with allowed mentions if your staff wants the purchase to post directly in the announcement or news channel. It can contain something such as: A new announcement from {user}.

Create the pet in Pets first, then keep it out of normal hatch results by using a 0 hatch weight. Then create a custom item with pet.give using that pet's pet key. This is ideal for seasonal pets, supporter pets, or rare collectible pets. It is also great for gacha items that can reward various pet types rewards. Remember to warn members that it will replace their current pet!

Create role items for seasonal roles, sell them during the season, then disable them in the shop when the season ends. Members keep the role if it is meant to be permanent, or you can use temporary role duration for timed access - such as temporary access to vip channels.

Create one role item for each color or icon role. Use role.remove first to remove other premium color roles, then role.give to give the selected one. This avoids conflicting color roles. Naya needs Manage Roles, and her bot role must be above every role she gives or removes.

Create a custom box item. Add a gacha inventory.give, currency.give, or role.give style reward path. Give common rewards high weight and subscription-style prizes low weight. Weight is like percent chance but it doesn't have to equal 100. If the rare prize needs details, include a modal.send action asking for UID, region, order notes, or top-up details so the member can skip opening a ticket; and send to a private staff channel.

Create a custom item with channel.create, use a name template like {user}-lounge, choose a category, and enable private channel for the buyer. This works well for temporary lounges, commission rooms, study rooms, or premium support spaces.

Use multiple actions on one item: send a private reply, grant currency, grant a collectible item, and send a staff log. Premium servers can use up to 5 actions, so bundles can feel polished without staff handling every purchase manually.

Make sure Naya has Manage Roles and that her highest role is above the role being given or removed. Discord does not allow bots to manage roles equal to or above their own top role.

Discord may block DMs based on the member's privacy settings or shared server state. For important purchases, also use a channel message, ephemeral reply, or staff log.

Check whether currency chat rewards are enabled, the channel is allowed, the message is long enough, the member is still on cooldown, the award chance failed, or the member already reached their daily chat cap.

Check allowed chest channels, spawn chance, spawn cooldown, cooldown mode, and whether the bot can view and send messages in the channel.

• Use a simple currency name and emoji.
• Enable chat capping with modest rewards and a healthy daily cap.
• Add a small shop with 3 to 6 items people actually want.
• Use requirements for prestige items, not every item.
• Add custom actions only after the basic shop already feels clear.

If prices feel meaningless, reduce earning speed or raise prices slowly. If earning feels too slow, improve the daily cap, cap bonus, chest rewards, or event rewards before making every shop item cheaper.

Every item should tell members what it does, whether it is consumable, whether it has a cooldown, and whether staff review is involved. Clear shop text prevents most support questions.

Voice XP can award XP per minute when enabled. You can set XP per minute and the minimum number of members required in the voice channel. Use a minimum above 1 if you want to avoid empty-call farming.

Blocked channels never award XP. Use this for bot commands, spam, staff channels, logs, counting channels, or anywhere progression would be easy to farm.

The dashboard curve is XP(L) = A * L^2 + B * L + C. This is the XP cost for each level step. L is the target level, A is the quadratic part, B is the linear part, and C is the flat part.

Naya stores total XP. To know the total XP needed to reach level L, Naya sums the curve from level 1 through level L:

Total XP to reach L = A * L(L + 1)(2L + 1) / 6 + B * L(L + 1) / 2 + C * L

With the default curve A = 50, B = 50, and C = 0, level 1 needs 100 total XP, level 2 needs 400 total XP, level 5 needs 3500 total XP, and level 10 needs 22000 total XP.

Diminishing returns are counted per member per hour. The first group of XP awards gets the full award percent. The next group gets the partial award percent. After the partial-award limit is reached, additional messages in that hour stop awarding XP.

Diminishing helps prevent spam while still making normal activity feel rewarding. It encourages members to return naturally instead of dumping many messages at once.

Role rewards give roles automatically when members reach selected levels. If role stacking is on, members keep all earned reward roles. If it is off, they keep only the highest relevant reward role.

Booster roles grant extra XP to members with matching roles. If stacking is on, matching booster percentages add together up to the booster cap. If stacking is off, only the highest matching booster applies.

Channel boosts add bonus XP for messages in selected channels. Use them for thoughtful areas like art, study, guides, event discussion, or slower high-effort channels. Keep bot and spam channels blocked instead.

Naya needs Manage Roles, and her top role must be above any reward role she gives or removes. If role rewards silently fail, role order is the first thing to check.

The dashboard controls the default rank card for members who have not customized their own card. You can set frame style, shadow opacity, chat bar color, XP bar color, and on premium servers, a default wallpaper.

Premium servers can upload a default rank card wallpaper. The dashboard recommends an 800 by 200 image. JPG, PNG, and WebP are supported by the upload field.

Rank cards can show level, total XP, XP progress, daily chat progress from currency capping, and a server rank position. This is why currency cap progress can appear visually on the card, even though the cap itself belongs to Server Currency.

Check that leveling is enabled, the channel is not blocked, thread XP is allowed if the message is in a thread, the message meets minimum characters, the member is not on cooldown, and the award chance did not fail.

Make sure voice XP is enabled, the voice channel has at least the configured minimum members, and members are actually connected long enough for the voice ticker to award XP.

Check the announcement channel, make sure Naya can view it, send messages, attach files if the rank card is included, and embed links if your announcement uses embeds.

Check Manage Roles permission and role order. Naya cannot give or remove roles that are equal to or above her highest role.

• Use a dedicated levels channel for announcements, rank cards, and leaderboards.
• Keep the default XP range until you know the pace you want.
• Use milestone role rewards, such as levels 5, 10, 25, 50, and 100.
• Use blocked channels for bot commands and low-effort spam channels.
• Enable diminishing returns if you want healthier pacing.

If leveling is too fast, raise the curve, lower award chance, lower XP awards, or make diminishing stricter. If leveling is too slow, do the opposite slowly. Small changes are easier for members to understand.

Leveling works best when members can see progress. Announcements, role rewards, rank cards, and leaderboards all help the system feel alive without needing staff to explain it repeatedly.

Server owners, administrators, and members with Manage Server can create events. You can also choose creator roles in the dashboard so event staff, moderators, or community leads can use the New Event button without giving them broad admin permissions.

Members use the posted board to open All Events. Active and upcoming events stay easy to find. Canceled and ended events are kept out of the normal active list so members do not have to sort through old cards.

Use a dedicated events, announcements, or community hub channel. Naya needs permission to view the channel, send messages, embed links, create or manage related threads where applicable, and use external emojis if your board uses them.

Check the board for upcoming server events. Use All Events to browse active events. Event hosts can create new cards from this panel.

Keep this short. The event cards carry the details; the board should teach members where to click.

Custom Solo and Custom Teams can include questions, accepted answers, and point values. Members submit answers through a Discord modal while the event is ongoing. Because Discord modals only allow up to 5 text inputs at a time, keep custom event prompts focused.

An optional relay channel can copy submissions to staff so hosts can review what members entered.

Use Standard events for watch parties, game nights, scheduled server activities, classes, hangouts, community meetings, or any event where members mainly need a time, place, host, and details. Before the event starts, members can RSVP as participating or maybe.

Use Custom Solo events when each member submits their own answers and earns points independently. Good fits include prediction contests, trivia rounds, puzzle hunts, scavenger clues, screenshot challenges, or "guess the score" events.

Use Custom Teams events when members should create teams, join teams, and submit answers for their team. Good fits include team puzzle nights, house competitions, group predictions, tournament side games, or collaborative challenges.

Correct custom answers award points once. If a user or team submits the same already-solved answer again, Naya records the submission but does not award duplicate points. Event cards can show top participants or top teams so members can follow progress.

RSVP clicks are buffered briefly so busy events can handle fast button activity. Counts may appear a moment behind during a rush, then settle as Naya flushes the latest choices.

Hosts can update event details, refresh the event card, change status, and keep the related event thread aligned. This is useful because real event details often change after the first announcement.

End or cancel events when they are no longer active. A board that only shows current events will feel much more trustworthy to members.

Use a Standard event. Put the streaming platform or voice channel in Location, add the time, and use Reward only if there is a participation prize. Members can RSVP before it starts, and the host can update the card if the movie or time changes.

Use Custom Solo. Add prompts such as "Who will win?" or "What score will it end with?", accepted answers, and point values. Use the relay channel if staff wants to review entries as they come in.

Use Custom Solo for individual puzzles or Custom Teams for group puzzles. Keep the first event to 3 to 5 prompts so submissions fit cleanly in the modal. Give each question a point value based on difficulty.

Use Custom Teams. Set a minimum and maximum team size, then let members create and join teams from the event card. This works well for house points, server factions, study groups, game squads, or seasonal teams.

Use the same board and make each recurring session a new event card. Reusing the board keeps members trained on where to check, while separate cards keep each event clean.

Check the creator role list in the dashboard. The member must have a selected creator role, Manage Server, Administrator, or be the server owner.

Make sure Naya can view the channel, send messages, embed links, and access the event card. If the card was manually deleted, repost or recreate the event from the board.

Submissions only open while Custom Solo or Custom Teams events are ongoing. Standard events do not have answer submissions.

For Custom Teams, the member must be in a team before submitting. Check team size limits and make sure the event is ongoing.

• Use one visible Events Board channel.
• Give event creation to a small trusted host role.
• Start with Standard events until members understand the board.
• Use Custom Solo for simple scored contests.
• Use Custom Teams only when the team flow is important.

Use short titles, clear times, one location, and a short reward note. Put long rules in the event thread or description only when they are truly needed.

If an event does not need answers or points, use Standard. If it does not need teams, use Custom Solo. The simpler format is usually easier for members to join.

Free servers can create up to 4 pet types. Premium servers can create up to 500 pet types. Start with a small lineup first, then add seasonal or rare pets once the system feels balanced.

Members use /pet. If they do not have an active pet, Naya creates a Mysterious Egg for them. Once the egg receives enough unique interactions, it hatches and the owner names the new pet.

Eggs can require up to 100 unique member interactions before hatching. This makes hatching feel social. If you want pets to be immediate, set the required interactions to 0.

When an egg hatches, Naya first chooses a rarity using the rarity chances you configured. Then she chooses a pet inside that rarity using each pet type's weight. Higher weight means the pet appears more often. Lower weight makes the pet rarer.

Pets can also be granted through server shop items, chests, or staff reward flows that use a give-pet style action. This is useful for event pets, shop-only pets, and special collectibles.

Pet rewards can scale as the pet levels. The dashboard lets you set the max level, extra coins per level, extra pet XP per level, player XP per action, and how much more player XP adventure gives compared with play and feed.

Each pet type has starve days. If a normal pet is not fed for too long, it can become deceased. Immortal pets ignore starve days and cannot be lost this way, which is best for rare, premium, or event pets.

Pet images should be stable direct image links. For Discord-hosted images, upload the image in Discord, copy the image link, and keep the original Discord message available so the link does not disappear later.

After hatching, the owner names their pet. Naya checks names against blocked words and domains before accepting them. Staff should still keep an eye on names, especially in larger servers.

Members can release a pet when they want to start over by using -releasepet command. Releasing wipes the current pet and can apply the release cooldown. Keep the cooldown enabled if you want to prevent frequent rerolling.

• Use 3 or 4 pet types at first.
• Keep Common around the easiest pets, then make Rare and Ultra Rare feel special.
• Use small play and feed rewards, with adventure as the larger slower reward.
• Make event or premium pets immortal if losing them would feel bad.
• Use 5 to 10 egg interactions for a social hatch, or 0 if you want instant pets.

If rewards feel too high, check adventure coins, adventure cooldown, level scaling, and double coin chance first. If members cannot hatch pets, make sure the pet lineup has at least one valid pet type and that the rarity chances are not all set to 0.

The board can use a title, description, embed color, header text, footer text, banner, thumbnail, header icon, and footer icon. Keep the board copy short, because the real activity happens on the plant messages.

Save stores the dashboard draft. Save and Post publishes the garden board in the selected channel. A dedicated garden channel works best, and many servers turn off regular member messages in that channel so active plants stay easy to find.

Free servers can create up to 4 plant types. Premium servers can create up to 500 plant types.

Water rewards are small rewards given when a member waters a plant. You can set coin min and max, XP min and max, double coin chance, and the open and closed colors used for plant embeds.

The fallback emoji is used when a plant needs a general bloom visual. The seed emoji is used for new seeds. Custom Discord emoji can make the garden feel much more like your server.

When someone plants a seed, Naya chooses one of your plant types at random. Higher weight makes a plant more common. Lower weight makes a plant rarer. For example, a plant with weight 10 appears more often than a plant with weight 2.

Water rewards go to the member who waters. Bloom rewards go to the plant owner when the plant successfully blooms. This lets helping feel worthwhile while keeping the larger reward attached to finishing a plant.

• A member presses Plant Seed on the garden board.
• If they are not on cooldown and have not reached their active plant limit, Naya creates a plant message.
• Members press Water on a plant to help it grow.
• The All Plants button lets members browse active plants in that channel.
• When the plant reaches its required waters, it blooms and the owner receives bloom rewards.

Plants bloom when they receive enough waters. If a plant goes too long without water, it wilts, stays marked as finished, and its button is disabled. Use a generous wilt timer if your server is small or relaxed.

Make sure Naya can view the garden channel, send messages, embed links, use external emoji if your plants use them, and create or edit the messages she posts. If the channel is read-only for members, Naya still needs permission to send there.

Check plant cooldown, waters per day, per-plant water cooldown, max active plants, and whether the plant has already bloomed or wilted.

• Use a dedicated garden channel.
• Start with 3 or 4 plant types.
• Keep water rewards small and bloom rewards more exciting.
• Use a few common plants and one rare plant.
• Set wilt time long enough that members do not feel punished.

If the garden starts giving too much currency, lower water rewards first. Watering can happen often, while bloom rewards are naturally limited by waters required, plant cooldowns, and active plant limits.

The board can use a title, description, embed color, author text, footer text, banner image, thumbnail, author icon, and footer icon. Keep the description clear enough that members know what kind of requests belong there.

Save stores the draft. Save and Post publishes the board in the selected channel. A read-only public board channel works best: members interact with Naya's dropdown and buttons, while discussion happens in the thread attached to each request.

Free servers can create up to 4 co-op games or activities. Premium servers can create up to 25.

Useful request types include NA Co-op, EU Co-op, Raids, Dungeons, Quest Help, Art Commissions, Art Trades, Marketplace Offers, or Team Finder. The field labels should match the activity so members know exactly what to enter.

• A member selects a game or activity from the co-op board dropdown.
• Naya opens a form asking for region, UID or name, level or gear, runs or kills, and a short request message.
• Naya posts the request embed in the board channel.
• Naya creates a thread for that request so members can coordinate without cluttering the board.

Co-op reputation is per server. It appears beside helpers when they have it and is meant to gently highlight members who often help, not force a competitive grind.

Each game or activity can have its own ping roles. This lets Naya notify only the people who asked for that kind of request instead of pinging everyone. Use this carefully so the board stays helpful instead of noisy.

Members with a selected blacklist role cannot create co-op requests. This is useful for watch-only roles, temporary restrictions, or servers that want request creation limited to approved members.

The server-wide request cooldown prevents the same member from opening requests too quickly. The dashboard supports 0 to 10080 minutes. Use 0 only if you are comfortable with members creating requests without delay.

Make sure Naya can view the board channel, send messages, embed links, use external emoji if needed, create public threads, and send messages in threads. If the board channel is read-only for members, Naya still needs permission to post there.

Check whether the member is on cooldown, has a blacklist role, or is trying to use a request type that no longer exists. Also confirm the board has at least one valid game or activity configured.

• Use a dedicated board channel.
• Turn off regular member messages in that channel if you want the board to stay clean.
• Start with a few clear request types instead of every possible category.
• Use field labels that match the game or activity.
• Use ping roles only for groups that actually want those pings.
• Set expiration so old requests do not stay open forever.

Short cooldowns work well for fast games. Longer cooldowns and longer expiration windows work better for commissions, trades, or slower requests where the conversation may take time.

Use Save and Post in the dashboard to post Guildboard in the selected channel. If Naya has the previous board message stored, she updates that message when possible. If it is gone, she posts a new one.

Daily Check-In is the best first feature because it is simple and useful immediately. Add Daily Quiz, Weekly Trivia, Lottery, weekly stats, and chest tracking after the board already feels clear.

Guildboard can award server currency and leveling XP. If those systems are not configured, rewards may feel confusing or may not display as intended. Chest Tracker uses Server Currency chest settings.

Daily check-ins are live. Answer today's quiz for a bonus reward.

Weekly trivia ends on Sunday. Submit your answer before the draw.

Chest channels reset throughout the day. Check the tracker before hunting.

Do not enable every feature just because it exists. A board with Daily Check-In, one weekly feature, and one stats block often feels more useful than a board with every section turned on.

Check-In resets by UTC day. If a member says they already checked in even though it is a new local day, the UTC day may not have changed yet.

• What channel should new members read first?
• Which server role unlocks the art channels?
• What day do weekly events usually happen?
• Which pet rarity is the rarest in this server?

If a trivia question is already active, draw it first. This prevents old submissions from being mixed with a new prompt.

Use a modest main prize if lottery is frequent. Use a larger prize if it is weekly or event-based. Pity prizes help participation feel worthwhile even when only one member wins the main prize.

Weekly Hugs / Bonks shows hug and bonk leaders. Weekly Messages / XP shows message and XP leaders. These blocks make the board feel alive, but they are best when your server enjoys light visibility around activity.

Chest Tracker uses Server Currency chest settings and can show status for up to 12 configured chest channels. Set up chest channels in Server Currency first, then enable Chest Tracker on Guildboard.

Stats and chest information are freshest when the board is posted or refreshed. If members report stale data, save and repost or refresh the board after changing related settings.

Enable Daily Check-In only. Use a short notice such as Claim your daily reward here. Set a small currency reward and a small XP reward. This gives members a low-pressure reason to return without cluttering the board.

Create quiz questions about rules, useful channels, server currency, pets, or events. Keep rewards small. This helps members learn the server through daily prompts instead of asking staff the same questions.

Post one trivia question each Monday and draw it on Sunday. Use the notice to show when trivia ends. This gives the server a recurring activity that does not require constant moderation.

Use a main prize for the exact or closest winner and a small pity prize for up to 3 to 5 close guesses. This makes the lottery feel friendlier in small servers where one winner can otherwise feel too narrow.

Enable Daily Check-In, Chest Tracker, and Weekly Messages / XP. This turns Guildboard into a useful activity hub for servers that already use Server Currency and Leveling heavily.

Make sure Naya can view the selected channel, send messages, embed links, and use external emojis if your board uses custom emojis. If Naya is trying to update a deleted board message, use Save and Post again.

Check-In is once per UTC day. If they already checked in for the current UTC date, they need to wait for the next UTC day.

A member can submit one quiz answer per UTC day. Opening a quiz prompt does not count by itself, but submitting an answer does.

Draw the active trivia first, then create the next one. This keeps submissions and winners clean.

Check Server Currency chest channels, spawn settings, and whether Chest Tracker is enabled. The tracker cannot show chest channels that are not configured.

Guildboard should be glanceable. If members need to scroll through too much information, disable a feature or shorten the notice.

Daily rewards should feel nice but not replace your whole economy. If members can earn a large shop item from a few check-ins, lower check-in rewards or raise shop prices.

Daily Check-In is for routine. Weekly Trivia and Lottery are for rhythm. Stats and Chest Tracker are for visibility. Use each feature for the job it does best.

The ticket panel can use a title, description, color, author, banner, thumbnail, author icon, footer icon, and fields. Premium servers can also customize the panel footer text and post the panel through a webhook name and avatar.

Save stores your draft. Save and Post publishes the panel to the selected channel. Naya requires a logs channel, ticket category, post channel, and at least one open ticket type before posting. You can leave the ticket-type filter off to show every open type, or enable it to post a panel that only shows selected ticket types.

Free servers can create up to 4 ticket types. Premium servers can create up to 25. Example types include different queues such as Support, Report, Appeal, Purchase Help, or Event Help. You may send multiple ticket panels with your choice of ticket types in each.

Each type can have its own first message inside the ticket, with optional content above the embed, ping roles, embed title, description, color, thumbnail, large image, and fields. You can also add up to 5 short pre-ticket questions so members provide the needed details before the ticket opens.

When a ticket closes, Naya creates a transcript, sends it through the logs flow, and tries to DM the opener. Discord may block DMs depending on the member's privacy settings, so logs are the reliable staff copy. The dashboard transcript list can be searched by type, opener name, reason, ticket number, or opener ID, and sorted by latest, oldest, ticket type, or opener.

Naya needs permission to view channels, send messages, embed links, manage channels or private threads, manage permissions, and attach transcript files or links. Staff roles should be above normal member roles and easy to audit.

Channel names are cleaned into lowercase letters, numbers, and hyphens. Include a sequence value to avoid duplicates.

Start with Support, Report, and Appeal. Set a private logs channel, add staff roles to each type, keep opening messages short, and add pre-ticket questions only where they save staff time.

The panel can use a title, description, color, author text, banner, thumbnail, author icon, footer icon, and fields. Premium servers can customize footer text and use advanced panel presentation through the Embed Builder with multiple embeds or containers.

Free servers can create up to 4 application forms. Premium servers can create up to 25. Each form can be open or closed without deleting it.

Each form needs at least one question. Questions can be added, edited, removed, and moved. The dashboard question field allows up to 400 characters. Multiple-choice questions are supported and need at least 2 options. Naya allows up to 50 questions.

Naya sends the questions through DMs one at a time. Members can type cancel to stop. If Discord blocks DMs because of privacy settings, the member will need to allow server DMs before completing the application.

Completed applications are posted as review messages with the member's answers. Keep review channels private to the people who should see applicant information. They are also posted on the dashboard, where you can easily view all the submitted past and present applications. You can also change the status of the applications from the dashboard, though no dm will be sent to the user.

Use separate forms for separate purposes, keep questions short, set a private default review channel, and use ping roles only for teams that truly need alerts. Save and Post publishes the panel only after a post channel is selected. A form that takes 5 to 10 minutes to answer is usually more comfortable than a long interview in DM form.

Triggers match at the start of a member's message. Lower priority numbers run first when more than one responder could match. Keep triggers at least a few characters long and specific enough to avoid accidental matches.

Choices let one trigger send different possible responses. Use weights when one choice should be more common than another, such as several daily reward messages with different flavor text or rewards. For instance a rare gift card with an extremely small weight (or chance) of that choice happening like a gacha game. You can also confine the autoresponders to certain channels.

Cooldowns are per member and can be set in seconds, minutes, hours, or days. Members can run /cooldowns or -cd to see active autoresponder cooldowns in the server. You can also hide a responder from that cooldown list while keeping the responder active.

Use a one day cooldown, a friendly reply, and coin or XP rewards. Example reply: {user}, you claimed {reward_coins} {currency_text}. New balance: {user_balance_after}.

Use a required booster, VIP, or override role and a one day cooldown. Give a slightly better reward or a special DM message so boosters have a simple daily perk. Example reply: you've used your daily {mention}! you received {reward_item_qty} x {reward_item_key} and + {reward_coins} {currency_text} {currency_emoji} and {reward_xp} xp - new balance: {user_balance_after}~

Use send mode Both. Public reply: check your dms for a quick server guide! DM text can include rules, role links, introductions, and common channels. You can include buttons and/or dropdowns if you wish to help give them further details about your server.

/hug and /bonk allow 3 uses per 30 seconds per member. Naya keeps track of each member's hugs and bonks including in the /leaderboard and in the guild board, if one is set in the server.

When a member uses a hug or bonk, Naya checks the member's personal image set first only if custom hugs are enabled and the member is not blacklisted by having a blacklisted role from /main-settings. If personal images are unavailable, Naya uses the server default image set. If the server default set is empty or reset, she uses Naya's global default hugs and bonks images.

These are the hugs and bonks admins choose for the server from the dashboard or by using /hugs-default. Resetting hugs does not reset bonks, and resetting bonks does not reset hugs. Admins can also use /main-settings to disable custom hugs and bonks so members cannot have their own hugs and bonks images shown on the server, and only server or naya global defaults are shown.

Personal image sets are global to the user. They let a member use their preferred hug or bonk images across servers where Naya is available and custom images are allowed. In /main-settings, admins can choose a blacklist role so members with that role will not have their personal hug or bonk sets shown.

Some sites, including Imgur and Tenor, may not work reliably as direct media sources. The fastest reliable method is to drop the GIF into Discord, open the image, and use Copy Image Link. Do not delete that Discord upload afterward, because Naya still needs the copied Discord media URL to exist.

Use direct URLs that end in common image formats such as .gif, .png, .jpg, or .webp, or stable Discord CDN links from uploaded images.

Use direct, stable image URLs, preview every image before saving, and keep server defaults appropriate for the whole community. If a link previews incorrectly, replace it with a Discord copied image link. Hugs and bonks work best as light social texture, with stats as a fun extra instead of the whole point.

Free servers can have up to 2 quests. Premium servers can have up to 500 quests.

Repeatable quests can be completed multiple times and should usually have a cooldown. Non-repeatable quests can only be completed once by each member.

Naya records the member's current objective count when they accept the quest. The quest completes when that count increases by the goal amount.

Objective text is the member-facing explanation, such as "Send 10 messages". Keep it short and make sure it matches the selected objective type and goal amount.

Use larger rewards for one-time quests and smaller rewards for repeatable quests. Repeatable quests are easier to balance when they have a clear cooldown.

If a member accepted a quest before you edited it, that accepted quest keeps the older objective version for that member. If you are changing the core goal, it is often cleaner to delete the quest and create a new one.

Keep quest names and objective text understandable at a glance. Let quests support normal server activity instead of pushing members into behavior they would not otherwise do.

Posts in a selected channel when a member joins. Use this for greeting text, rules links, role instructions, or a short server introduction.

Posts when a member leaves. Keep this short; these messages are most useful for staff awareness or community continuity.

Posts when Discord sends a server boost event that Naya can see. For boost event messages to work, enable Server Settings > Engagement > Send messages when someone boosts this server, and make sure Naya can view that channel.

Sends private messages when possible. Some users block server DMs, so public setup should not depend on DMs being delivered every time.

Each welcome message type can hold multiple saved messages. Naya chooses one at random when the event happens. Free servers can save up to 3 messages per type, and premium servers can save up to 10.

Set the embed color to random or enable Rainbow in the dashboard to make Naya choose a new embed color for each sent message.

Welcome and farewell cards can allow or ignore bot accounts. Leave bot messages off for normal community welcomes; enable them only when your server intentionally wants bot joins or bot leaves announced.

Check that a public channel is selected and that Naya can view the channel, send messages, embed links, and use webhooks if webhook identity is enabled.

Discord may block DMs depending on the member's privacy settings. Naya also has to share a mutual server with the user; otherwise Discord does not allow her to send that DM.

Depending on your settings, boosters can rename their role, choose a color, add or remove a role icon, and preview changes before applying them. This can all be done by simply running the /boosterperks command.

Naya automatically places each custom booster role right above the Discord booster role. Make sure Naya's highest role is above the booster role so she can create, move, and edit the custom roles.

Naya automatically deletes a member's custom booster role when the member leaves the server, stops boosting, or loses the configured override role.

Daily write limits protect the server from excessive role edits. Discord allows up to 300 roles in a server, but most servers do not receive enough boosts for this to become a practical issue. Keep logs enabled if staff want an audit trail of role changes.

Premium servers can use richer booster perks presentation, including customized public perk embeds, media, and change gift limits.

Enable logs, set a clear override role if needed, keep role write limits on, and post a short explanation telling boosters to use /boosterperks. For boost event logs to work, enable Server Settings > Engagement > Send messages when someone boosts this server, and make sure Naya can view that channel.

Best for short reminders, resource links, or channel instructions. Plain content appears above the embed when both are used.

Best for rules, schedules, frequently used links, or multi-part information. You can set title, description, color, author text, footer text, thumbnail, banner, and icon URLs.

Premium servers can send stickies through a custom webhook username and avatar. Free servers send stickies as normal Naya bot messages.

Free servers can create up to 4 stickies. Premium servers can create up to 300 stickies.

Stickies are most helpful when they answer repeated questions. Too many persistent posts can make active channels feel noisy, so reserve them for information members genuinely need.

Naya needs permission to view the channel, send messages, embed links, manage messages for clean reposting, and manage webhooks if webhook identity is enabled.

Save stores the sticky settings without posting immediately. Save and Post stores the settings and asks Naya to place the sticky in the selected channel.

If you edit a sticky that is already posted, save it and refresh or post again so the visible channel copy matches the dashboard version.

Check that the channel still exists, the sticky has content or embed text, and Naya can view the channel, send messages, and embed links.

Webhook identity requires premium and a valid webhook username or avatar URL. Naya also needs manage webhooks permission in that channel.

If something goes wrong, such as missing permissions or an invalid channel, Naya may disable the sticky so it does not keep failing. Fix the issue, enable the sticky again on the dashboard, then save and post it again.

Free servers can run up to 6 active giveaways at the same time. Premium servers can run up to 25 active giveaways.

Free server giveaways can last up to 30 days. Premium server giveaways can last up to 180 days. If a giveaway needs more time, use /gedit before it ends and extend the duration as needed.

Admins can use giveaway commands by default. If you want trusted non-admin roles to manage giveaways, add those roles in /main-settings.

A giveaway can require members to be in another Discord server. Naya verifies this from server membership cache, so the required server must also have Naya in it.

If the required server is on a different cluster, there can be a short delay when the cache expires. A member may be told they are not in the required server even after joining; if this happens, wait about a minute and try joining the giveaway again.

Bonus roles can add extra entries for members who have those roles. You can choose whether all bonus roles stack together or whether Naya should only use the highest bonus.

Naya can assign up to 10 selected winner reward roles when the giveaway ends. She needs permission and a high enough role to assign them.

Giveaways can create no thread, a public thread, or a private thread when they end. Threads are best for giveaways where staff need winner follow-up.

When a giveaway ends naturally, Naya checks roles again near the end so winners are based on fresh eligibility. Role data is refreshed up to about 30 seconds before the giveaway ends.

Naya also checks whether entrants are still in the required server before they can win. If the required-server check takes too long after multiple attempts, Naya may draw winners without that final required-server filter so the giveaway can still finish during cluster or cache issues.

/gend and /greroll may pull winners who are no longer in the required server. Those members still had to pass the required-server check when they originally joined the giveaway.

Regular Embeds create classic Discord embed messages. They are best for rules, server guides, staff announcements, shop panels, event summaries, role menus, ticket panels, and any message that should look clean without needing a complex layout.

Containers create newer component-style layouts with text blocks, media, dividers, sections, accessories, and action rows. Use them when you need a richer layout than a normal embed, such as a structured guide, multi-section panel, or visual menu.

The preview updates as you edit. Samples are available as starting points, which is faster than rebuilding common layouts from scratch. Always preview on a narrow window too, because Discord users often read panels on mobile.

Use direct image URLs that start with http:// or https://. If a site gives a preview page instead of the raw image file, Discord may not render it. Uploading the image to Discord and copying the image link is often the fastest reliable path.

Naya needs Manage Roles, and her highest role must be above every role she gives or removes. Verification actions will not grant or remove dangerous Administrator roles. If a role action fails, check role order first.

Naya Commands dropdowns can show the server's ticket types or application forms. It allows you to post a completely customized panel. However, note that when updating ticket types or application forms you will need to repost it to update.

Bot Post sends the message normally as Naya in the selected channel. This is the standard delivery method and is available to free servers.

Custom Webhook mode lets Naya post with a custom username and avatar. Discord Webhook mode uses a pasted Discord webhook URL.

To edit an existing Discord webhook message, use Discord Webhook mode with the webhook URL and the numeric webhook message ID. Editing Naya-created custom webhook posts is not the same path, so use Discord Webhook mode when editability matters.

Forum channels need an existing forum post or thread target. Paste the thread ID, message link, or exact active thread name. If a thread name is not found, paste the ID instead.

Generate a builder link before posting complex messages. The link saves the builder state, including embeds, containers, buttons, dropdowns, and interaction data, so you can restore the message later without rebuilding it.

Use Load Link to restore a builder link. Use the edit or restore field when you have a Discord message link and want to load that message into the builder. If the message cannot be edited directly, the dashboard can still restore its contents so you can post a new version.

Discord panels are often read on mobile. Keep button labels short, avoid crowded field names, and use dropdowns when a role menu has more than a few choices.

Use a Regular Embed with a short title, a clear description, and fields for each important rule or channel. Add a link button to the full rules page if the server has one. Keep the embed itself short enough that members actually read it.

Use dropdown options or buttons with Toggle All Roles. Put every color role in the same group so choosing one color removes the other color roles first. Make sure Naya's role is above every color role.

Use a button with Verification. Configure roles to add, roles to remove, and a private success reply. This is useful for member screening, rules acceptance, or unlocking the main server after a simple click.

Use a Naya Commands dropdown for tickets or applications. This keeps the panel current with the configured ticket types or application forms, instead of manually recreating every option in the embed builder.

Premium servers can connect custom item actions to buttons or dropdowns. This is useful for paid panels such as suggestions, confession forms, top-up forms, custom reward claims, gacha boxes, or seasonal perks.

Build the announcement once, generate a builder link, and save that link somewhere staff can find. Next time, load the link, change the date, image, and details, then post again. This prevents every announcement from being rebuilt by hand.

First see if the emojis in buttons and dropdowns were valid. Make sure Naya can view the channel, send messages, embed links, use external emojis, and manage webhooks if webhook posting is selected. Also check that the message does not exceed Discord limits.

Use a direct image link. Some sites provide a webpage link instead of an image file. If needed, upload the image to Discord, copy the image link, and do not delete the source Discord message afterward.

Check Manage Roles permission and role order. Naya cannot manage roles that are equal to or higher than her highest role.

Check that the server has ticket types or application forms configured and available. Live dropdowns can only show what exists for that server.

Make sure the full builder link was copied. Older or incomplete links may not restore correctly.

Do not combine rules, tickets, role menus, and announcements in one panel unless they truly belong together. A focused message gets fewer support questions.

Buttons are good for 1 to 5 clear choices. Dropdowns are better for longer menus, role lists, tickets, applications, and anything where labels need more space.

Generate a builder link before posting anything with actions. It is much easier to edit later, and it gives staff a reliable backup.