Announcement

Collapse

Ateam Forums Closing [UPDATE]

The forums will be closing at the end of April. However, we may have an option for backing up some content.

Details are in this thread.
See more
See less

Differentiated advancement

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Differentiated advancement

    Sorry for the awful title. I'm suggesting an idea for future rings that rings wherein players must choose between alternate abilities.

    Imagine the rings as they exist now, except once the top ability is learned, the player must choose between the slots to the right or left. After choosing the next item on both sides becomes available to learn. The player must again choose A or B, until reaching the bottom of the ring, where once again there is a single choice. Reaching the bottom of the 6th ring is all that's required for advancement to the 7th ring.

    Perhaps since each player only learns half of the abilities, make the rings larger. Each layer could be a choice between, say, an attack or a buff. Maybe a choice between a passive to increase class advantage or a passive to increase class defiance. This way each character can be a bit unique while still maintaining viability.

    Instead of locking skills that aren't learned, keep them available for half proficiency. If the A skill was learned for 6k prof, the player could go back and learn the B skill for 3k if they decided the A side didn't fit their build. At that point the A skill becomes unavailable again but can be bought back for another 3k
    Last edited by HotMessExpress; 03-02-2017, 05:33 AM.
    Hot Mess Express 2086796674


    #2
    I was going to suggest something similar: Class Branching. Your idea seems less regretful tho, since you can go back. With branching, you'd have to choose a branch and leave the other behind.

    Comment


    • HotMessExpress
      HotMessExpress commented
      Editing a comment
      One of the advertised features of the game is that you aren't locked in to one class. I think a rigid tree system would not be viewed favorably by the devs

    #3
    I really like this idea!

    Comment


      #4
      https://forum.a-tm.co.jp/forum/uniso...branch-classes

      Something like this?

      Comment

      Working...
      X