You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The running joke in the story is that you are consuming the idols. While actually consuming the idols re: stats would be bad, we should offer more than +1 per idol for the effort.
Thinking out loud, the # of points that are randomly assigned could be 'the stage of the story' x 'the number of times you've beaten the story+1'. So 5 points for chapter 5, 15 points for chapter 5 second playthrough, etc.
The text was updated successfully, but these errors were encountered:
I still think we should. It'd take a while for bonuses to catch up at the rate that enemies are getting stronger by (currently 50 points to each stat per chapter for the bosses, versus 1 random point for you per idol).
Feeding is always going to be the best way to get stats, but 1 point is pretty meaningless. When the agency is in, even the worst graduation will give you more than that. Perhaps we make the bonus you receive off a win tied to something you can upgrade in the agency?
There is some balancing to take into account, as you say. Testing required I think.
colons
changed the title
Beating the story mode units should give you larger bonuses
Beating the story mode units should give the idols who fight them bonuses
Apr 1, 2018
colons
changed the title
Beating the story mode units should give the idols who fight them bonuses
Beating the story mode units should give you larger bonuses
Apr 1, 2018
The running joke in the story is that you are consuming the idols. While actually consuming the idols re: stats would be bad, we should offer more than +1 per idol for the effort.
Thinking out loud, the # of points that are randomly assigned could be 'the stage of the story' x 'the number of times you've beaten the story+1'. So 5 points for chapter 5, 15 points for chapter 5 second playthrough, etc.
The text was updated successfully, but these errors were encountered: