{"id":449,"date":"2014-11-09T17:58:59","date_gmt":"2014-11-10T00:58:59","guid":{"rendered":"https:\/\/www.crabattack.org\/blog\/hawk\/?p=449"},"modified":"2014-11-09T17:59:58","modified_gmt":"2014-11-10T00:59:58","slug":"november-9th-2014","status":"publish","type":"post","link":"https:\/\/www.crabattack.org\/blog\/hawk\/november-9th-2014\/","title":{"rendered":"November 9th, 2014"},"content":{"rendered":"<p>This week saw the completion of co-op class design. The design process was\u00a0a little more arduous than last time\u00a0due to single classes requiring a different touch from triple classing. There&#8217;s not a whole lot to talk about with the design process itself, though. The focus was to give each class an advantage in certain situations and to have more synergy with\u00a0certain other classes. Not much mind was paid towards balancing absolute power levels between them just yet, right now I&#8217;m just trying to create interesting play styles. Balance will come later.<\/p>\n<p>The other big issue of the week was balancing party movement. The old system was that, when partied, each player\u00a0in the party could move on\u00a0their turn and bring party members with them. The end result is great for pacing (everyone still gets a turn), but terrible for balance. In PVP this merely resulted in parties\u00a0being hugely advantaged over solo players (being able to clear as many monster dens in a turn as their number of party members while having a battle advantage to boot), but in co-op it&#8217;s an even bigger problem. I want to have co-op objectives that require parties to split up in order to be more efficient with timers. If a full party has a\u00a0near identical move rate combined with extra combat efficiency, then there&#8217;s no real reason for them to split up.<\/p>\n<p>The most obvious solution to this problem was to cycle through each player in a party each\u00a0round to decide who gets to move the party for the round. This was pretty unintuitive and also created issues (if player C leaves the party after A,B have\u00a0already done their turn for the round, then the party ends up unable to move). Crazier solutions were considered like merging parties into a single turn taker. Lots of overhead.<\/p>\n<p>I eventually settled on a much simpler solution. When moving in a party, every player has their stamina drained from the movement. To\u00a0give every player an\u00a0opportunity to move the party, I\u00a0also added shuffling the turn order each round based on agility (more perfectly even ideas were considered like cycling the first turn player ie (A-&gt;B-&gt;C-&gt;D)-&gt;(B-&gt;C-&gt;D-&gt;A) but this results in one player having to wait 6 turns for their next turn every round which is terrible pacing). This actually has some pretty cool implications for PVP since it\u00a0allows players to actually have a chance to catch up to other players that they&#8217;re chasing. As a last necessary tweak, I also made it so players can&#8217;t move after having initiated combat in a round (since parties were still technically capable of multiple battles in a round, albeit\u00a0not as much as they had before).<\/p>\n<p>This system still isn&#8217;t totally there since it\u00a0creates many turns where party members\u00a0have nothing to do but end their turn (which is especially terrible in single player). In a truly ideal world there will be an option to access other party member&#8217;s\u00a0menus during the party leader&#8217;s turn,\u00a0as well as leave a party even when it&#8217;s not your turn in order to avoid these &#8220;pointless&#8221; turns completely. But I want to get a feel for how a more constricted party plays before I clean it up.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>This week saw the completion of co-op class design. The design process was\u00a0a little more arduous than last time\u00a0due to single classes requiring a different touch from triple classing. There&#8217;s not a whole lot to talk about with the design process itself, though. The focus was to give each class an advantage in certain situations&#8230; <a href=\"https:\/\/www.crabattack.org\/blog\/hawk\/november-9th-2014\/\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">November 9th, 2014<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-449","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.crabattack.org\/blog\/hawk\/wp-json\/wp\/v2\/posts\/449","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.crabattack.org\/blog\/hawk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.crabattack.org\/blog\/hawk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.crabattack.org\/blog\/hawk\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.crabattack.org\/blog\/hawk\/wp-json\/wp\/v2\/comments?post=449"}],"version-history":[{"count":3,"href":"https:\/\/www.crabattack.org\/blog\/hawk\/wp-json\/wp\/v2\/posts\/449\/revisions"}],"predecessor-version":[{"id":452,"href":"https:\/\/www.crabattack.org\/blog\/hawk\/wp-json\/wp\/v2\/posts\/449\/revisions\/452"}],"wp:attachment":[{"href":"https:\/\/www.crabattack.org\/blog\/hawk\/wp-json\/wp\/v2\/media?parent=449"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.crabattack.org\/blog\/hawk\/wp-json\/wp\/v2\/categories?post=449"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.crabattack.org\/blog\/hawk\/wp-json\/wp\/v2\/tags?post=449"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}