1.7.8

January 10, 2017

• Fix issue of conflicting thread accesses.

1.7.7

January 10, 2017

• Fix issue with UI jank for tallies that take a long time to process.

1.7.6

December 9, 2016

• Fix issue with handling rank voting that votes for the same option multiple times.

1.7.5

November 22, 2016

• Add a task filter option under Quest Options. Task filters may be set so that only vote entries that match the specified tasks are tallied. This allows tallying of votes that cross normal tally boundaries, such as a special vote option that was added after normal voting started, and continues after the next update.
• Extended vote trimming has been extended so that it can trim to just the first sentence of the vote line. The initial trimming method (trim til you reach a dash or colon separator, as long as it falls within certain boundaries) still applies. The sentence trimming can trim down to a sentence that takes up to one half of the entire vote line.
• Tally adjusted to be able to handle stickied posts properly, without causing duplicated votes or excluding votes.
• Bypass bug that led to corrupted parsing of a post. If a post contains BBCode tables or tabbed data of a certain complexity, the HTML library fails to parse it correctly, and the post can't be processed correctly. Such posts will now be skipped instead of causing the entire parse to fail.

1.7.4

June 22, 2016

• Revised algorithms to use for ranked vote tallying.

A bunch of research and testing was done through over a dozen different methodologies. Settled on Ranked Instant Runoff as the standard default, while also adding in the ability to cross-check the results against a simple scoring method (Wilson), a Condorcet method (Schulze), and an improved version of the old Coombs' method (Baldwin).

The type of algorithm to use can be changed under Global Options. However this value will not be saved to the config, as it's not desirable to allow different people to default to different tallying methods without explicitly deciding to do so.

There will always be arguments against the currently chosen default. Every voting method has multiple, sometimes extremely problematic issues. The one that was chosen seemed to balance out the best properties of those available, for the context of quest voting. It also allows a bit of flexibility in going to score voting (giving each option an independent score, rather than a sequential rank), should anyone want to experiment in that area.

Minor note: The program files are larger because they still contain all the unused algorithms. Those algorithms may be removed entirely at a later time, but are left in for now in order to be easy to bring back into play if further testing is needed.

1.7.3.2

Additional bug fix for theming. Was unable to identify last page in thread.

1.7.3.1

May 27, 2016

Bugfix for theme changes on Sufficient Velocity.

1.7.3

April 15, 2016

• A lot of back-end work to support mobile development.

1.7.2

April 6, 2016

• Bug fix: Editing quest names broke the combobox.

1.7.1

April 6, 2016

• Add option to allow forcing all proxy votes to be pinned.
• Fix bug in updating Manage Votes view that could break when adjusting vote tasks.
• Fix issue with identifying named votes that didn't have any content (particularly if the plan's details weren't written in the vote itself).
• Fix bugs in handling ranked voting that have crept in due to other code changes, as well as exceeding original specifications.
• Significant rewrite of code to make it safe for portability, in prep for making a mobile (Android, possibly iOS in the future) version.