PRELUDE NOTE: We are still waiting on a reply from Greg Farshtey about several hot-button topics discussed in the last topic, but we figured it’d be best to not delay this topic any more than it already has been. When Greg replies, we will update this main post with the answers he gave, as well as make a new post in this topic sharing the information.
- Keep the standard method: Hold all four polls for each Toa Hagah at once
- Stagger the polls by character (Open Kualus polls, announce the Kualus winner, open Pouks polls, etc.). This option WILL have lightning-round poll durations (2 days for prelim, semifinal, and finals)
- Mandate each creator design their Hagah as a “set” and enter all four at once for the sake of team coherence. Voting would, as a result, not be character-by-character but rather the full set of Hagah entered by the creator. Entries that enter less than four characters will be disqualified.
Alright fellas, so here’s the deal. We’re going to have ONE FINAL TOPIC before we get these things up and running; some serious questions worth contemplating were raised in the prior topic, and we felt like they deserved a few surveys to gauge feedback on.
KEY WORD: “survey.” Not “binding poll.” I put that here because ultimately we’re going to make the decision we feel is best for the contests to run efficiently, but I want to gauge feedback to see how much certain things matter to people.
FOR CLARITY ON EACH POINT:
On the matter of the first subject, in the prior topic, @ToaKebaka made an appeal to mandate that the final artist must not be allowed to change the mask used in the initial design, so as to preserve the creative vision of the original MoCist/artist. In his own words:
He elaborates further:
Generally speaking, I agree with this perspective. Our idea was that we wanted the final artist to have a role in the creative process by being able to contribute their own unique mask designs, and I still agree with that idea. However, I also see the merit in respecting the original creative vision of the character design. That being the case, we present this compromise: Allow for the creator to dictate whether they’re okay with allowing their mask to be changed or not. We will mandate that the creator make a statement in the topic as to whether the mask may be changed in the final design, which will be logged in the entry list. This statement will also be included in the character polls, so voters will know what they’ll be voting for mask-wise. We believe this is the best middle-ground to respect creativity on both sides, and we’re curious to hear your feedback on the matter.
This would also allow for masks that were on our “ban-list” to be used as placeholder masks in MoCs, with the caveat that they MUST be changed in the final version. This should help alleviate some concerns people were having about build restrictions based on mask availability in certain colors.
Now, for the main event…
In the closing day of the last topic, @Hazash wrote up a large post regarding the notion of Hagah uniformity. His full post can be found here, but the summary is basically that he feels by allowing voting on all four characters at once, we run the risk of inadvertently voting in Hagah designs that function well independently of each other, but have potentially poor team cohesion. This is something we’ve considered, but ultimately feel like cannot be fully controlled. Even if we implement any of these solutions, there’s no guarantee that full team cohesion will be voted on. Even more, what exactly team cohesion means is different for each person. Certain people care more about certain elements of design parity than others, and I don’t think a future exists where we please everybody 100%. That being the case, we do have two proposals as a direct result of Hazash’s post (which I would heavily encourage you all to read).
Option 1: Stagger voting on a character-by-character basis. For instance, we could open the Kualus preliminary polls, have them run for their allotted duration. Then, we would open the Kualus semifinals, and do the same. Finally, we’d open the Kualus finals, announce the winner, and THEN open the Pouks preliminary polls. This way, the voting preference of the community could be altered based on how the designs are shaping up on a character-by-character basis. However, this method is not perfect, as there still is a risk of parity not being achieved in the end (as I already mentioned). Also, this would theoretically drag out the contest voting for… an extremely long amount of time. Our solution for this would be to have LIGHTNING-ROUND voting, with each round of polling only lasting for about two days. We know this element may be controversial, but I feel like it would be important in this context to keep things moving along smoothly. In this hypothetical, the full voting process for each character would last about a week, culminating in a month to determine the designs for the four Toa Hagah.
OPTION 2: Mandate all four Toa Hagah be designed and entered as a unit for the sake of team cohesion. Currently, we allow for people to enter an individual character or all four, depending on their preference. However, if we opted to go this route, the Hagah would be designed as a set, and voters could elect to choose the designs with the most cohesion between themselves. The obvious negatives to this being that people would be forced to build four MoCs rather than one, and there would be no option to vote on a character-by-character basis: you would have to vote for each Hagah as a full set.
These are the only options we’re willing to consider here. We recognize it’s a difficult problem to solve, but those are the best methods to potentially alleviate this problem if it’s something people actually care that much about having alleviated; personally, I could go either way. I get the irritation having dissimilar Hagah could cause, but as there’s nothing lore-breaking about it, I could just get used to it if that’s how it shakes out. We’re not willing to consider things like allowing the final group artist to make sweeping changes to bring the characters in line, because at that point, it violates the prior concern about maintaining the creative freedom of the original designer.
I’d love to know your thoughts on these issues! Please feel free to share them and discuss all this stuff in as much detail as you want, and remember, we’ll update the main post and give another update when Greg gets back to us!