Skip to content

TeamsAPI integration #52

Description

@ez-plugins

To get more team work within the community and get unity within faction/clan/team integration I've created TeamsAPI, to prevent making making an external extension in TeamsAPI for FactionsUUID that breaks with FactionsUUID changes I would suggest me contributing optional TeamsAPI integration into FactionsUUID.

Idea

  • Make an abstraction layer for the optional TeamsAPI providers to implement TeamsAPI into FactionsUUID as optional integration
  • Make it optional (with disable option) but auto-detect by default through a configuration option.
teamsapi:
  enabled: auto
  • Make it work together with the already implemented features of FactionsUUID

Details

In big lines (black/white) this will help the Factions ecosystem to develop more customized Faction solutions through time, which helps you as maintainer to not have to implement very niche features into the Factions plugin.

Probably some more configuration options / better defaults would be needed in both TeamsAPI and FactionsUUID for correct API usage when available with safe fallback on existing features. I would suggest to do this in direct contact and talk this through point per point when we come at this point.

Open for any feedback.

Kind regards,
Shadow48402

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions