New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Campaign Summary: upgrade for Manage Departing Survivors #496

Closed
toconnell opened this Issue Mar 30, 2018 · 3 comments

Comments

Projects
None yet
1 participant
@toconnell
Owner

toconnell commented Mar 30, 2018

This hasn't been fundamentally enhanced or improved since it was first pushed as a feature over a year ago. It got a re-skin recently, but the underlying functionality and design are bad...and seem to be broken (see comment below).

This ticket is for the total refactor. The idea should be that it flows through a few menus, e.g. like this:

  1. set monster (before survivors are manageable)
  2. click to start aftermath
  3. set aftermath type (victory/defeat) in $scope
  4. departing survivor operations in the aftermath (xp, etc.), w/ hooks to API
  5. advance LY on return set it in $scope
  6. finalize return, push to API and re-init CS view
  • set monster should be "over" all-survivor controls until it's set
  • set monster should always be available (e.g. in case it changes during the hunt)
  • increment current LY
  • re-init view
@toconnell

This comment has been minimized.

Owner

toconnell commented Mar 30, 2018

User workflow from email:

Sometimes it's hard for me to 'flow' through a lantern year. For instance; last night we returned from lantern year five hunt/showdown (finished during previous game night). We did the Sense Memory and Armored Strangers stories per the timeline. But you actually tick the year (6) during this process. So now, we are all ready to go on what in my mind is hunt/showdown year 6 but that year is already checked off. So after checking off year 6, am I on hunt number 6 or hunt number 7? That part is hard for me to keep straight and I'm not sure the app shares any blame there!

But, here is my workflow;

  1. We return from a hunt.
  2. I go into the manage departing survivors and set the showdown type, quarry, and victory or defeat. (survivors are marked as returning)
  3. We do a settlement event.
  4. We do any story events.
  5. We update the deathcount.
  6. We update the timeline.
  7. We endeavor/build
  8. We select survivors and add them to 'departing survivors' for next hunt/showdown
  9. We do the hunt manually (not using app)
  10. We do the showdown
  11. We return from hunt.
  12. I go into the manage....

Somehow we seem to end up with more than four people marked at 'Returning Survivors' after step 1. It is ENTIRELY possible I didn't correctly return the survivors at some point and they never got marked 'returning'. Based on how you say things work, this could also explain a survivor who was supposed to miss the next fight being stuck in miss the next fight limbo because the 'next' fight never ended properly.

Timeline_Confusion.docx

@toconnell

This comment has been minimized.

Owner

toconnell commented Apr 8, 2018

OK, this is coming along:

dep_sur_wip_0

@toconnell

This comment has been minimized.

Owner

toconnell commented Apr 9, 2018

Alright, all the feature stuff is done and ready to ship. Plan now is to skin it for tablet and wide, cut a quick feature demo and push it out the airlock (i.e. move the current release to production).

@toconnell toconnell closed this Apr 9, 2018

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