frzyc

Results 109 comments of frzyc

Sounds good. I'd say something like 300 characters for names, and showing maybe first 100 character before truncating.

I wouldn't mind condensing this information, my only argument is to keep these expanded to assist user with understanding the new workflow. Lets leave this for a few weeks, then...

Condensing the team description can be another issue we can tackle now, an additional work item might be making the multi-line input expandable.

> For importing GO data on another GO data for team/loadout, I believe the current logic is the import data overwrite the existing data. I think I am fine with...

Just the number of team/loadout/builds before import, and after

yeah loadouts are called `teamChars`(due to legacy naming) so it would be `database.teamChars.values.length`

No, adding this to real builds will potentially break the "plug and play" versatility of loadouts,(and subsequently team exim) I am not sure if I want to cover the usecase...

we could add constellation delta as a separate stat, through they would not be different in character builds (same loadout). It really depends on how much duct taping you want...