jedmund/hensei-api

An API to help Granblue Fantasy players create and share teams and strategies.

README

This README would normally document whatever steps are necessary to get the application up and running.

Things you may want to cover:

• Ruby version

• System dependencies

• Configuration

• Database creation

• Database initialization

• How to run the test suite

• Services (job queues, cache servers, search engines, etc.)

• Deployment instructions

• ...

hensei-api's Issues

Allow removing items from teams

Ensure that destroy works on GridCharacter GridWeapon and GridSummon

Allow users to "remix" teams by copying them to their account to edit

Frontend issue: jedmund/hensei-web#57

Users should be able to copy other people's teams to their own account to edit and add substitutions or improvements.

Remixed teams should leave a breadcrumb trail so you can see derivative teams on the original team page

Base skills cannot be selected

We introduced a bug at some point that made it so base skills (i.e. from Dancer) cannot be selected on their EXII equivalent class.

Frontend issue exists for visibility: jedmund/hensei-web#63

Setting multiple options through the job_skills endpoint can 422 if previous skills exist already

If you try to set multiple subskills at once but there's already some set from before, it actually checks them one by one, and since the first one in this case is miserable mist, it locks, even though the final result this call would make is valid

Write gbf.wiki parser

Mismatch between API and frontend when adding a summon without specifying uncap_level

The request:

Result:

Support third-party auth

People might be more compelled to sign up if we support some third-party services. We should be judicious about which to support and try not to support too many.

Unfortunately, Twitter is a shoe-in because of the Granblue community, but Discord, Apple and Google might be good alternatives.

Changing summon uncap doesn't work, apparently

It works but lol

https://puu.sh/JQzNb/1ca02c1463.png

Endpoints for getting all characters, weapons, or summons

Right now there's an endpoint for getting specific character, weapon, or summon but there isn't one to get all of them. Being able to get the entire dataset would be a nice feature to have. Having everything included probably is not needed. Could also just go with some basic information such as ID, Name (En/Jp), and Element.

Better filters for low-quality teams

People started making grids that are just multiples of the same weapon several times. We should filter these out.

Can't select Yatima

weird

Implement character modifications (EMP items, styles and awakening)

These changes should go on GridCharacter similar to how mods are implemented on GridWeapon.

Add nicknames for characters

Charlotta is Box, Threo is Cake and Sarasa, etc.

Update raid list

• Add Dread Barrage section
• Add raid ordering so NM150 shows up above NM200

Add granblue_id to weapon keys

• Determine whether IDs for different types of weapon_keys overlap, as that will affect whether we need a unique constraint or not on the column.
• Add granblue_id column to WeaponKeys table
• Return granblue_id in the WeaponKeyBlueprint
• Populate with data

Enforce summon limits

Only 1 Beelzebub and Yatima can be equipped per team