|
|
| (3 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| '''Feedback''' is very helpful for making Warzone into a great game. Many of Warzone's features came from community '''feedback'''.
| | #REDIRECT [[Feature Request Forum]] |
| | |
| ==Your vote counts==
| |
| | |
| Warzone uses a [http://Warzone.uservoice.com UserVoice forum] to track feature additions or changes. There, players can vote on which features they'd most like to see added to Warzone.
| |
| | |
| Here's how it works: Everyone gets 10 votes. You can vote for features that you would like to see added to Warzone. So you can vote for 10 different features, or you can put multiple votes into a single feature if you really care about that feature. (Up to a max of 3 votes per feature)
| |
| | |
| You can take your votes back or move them around at any time. If a feature gets implemented, you also get your votes back and can put them towards something else.
| |
| | |
| '''IMPORTANT''': You '''must''' use the same e-mail address on UserVoice.com that you use on warzone.com. This is how the site knows you're the same person. If you use a different e-mail address, your votes will not be counted. This also means that if you change your Warzone e-mail address, you should also change your UserVoice e-mail.
| |
| | |
| ==Criteria for a new feature==
| |
| | |
| While it would be great to implement every feature suggested, this simply isn't possible. There's no magic number of votes that a feature needs to get accepted; the point of voting is to see which features are most in-demand. This is also important to avoid design-by-committee syndrome, since sometimes trying to please everyone ends up pleasing no one.
| |
| | |
| Features are typically judged based on these criteria:
| |
| | |
| * How good of a fit the feature is for Warzone's theme and direction.
| |
| * How much effort the feature takes to implement and maintain.
| |
| * How many votes the feature gets (i.e. how in-demand it is).
| |
| * Additionally, sometimes a feature can get implemented just because it happens to fall into an area of code that is being worked on for something else.
| |
| | |
| == UserVoice Multi-Ideas ==
| |
| | |
| A single idea on the UserVoice forum should generally contain a single idea/feature/improvement. Sometimes players create an idea that mentions multiple features. Doing this is not disallowed, however, it is risky, and may not get you what you want. A good example is the [https://Warzone.uservoice.com/forums/77051-Warzone-features/suggestions/1460793-tournament-overhaul Tournament Overhaul] idea, which calls for many features to be added to [[Tournaments|tornaments]].
| |
| | |
| The advantage of creating a single idea with multiple features is that it appears more attractive to other voters. If any one of your features appeals to a player, they're likely to vote on it, and therefore you're likely to get more votes.
| |
| | |
| The problem comes when one or some of the features is implemented, but not all. After this is done, there's three options:
| |
| | |
| # Leave the idea as it is on UserVoice.
| |
| # Edit the idea to remove the features implemented, leaving the ones not implemented.
| |
| # Close the idea as Complete, even though some parts of it weren't implemented. | |
| | |
| Number 1 clearly isn't a good option, as it would leave features up for voting that are completed.
| |
| | |
| Simply editing the idea isn't really appropriate either, since we don't know which of the features that the voters voted for. If most of them voted for the feature that was implemented, it doesn't make sense to carry their votes over to the rest of the features, as this would misrepresent their intentions and not give them their votes back.
| |
| | |
| Therefore, these ideas will just be closed as completed if any part of them is implemented. After this is done, everyone who voted for them will get their votes back. If the voters still desire a part of the idea that was not implemented, they can create a new idea specific to that part, and put their freshly acquired votes into that one one.
| |
| | |
| == UserVoice and Mods ==
| |
| | |
| Sometimes, people submit ideas to the UserVoice forum that can be implemented with Warzone's [[mod]] framework. This section outlines guideline for whether or not your idea belongs on UserVoice:
| |
| | |
| First, if your idea ''cannot'' be implemented using the mod framework, then it's OK to submit to it UserVoice. You can either word it as a normal feature, or word it as an idea to add support to the mod framework.
| |
| | |
| If your idea ''can'' be implemented using the mod framework, next determine if a mod already exists to accomplish it. If a mod already exists, then it's OK to submit it to UserVoice as an idea to convert a mod into a built-in feature. Be sure to note in the description that your idea is to convert an existing mod into a built-in feature. Note that these type of ideas will only be considered if the mod is already pretty popular.
| |
| | |
| If your idea can be implemented using the mod framework, but no mod exists yet, you should ''not'' submit it as an idea to UserVoice. The next step in getting your idea to become reality is to get it created as a mod. UserVoice is not the appropriate place to pitch to mod developers, as UserVoice is aimed at pitching your idea to the Warzone creators. Instead, if you can't create the mod yourself or need help doing so, try the Warzone Programming forum.
| |
| | |
| [[Category:Warzone]] | |