Skip to main content

Seasons

Open Various > Seasons.

How The System Works

Create seasonal leaderboards connected to MySQL data or manual ranking data. This page stores the records and settings used by the related admin workflow, storefront page, checkout flow, support area, theme, or integration. After saving, refresh the affected page and test the result from the user side when possible.

Before You Fill The Form

Check that your admin role has permission for this page. If the form depends on a payment provider, server connection, theme module, or external account, configure that dependency before saving. If a selector is empty, create the related product, category, user, role, provider, server, or currency record first so it appears in the dropdown.

How To Fill The Form

FieldHow to fill it
Season nameEnter the visible name users or admins will recognize in lists, cards, menus, or public pages.
MySQL connection statusChoose whether this record should be active, visible, public, required, or shown to users.
MySQL serverSelect or enter the server that should handle delivery, commands, status checks, or display.
MySQL databaseFill this field with the value requested by the label. If it is optional and you are unsure, leave it empty and test the result.
MySQL portEnter only the numeric port when the field asks for a port.
MySQL usernameEnter the visible name users or admins will recognize in lists, cards, menus, or public pages.
MySQL passwordCopy this value exactly from the provider, server, Discord, payment panel, or integration dashboard. Do not add extra spaces.
MySQL tableFill this field with the value requested by the label. If it is optional and you are unsure, leave it empty and test the result.
Username columnEnter the visible name users or admins will recognize in lists, cards, menus, or public pages.
Ranking columnFill this field with the value requested by the label. If it is optional and you are unsure, leave it empty and test the result.
Continuous season statusChoose whether this record should be active, visible, public, required, or shown to users.
Season startFill this field with the value requested by the label. If it is optional and you are unsure, leave it empty and test the result.
Season endFill this field with the value requested by the label. If it is optional and you are unsure, leave it empty and test the result.
CommandsFill this field with the value requested by the label. If it is optional and you are unsure, leave it empty and test the result.
ServersSelect or enter the server that should handle delivery, commands, status checks, or display.

Create Or Update A Record

  1. Open the page from the admin menu.
  2. Click the add, create, publish, send, give, ban, upload, or generate action shown on the page.
  3. Fill the required fields first. Required fields are usually marked with an asterisk in the panel.
  4. Fill optional fields that affect display, delivery, pricing, limits, rewards, integrations, or visibility.
  5. Save the form and wait for the success message.
  6. Open the list or public page to confirm that the record works as expected.

Page Actions

  • Add season: Opens the form for creating or publishing a new record.
  • Edit season: Opens the selected record so you can change its saved values.
  • Check database connection: Verifies the connection, configuration, or selected value before you rely on it.
  • Add column: Opens the form for creating or publishing a new record.
  • Add server: Opens the form for creating or publishing a new record.
  • Add command: Opens the form for creating or publishing a new record.
  • Delete selected seasons: Removes the checked records from the list. Use it only after confirming the selection.

After Saving

Return to the list and confirm that the record is visible. If the page supports ordering, drag the record into the correct position and click Save changes. Then test the affected user flow, such as checkout, login, support, content display, reward delivery, or integration sync.

Important Notes

  • Test the database connection before saving.
  • Column names must match the external MySQL table exactly.

Common Issues

The record does not appear to users Check status, visibility, date limits, stock or usage limits, role permissions, and whether the related extension is enabled. A dropdown is empty Create the related record first. For example, products need categories, SMM products need providers, rewards may need products, and server delivery needs a connected server. Saving works but the feature does not run Check external credentials, server connection, API keys, theme compatibility, cache, and required extension settings.