Official API for 3rd Party Tools

NivenFresNivenFres ✭✭✭✭
With the recent happenings with iampicard, I propose that DB make a publicly available secure web API available. This would allow for an official interface that 3rd party tools could be created, yet the information controlled by DB. I would suggest API functions that allowed read-only functionality, no direct manipulation of the game itself.

I believe most of the community wants to be able to query information about their accounts.

The kinds of functions I would recommend would be things:
  • The ability to get a list of an individual users characters and their stats.
  • The ability to get a list of a user's inventory.
  • The ability to get a list of a user's ships.
  • The ability to get the stats of any character given a set of parameters (e.g. 2/5 FF Level 55, items 1 & 2 equipped, with 3 & 4 missing).
  • The ability to get information about the current voyage (primary, secondary stats, ship stats, bonus skill for each slot).
  • The ability to get information about the current gauntlet round.

I believe things like this would still give the general population the information they want, without allowing for manipulation of the game itself. It would also allow different developers to create different tools.
"If it wasn't for autocorrect, we wouldn't have Tuvok on a Giraffe."

Comments

  • Dirk GundersonDirk Gunderson ✭✭✭✭✭
    Seconded, even if it were only the first four items. Exporting data is a painful, error-prone process right now and an export function would make things much easier for further analysis.
  • I THIRD THIS MOTION
  • I'm in favor of this wholeheartedly and additionally so as it spits in the eye of the doxxing petaQs.
  • mejoyhmejoyh ✭✭✭
    bump!
  • Mr. RiderMr. Rider ✭✭
    edited January 16
    I am on board for this too, tools are needed, I have used them in the past to make informed choices.
  • FetaroFetaro ✭✭
    edited January 16
    We need to know what we are allowed to do, and what are the different APIs we can call. Even if the API documentation is not ready, we need to know what we are allowed to do.

    If you answer "You can do everything excepted macros", you'll have precise your definition of macros, since it is kinda vague. For some people, a button to recall a voyage is a macro. For instance, was IAP 100% ok?

    We need to have a clear statement from you, since some people will feel like what we'll do isn't authorized, with its lot of nasty consequences.
  • NivenFresNivenFres ✭✭✭✭
    edited January 16
    Fetaro wrote: »
    We need to know what we are allowed to do, and what are the different APIs we can call. Even if the API documentation is not ready, we need to know what we are allowed to do.

    If you answer "You can do everything excepted macros", you'll have precise your definition of macros, since it is kinda vague. For some people, a button to recall a voyage is a macro. For instance, was IAP 100% ok?

    We need to have a clear statement from you, since some people will feel like what we'll do isn't authorized, with its lot of nasty consequences.

    That is why what I propose doesn't actually support any game interaction. This is requesting an official query-only interface. It would allow for requesting information (crew, ships, etc), but no actual interaction with the game. It removes any direct game automation.
    "If it wasn't for autocorrect, we wouldn't have Tuvok on a Giraffe."
Sign In or Register to comment.