Permalink
Switch branches/tags
Commits on Oct 23, 2018
  1. Add unregister method for JDA (#174)

    simpleauthority authored and aikar committed Oct 23, 2018
    This PR is to allow users to unregister commands from the `JDACommandManager`
    
    Currently slightly flawed, needs research. When re-registering it spits out a load of messages like so:
    ```
    SEVERE: [ACF] ACF Error: settings registered subcommand boss role for root command settings - but it is already defined in settings
    Sep 20, 2018 3:58:31 AM com.algorithmjunkie.freelance.gachapon.acf.JDACommandManager log
    SEVERE: [ACF] 2 subcommands of the same prefix may not be spread over 2 different classes. Ignoring this.
    ```
    
    Not sure if this is just for me, or if it's for all.
Commits on Sep 10, 2018
  1. (DEPLOYED ACF) Updated JavaDocs

    aikar committed Sep 10, 2018
  2. CommandIssuer should be IssuerOnly context

    aikar committed Sep 10, 2018
    Likely fixes #170
Commits on Sep 2, 2018
  1. (DEPLOYED ACF) Updated JavaDocs

    aikar committed Sep 2, 2018
  2. Register SubClasses before Command register() (#169)

    Dariasc authored and aikar committed Sep 2, 2018
    This is so the SubCommands from the SubClasses get added to the SubCommand map before calling **addChild()**
Commits on Aug 27, 2018
  1. Fix typo (#164)

    MrPowerGamerBR authored and aikar committed Aug 27, 2018
  2. Fixes #165 (#166)

    Gabik21MC authored and aikar committed Aug 27, 2018
    This seems kind of wrong to me. Somone calling RegisteredCommand#getHelpText out of context will run into the same issue.
Commits on Aug 19, 2018
  1. (DEPLOYED ACF) Updated JavaDocs

    aikar committed Aug 19, 2018
  2. Register CommandIssuer context

    aikar committed Aug 19, 2018
Commits on Aug 6, 2018
  1. Improve logging concerning command replacements (#161)

    NiklasEi authored and aikar committed Aug 6, 2018
    The code is now checking for placeholders, that are not replaced. This would also warn the dev if he completely forgets to register a replacement. 
    The downside of this is, that any %.* kind of pattern, that is NOT supposed to be a replacement will cause an error message. But since I couldn't come up for a reason to include % in any of the Annotation values other than a replacement, I decided this is much easier than checking all "old" commands when a replacement is registered.
    Alternatively, I could collect all these unreplaced replacements and check against the collection when a new one is registered. This would not warn a dev that forgot to register the replacement, but on the other hand still allows the use of %. Please tell me what you think.
    
    resolves #160
Commits on Aug 3, 2018
  1. (DEPLOYED ACF) Updated JavaDocs

    aikar committed Aug 3, 2018
  2. Deny permissions if command is issued by a webhook (#156)

    mikroskeem authored and aikar committed Aug 3, 2018
  3. Replace Guava Iterables (#158)

    mikroskeem authored and aikar committed Aug 3, 2018
    Goes under #120
    
    After this, only MultiMaps remain.
Commits on Jul 25, 2018
  1. (DEPLOYED ACF) Updated JavaDocs

    aikar committed Jul 4, 2018
  2. Make Users optional arguments (#139)

    simpleauthority authored and aikar committed Jul 25, 2018
    This PR allows `User`s to be optional command arguments similar to how the annotation operates on Bukkit's `Player`.
Commits on Jul 24, 2018
  1. fix compilation of example plugin (#154)

    Gabik21MC authored and aikar committed Jul 24, 2018
Commits on Jul 19, 2018
  1. Drop trivial Guava usages (#142)

    osipxd authored and aikar committed Jul 19, 2018
Commits on Jul 4, 2018
  1. Sanitize Bukkit Command Label Before Passing On (#149)

    willies952002 authored and aikar committed Jul 4, 2018
    Fixes #146 
    
    This might not be the 100% perfect method for fixing this, but as it stands, it's the least amount of diff
     needed to fix said issue.
Commits on Jun 23, 2018
  1. remove mvn build since travis does that

    aikar committed Jun 23, 2018
  2. add Travis

    aikar committed Jun 23, 2018
Commits on Jun 19, 2018
  1. (DEPLOYED ACF) Updated JavaDocs

    aikar committed Jun 19, 2018
  2. Enable ability to disable logging of uncaught exceptions

    aikar committed Jun 19, 2018
    You must pass your own exception handler in order to do this.
    
    Implementors need to be sure to log if its not a desired throw or
    otherwise you will have silent command failures.
Commits on Jun 18, 2018
  1. Forgot to implement method for sponge (#144)

    Gabik21MC authored and aikar committed Jun 18, 2018
  2. Improvements (#143)

    Gabik21MC authored and aikar committed Jun 18, 2018
    Improve help output for commands split over multiple base commands
    Fix help last page detection
    Fix missing argument on Player Context Resolve
    Expose registered root commands
Commits on Jun 17, 2018
  1. Add russian translation (#141)

    osipxd authored and aikar committed Jun 17, 2018
Commits on Jun 13, 2018
  1. (DEPLOYED ACF) Updated JavaDocs

    aikar committed Jun 13, 2018
  2. (DEPLOYED ACF) Updated JavaDocs

    aikar committed Jun 13, 2018
Commits on Jun 5, 2018
  1. Update Spanish translations (#140)

    Snow-Pyon authored and aikar committed Jun 5, 2018
Commits on Jun 3, 2018
  1. (DEPLOYED ACF) Updated JavaDocs

    aikar committed Jun 3, 2018
  2. [JDA] Fix User context resolution (#138)

    simpleauthority authored and aikar committed Jun 3, 2018
    When @ mentioning someone in Discord, if you manually click the user's name then the ID will be in the chat field as "<@!...>". However, one can _also_ mention a user like so "<@...>".
    
    This PR handles both cases.
  3. (DEPLOYED ACF) Updated JavaDocs

    aikar committed Jun 3, 2018
  4. Repair context types, add Role context, add CrossGuild annotation (#137)

    simpleauthority authored and aikar committed Jun 3, 2018
    In a previous PR, some contexts were not changed from **IssuerOnly** to **IssuerAware**. This has been patched.
    
    I've added a context to resolve a Role. It makes use of the next item I added.
    
    The CrossGuild annotation is used to signify whether or not the context is to be interpreted from a guild perspective or a bot perspective (i.e. all guilds). This annotation could probably be better named.