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
| Field | How to fill it |
|---|---|
| Season name | Enter the visible name users or admins will recognize in lists, cards, menus, or public pages. |
| MySQL connection status | Choose whether this record should be active, visible, public, required, or shown to users. |
| MySQL server | Select or enter the server that should handle delivery, commands, status checks, or display. |
| MySQL database | Fill 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 port | Enter only the numeric port when the field asks for a port. |
| MySQL username | Enter the visible name users or admins will recognize in lists, cards, menus, or public pages. |
| MySQL password | Copy this value exactly from the provider, server, Discord, payment panel, or integration dashboard. Do not add extra spaces. |
| MySQL table | Fill 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 column | Enter the visible name users or admins will recognize in lists, cards, menus, or public pages. |
| Ranking column | Fill 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 status | Choose whether this record should be active, visible, public, required, or shown to users. |
| Season start | Fill 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 end | Fill this field with the value requested by the label. If it is optional and you are unsure, leave it empty and test the result. |
| Commands | Fill this field with the value requested by the label. If it is optional and you are unsure, leave it empty and test the result. |
| Servers | Select or enter the server that should handle delivery, commands, status checks, or display. |
Create Or Update A Record
- Open the page from the admin menu.
- Click the add, create, publish, send, give, ban, upload, or generate action shown on the page.
- Fill the required fields first. Required fields are usually marked with an asterisk in the panel.
- Fill optional fields that affect display, delivery, pricing, limits, rewards, integrations, or visibility.
- Save the form and wait for the success message.
- 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.
