Search, filters, and editing records

Admin lists can contain many records. Searching first is safer than paging through every result or creating a duplicate. The search box is at the top of a model list. Enter a distinctive value, press Enter, and read the columns in the returned rows before opening one.

Search is specific to the page you are on. A search for Jordan on Collectibles looks through collectible details; the same search on Players looks through player information. It is not a global search across every model.

What to search for

Use the most stable value you have:

• Collectibles: name, short name, internal code, edition name, ability, special effect, emoji, or artist/source credit.
• Player profiles: Discord user ID or display name. A Discord numeric ID is the safest choice when several players have similar display names.
• Player collectibles: collectible name or code, owner Discord user ID, original catcher ID, special name, or special tag.
• Commands, responses, and feature flags: command name or key. Commands can also be searched by instance slug or add-on slug in a global view.
• Packs and boosters: name, code, or emoji. Pack inventory can be searched by the owning player’s Discord ID or the pack name.
• Trades, orders, and auctions: the participating Discord user ID; auction item and bid lists also accept their related numeric record ID.
• Imports and deployment records: the instance slug, creator username, action, status, or container name, depending on the list.

Searches are case-insensitive in normal use. Start with a unique part of a name rather than pasting a long sentence. If too many rows appear, add a filter instead of guessing which one is correct.

Filters and result columns

The filter controls narrow a list by a known state. They do not change anything until you choose a value, and they can be removed to return to the full scoped list.

Common filters include:

• Enabled: use when finding a feature, collectible, special, pack, booster, or command that is active or inactive.
• Status: use for trades, auctions, imports, deployment operations, runtime records, and billing membership states.
• Tradeable and Deleted: use on player collectibles to tell whether an item can still be traded or has been removed from normal use.
• Purchasable, Openable, and Usable: use on packs and boosters to understand why a player can or cannot buy, open, or activate something.
• Type, source, or action: use on commands, trade items, boosters, spawn records, and deployment records to focus on one kind of activity.

Read the result columns before clicking a record. In an owner view, the visible columns focus on player-facing information. In a global view, an Instance column often appears; verify it before editing. This is the final check that a record belongs to the bot you intended to manage.

Sorting and pagination

Click a column heading when the interface presents it as a sort control. Use it to bring names, IDs, dates, or status values together. Sort order only changes how the list is displayed, not the data itself.

There are 50 rows per page. Use the page navigation at the bottom after applying a narrow search or filter. Avoid selecting rows across different pages for one bulk action; confirm the selection on the visible page first.

Autocomplete fields

Many relationships use an autocomplete field instead of a long dropdown. Examples include choosing a collectible for a player-owned item, a player for a trade or pack, a template for a special, and an edition for a pack reward.

1. Click the field and type a few characters of the local name, code, or ID.
2. Wait for the suggestions.
3. Read the label carefully and click the exact result.
4. Save the record and reopen it if you need to verify the selected relationship.

Autocomplete loads results a page at a time. Make the term more specific if you cannot see the correct suggestion. Do not type an arbitrary global ID or a value copied from another instance: owner-mode suggestions are intentionally limited to the selected instance.

Adding a record

Press Add [model] only after confirming that the record does not already exist. Required fields are marked by the form. In an owner or helper view, the instance is applied automatically and is not shown. A global administrator may need to choose the instance explicitly.

Use Save and continue editing when you need to check a card preview, add a second relationship, or make several related changes. Use Save and add another when entering a batch of independent records. Use plain Save when the record is complete and you want to return to search results.

An error at the top of the form means nothing was saved until you correct the highlighted field. Read the field-specific message instead of repeatedly pressing Save. Common examples are a reward maximum lower than its minimum, a required related record that was not selected, or reward content that belongs to a different instance.

Bulk actions

Bulk actions affect every checked row, so use them carefully. Select rows with the left checkbox, choose the action from the action dropdown, then press the action button. Kompendium confirms the number of records changed in a message.

The most common bulk action is on Collectible specials: Enable selected specials and Disable selected specials. Filter the list first, select only the specials for the intended event, run the action, then check the enabled column. Global administrators may also have subscription and provisioning actions on the Users and Patreon pages. Those actions affect accounts or deployments and should be used only by platform operators who understand the result.

Record history and deletion

Use the record’s History control to review changes made through the admin. It is useful for finding out when a status, name, or permission changed. It does not restore an older version for you; compare the old and new values, then deliberately edit the record if a correction is needed.

Delete removes the record after confirmation. Never use it as a way to hide a player-facing feature. Prefer an Enabled or Active field when one exists. Some records are protected: the General Edition cannot be deleted, and deleting a non-general edition moves its collectibles to General Edition instead. Before deleting packs, player items, listings, or configuration records, create a manual backup from the dashboard’s Data page.