![]() ![]() I feel like, with bugs as they are, a back and forth system would let every Amara have Remnant all the time because you could spec to it, back out, and it would have activated it, but forgot to close it. ReSpeccing otherwise means creating a system that goes forward and backwards, keeps and eye out for errors, and also remembers to wipe out the abilities you wipe out. ReSpeccing with a clean slate system means you only have to code a wipe button, and you’ve already got the Spend Point System in place to begin with. I think it’s just an easier and less messy experience on development and user end to work with a clean slate system. I have to click all my points backwards down the tree to Grizzled, then climb back up, effectively doubling the amount of work it would have taken to wipe it clean and redo it. ![]() Now, let’s say I finally got down to Moze’s splash for cool down, and want to remove Grizzled. So maybe they could let you only remove from the furthest points. They’d have to code hard locks to stop you from clearing a skill out from tier one that affects how you make it through the rest of the tree. Things could get messy if they let you change a point from anywhere to anywhere at any time or even just on Sanctuary. I think it’s probably the way the trees fill up and allow access to new things. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |