Skip to content
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

📒 Command Info Accessible as Command Structure Event Value #5885

Closed
1 task done
hapily04 opened this issue Aug 7, 2023 · 0 comments
Closed
1 task done

📒 Command Info Accessible as Command Structure Event Value #5885

hapily04 opened this issue Aug 7, 2023 · 0 comments
Labels
completed The issue has been fully resolved and the change will be in the next Skript update. enhancement Feature request, an issue about something that could be improved, or a PR improving something. priority: lowest "Nice to have" updates that are not required (tiny low impact bug fixes or QoL enhancements).

Comments

@hapily04
Copy link

hapily04 commented Aug 7, 2023

Suggestion

Currently these values require a string for the command name as it uses the commandmap to find the command and access these values. However, these should be accessible as event values in the trigger of the command.

What I have to do right now to get the usage of the command I'm writing it in:

command /gamemode [<gamemode>] [<player>]:
    permission: gamemode
    aliases: /gm
    usage: /hi
    trigger:
        broadcast usage of command "gamemode"

What I should be able to do:

command /gamemode [<gamemode>] [<player>]:
    permission: gamemode
    aliases: /gm
    usage: /hi
    trigger:
        broadcast usage

Why?

Shouldn't have to mention the name of the command that the trigger is already located under

Other

No response

Agreement

  • I have read the guidelines above and affirm I am following them with this suggestion.
@hapily04 hapily04 changed the title Command Info Accessible as Command Structure Event Value 📒 Command Info Accessible as Command Structure Event Value Aug 7, 2023
@AyhamAl-Ali AyhamAl-Ali added enhancement Feature request, an issue about something that could be improved, or a PR improving something. priority: lowest "Nice to have" updates that are not required (tiny low impact bug fixes or QoL enhancements). labels Aug 7, 2023
@UnderscoreTud UnderscoreTud added the PR available Issues which have a yet-to-be merged PR resolving it label Aug 8, 2023
@TheLimeGlass TheLimeGlass added completed The issue has been fully resolved and the change will be in the next Skript update. and removed PR available Issues which have a yet-to-be merged PR resolving it labels Oct 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
completed The issue has been fully resolved and the change will be in the next Skript update. enhancement Feature request, an issue about something that could be improved, or a PR improving something. priority: lowest "Nice to have" updates that are not required (tiny low impact bug fixes or QoL enhancements).
Projects
None yet
Development

No branches or pull requests

5 participants