Skip to content

Create /locker command #65

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 8 commits into
base: main
Choose a base branch
from
Open

Conversation

AlphaX50
Copy link

@AlphaX50 AlphaX50 commented Dec 28, 2024

I created the /locker command allowing users to view their Fortnite locker in Discord. It displays locker items (skins, emotes, emote, glider, loading screens) according to configurable season and chapter filters. An aesthetic design has been added, with a circular logo in the upper-left corner of the canvas.

Main features:

  1. Item display: Displays locker items according to selected category (skins, emotes, etc.).
  2. Filter by Season and Chapter: The command filters items according to the seasons and chapters defined in config.json. If bEnableLockerLimit is false, filtering is disabled and all items are displayed.
  3. Enhanced Design: A dark background with visible text and a circular logo in the upper left corner are added to improve appearance.
  4. Page Management: Items are divided into pages, with each page containing a configurable number of items.

Configuration (config.json):

{
  "bEnableLockerLimit": true,
  "bLimitChapter": 1,
  "bLimitSeason": 7,
}

image
image
image

@Alon122
Copy link
Contributor

Alon122 commented Dec 28, 2024

The logoY is not defined

image

@AlphaX50
Copy link
Author

error fix !

@burlone0
Copy link
Contributor

@AlphaX50 Add like if u have more pages u can look the others with /locker [category] [user] [page] and yes add user too, for user and page make sure the options are not required

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants