NetTally - Vote tally program

So this is almost certainly something on my end, but I have no idea how to fix it after a cursory look over the the Wiki. I downloaded the updated NetTally today, and I promptly got the following error whenever I tried to run a tally:



I've tried it on multiple quest threads, and also tried previous versions with no joy forthcoming.

Help?

Edit: I think I understand now, it has to be related to the change to SV's threadmarks system. If I designate a post manually now, it works. If I go from last threadmark, it doesn't.
 
Last edited:
The tally program isn't remembering when I add new things.

I've run a tally on this thread twice today, and each time I've had to re-enter it as a new quest to tally.
The tally program simply doesn't appear to register its addition, so if I open a second window of the program it simply won't have it, and if I close one that I've added it too I'll need to re-add it to tally again later.
 
@Kinematics when you make a tally it gives you some data, such as
Vote Tally : Original - Fantasy - Forge of Destiny(Xianxia Quest) | Page 336 | Sufficient Velocity
However, the tally above was actually from #8386 to end of thread

I think it would be great if the tally included which post number it started on and ended on. (if end is 0, list the number of the last post actually counted)

This would help with clarity. Also, when making a new tally it would make it easier to find the right starting point (same as the last time) in case the starting point is not last threadmark
 
The tally program isn't remembering when I add new things.

I've run a tally on this thread twice today, and each time I've had to re-enter it as a new quest to tally.
The tally program simply doesn't appear to register its addition, so if I open a second window of the program it simply won't have it, and if I close one that I've added it too I'll need to re-add it to tally again later.
OK, I've checked running a tally on that thread, and it seems to remember the thread fine between runs of the program.

However, since you mention running multiple instances, I should note that it doesn't save quest config info until you close the program. If you open one instance, add the thread, and then open another instance without the first one being closed, the second instance will load up the same config that the first instance originally opened, which will not include the thread.

If you're opening multiple instances, and adding the thread to some of them, and then closing, you'll have to consider the order that that occurred. If you add to Instance 1, open Instance 2, close Instance 1, and close Instance 2, the final config save will be Instance 2, which will re-save the original config values.

I could rewrite things to update the config every time an update to the quests is made, rather than just at program close, but that gets rather complicated, and still has issues where things are going to end up failing simply because this is a difficult problem to solve. And that's also assuming that I'm guessing at the source of your problem correctly. It might also be an issue of not having permission to save your config info.

If this doesn't describe the issue you're having, can you check for a current error log in C:\ProgramData\NetTally ?
 
OK, I've checked running a tally on that thread, and it seems to remember the thread fine between runs of the program.

However, since you mention running multiple instances, I should note that it doesn't save quest config info until you close the program. If you open one instance, add the thread, and then open another instance without the first one being closed, the second instance will load up the same config that the first instance originally opened, which will not include the thread.

If you're opening multiple instances, and adding the thread to some of them, and then closing, you'll have to consider the order that that occurred. If you add to Instance 1, open Instance 2, close Instance 1, and close Instance 2, the final config save will be Instance 2, which will re-save the original config values.

I could rewrite things to update the config every time an update to the quests is made, rather than just at program close, but that gets rather complicated, and still has issues where things are going to end up failing simply because this is a difficult problem to solve. And that's also assuming that I'm guessing at the source of your problem correctly. It might also be an issue of not having permission to save your config info.

If this doesn't describe the issue you're having, can you check for a current error log in C:\ProgramData\NetTally ?
To clarify, what I mean is that I want the output to include the start and end post numbers.

Instead of
Tally Results said:
Vote Tally : Original - Fantasy - Forge of Destiny(Xianxia Quest) | Page 331 | Sufficient Velocity
##### NetTally 1.9.2
have
Tally Results said:
Vote Tally : Original - Fantasy - Forge of Destiny(Xianxia Quest) | Page 331 | Posts 8386 - 8711 | Sufficient Velocity
##### NetTally 1.9.2

while it is true that it saves the last selection if you select it from the list. The list is quite long and I find it easier to always just paste the thread address. which resets it.

Also, I was primarily interested in it for the sake of verifying tally posted by others.
So I can look at someone else's vote and go "ah, you made a mistake, you started at post X when it should have started at post Y due to moratorium on voting for discussion purposes / threadmarks issue"
 
Last edited:
To clarify, what I mean is that I want the output to include the start and end post numbers.
Yes, I was working on that separately. My response was to the issue LostDeviljho was having.

I'll be modifying the display slightly differently than your suggestion. The displayed title is actually literally the title of the html page that the tally starts on, and I won't try to figure out what that might be to edit it. I'll add the post numbers at the tail end of it instead.
 
Yes, I was working on that separately. My response was to the issue LostDeviljho was having.
oh sorry, my bad there
I'll be modifying the display slightly differently than your suggestion. The displayed title is actually literally the title of the html page that the tally starts on, and I won't try to figure out what that might be to edit it. I'll add the post numbers at the tail end of it instead.
cool, thanks
 
To clarify, what I mean is that I want the output to include the start and end post numbers.
OK, for the post numbers displayed, it's currently going to output the start and end posts after all filtering is done. So, for example:

#1: Threadmark
#2: Comment
#3: Vote 1
#4: Vote 2
#5: Vote 3
#6: Comment

If you tally that, it will indicate it tallied posts 3-5. If Vote 3 was filtered out for some reason, it will indicate it tallied posts 3-4. If Vote 2 was filtered out, it will indicate it tallied posts 3-5.

Getting it to note that it tallied posts 1-6 is actually a little difficult, because by the time I get this information, all filtering has already been completed. So post 1 was filtered because it was by the thread author, and the comments were filtered because they're not actually votes, etc. On the other hand, if you're wanting to check on moratoriums or the like, then you'd want the exact post number of the first valid vote anyway, so that's fine.

If there are no suggested modifications, I'll go with this.
 
It seems perfectly reasonable for a case of "count from last threadmark".
but what if you put in a specific number manually in the start post box?
wouldn't that number be available by just looking at the "starting post number" variable without even needing to load the thread?

Anyways, I think the above is perfectly fine for a vote that was "last threadmark to end of thread". at such a case it clearly indicates what posts were actually counted which is what you really want.

But I think if a specific number has been entered in the "start" post box instead of last threadmark than it should be displayed (as that indicates that for some reason last threadmark is unsuitable, so starting post is more important).
Showing that number directly rather than the number of the first actual vote posts would serve to clarify that the appropriate comment posts were examined by the program even if they contained no valid votes

Not sure about what to do with a number entered in the end box, since it could be larger than actually exists?
 
Last edited:
NetTally 1.9.3 (May 30, 2017) (Downloads)

* Add global option to include/exclude plans with 0 voters.
* Add info to the general output indicating the range of post numbers that were actually tallied in the vote.
* Fix: Remove 'unread' from the URL during automatic URL cleanup. Fixes issue with modification to certain forum behavior.
* Fix: Ensure spoiler labels are always inside quotes, to prevent corruption of output display.
* Leave vote counts that are used as part of compact spoiler labels in brackets, instead of changing to parentheses.
* Fix: Ensure renaming notification happens, so that the main dropdown list's names are up to date. Fixes issue with the default fake thread name remaining even after fixing the URL afterwards.
* When handling forums with multiple threadmark categories, properly extracts only the primary category for searching for the last threadmark.
 
I'm kinda curious to know which thread caused that issue to be found.

I can easily understand something like an image thread having pages that are over 1 MB in size, but I find it hard to imagine that a quest thread can reach that point without having some spam that never got cleaned up.
 
I'm kinda curious to know which thread caused that issue to be found.

I can easily understand something like an image thread having pages that are over 1 MB in size, but I find it hard to imagine that a quest thread can reach that point without having some spam that never got cleaned up.
Note: this is 1 MB of raw HTML; absolutely no images or other resources added to the basic page.

Anyway, this was on the first page of a quest, with all the character sheets and stuff, and apparently just the spell list alone was over 70k words (so about 420k of the 1 MB, not counting markup). Total page size was 1,178,079 bytes.

Thread is on QQ, so I can't link to it.
 
NetTally 1.9.5 (June 10, 2017) (Downloads)

* Fix: Tasks used for re-ordering were not always updated correctly after changing partitioning mode.
* Add: Allow explicit partitioning of vote blocks in the Manage Votes window, to split the vote into its constituent child lines (partitioned by block).
* Change: Posts filtered by number are moved up to the same tier as posts filtered by username, and are completely excluded from further processing, instead of allowing embedded plans to be processed.
* Change: Adjust compact mode so that if a parent line has all children line of only +1 depth, then all of those children are entered and accumulated for display, instead of only working if the parent only has one child line. Any children with greater than +1 depth trigger going back to the standard Plan <username> substitution line.
 
I could rewrite things to update the config every time an update to the quests is made, rather than just at program close, but that gets rather complicated, and still has issues where things are going to end up failing simply because this is a difficult problem to solve.
I happened to be re-reading this. I have neither used NetTally myself nor ever seen a screenshot of it. Handwaving the amount of programming work required for them, two thoughts:
  1. Could you add a "force save config"/"force (re)load config" type button somewhere? Then people who insist on running multiple instances could resync settings by hand.
  2. The usecase seems to be "have two NetTally windows open at once, doing different things". Could you add some sort of "one backend instance -- multiple frontend windows" functionality?
 
@Kinematics
So I just upgraded from version 1.7.4 to version 1.9.5, but I'm getting an error that I wasn't getting before. Found this out in response to a QM saying that their version wasn't working.

I've tested a variety of threads on both SV and SB, and can't find any others that cause this error.


Attempting to tally the following thread gives an error message saying "Invalid URI: Invalid port specified".
Digimon World: Infamy

The error happens both if I manually enter the post number of the last threadmark and if I use the "Try Last Threadmark" option. Version 1.7.4 works correctly as long as I manually enter the post number.

Edit:
And another user found that versions up to 1.8.1 tally that thread correctly, but everything newer than 1.8.1 fails.
 
Last edited:
@Kinematics
So I just upgraded from version 1.7.4 to version 1.9.5, but I'm getting an error that I wasn't getting before. Found this out in response to a QM saying that their version wasn't working.

I've tested a variety of threads on both SV and SB, and can't find any others that cause this error.


Attempting to tally the following thread gives an error message saying "Invalid URI: Invalid port specified".
Digimon World: Infamy

The error happens both if I manually enter the post number of the last threadmark and if I use the "Try Last Threadmark" option. Version 1.7.4 works correctly as long as I manually enter the post number.

Edit:
And another user found that versions up to 1.8.1 tally that thread correctly, but everything newer than 1.8.1 fails.
Hmm. OK, the error is when it tries to parse this image URL: "http://blob:http://imgur.com/a8d8f6a7-f5dc-419d-aa61-67863105d257".

And it comes from this post, at the point where the text starts with "His fist clenched and shaking in rage...". Just prior to that, you'll note an [IMG] placeholder. That's because said image reference is garbage.

1.8.2 introduced some slightly fancier handling of how it parses image URLs (unescapes percent-encoded URLs), and it looks like it didn't handle things properly when they broke. I'll have to fix that.
 
NetTally 1.9.7 (June 15, 2017) (Downloads)

* Fix: Certain ranked voting setups had the potential to generate blank results, which caused an exception to be thrown.
* New: NetTally will communicate changes to the quest list with other instances of NetTally running on the same computer.

The above changes apply to adding new quests, removing quests, and renaming quests. It will not carry over changes to a given quest's configuration (ie: the various filters, partitioning mode, start/end posts, etc) or any global options, since there's reasonable use cases where you want different instances of the program to be run with different configurations.

A future update may adjust that so that configuration changes are updated as long as the quest being changed is not the currently active quest, so that the changes will be retained regardless of the order in which the the program instances are closed.


@LostDeviljho and others, this should fix the issue of losing some changes when running multiple instances of the program.
 
NetTally 1.9.8 (June 26, 2017) (Downloads)

* Keep a record of user merges and task modifications, and apply those modifications on any subsequent tallies for a given quest run on the same partition mode.
* Modify options handling. All tally formatting options that were previously global are now per-quest.
* Fix: Ensure custom task ordering works for ranked votes.
* Fix: Update threadmark locating code again.

Recording and re-using user merges effectively auto-merges votes based on prior manual merges each time you run the tally. This includes assigning tasks manually. So, once you've done the merging once, you should generally not need to do it again on subsequent runs on the same quest. If you change partition modes, the prior partition mode merges will be remembered if you switch back.

Clearing the cache will reset the merge history. Tallying another quest will reset the merge history.
 
Last edited:
Idea: Have an option to auto-merge votes that have identical letter/numbers, with the most-voted among the set becoming the true vote.

The most common error is Incorrect spacing, but other non-basic text errors are also pretty common.

Probably don't want this to be the default, but it'd be nice for taking a look at something like, say, this
Vote Tally : Original - Paths of Civilization | Page 2476 | Sufficient Velocity [Posts: 61893-62638]
##### NetTally 1.9.8

[81] Red Banner Company - Northern Nomads


——————————————————————————————————————————————
Task: Divine

[61][Divine] Speak against it (-1 Religious Authority, potential trouble for heir)
[15][Divine] Speak up for the idea (+1 Religious Authority, other effects)
[5][Divine] Stay silent (+1 Religious Authority)
[3][Divine] Speak against it (-1 ReligiousAuthority, potential trouble for heir)
[1][Divine] Stay silent (+1 Religious Authority
[1][Divine] Speak up for the idea (+1 Religious Authority, other effects)


——————————————————————————————————————————————
Task: Main

[55][Main] Sacred Forest Renewal
[51][Main] Sacred Forest Renewal x2
[18][Main] Sacred Forest Renewal
[11][Main] Megaproject-Sacred Forest Renewal
[8][Main] Sacred Forest Renewal x2
[4][Main] Megaproject-Sacred Forest Renewal x2
[3][Main] Sacred Forest Renewalx2
[3][Main] Build Mills
[2][Main] Megaproject
[1][Main] New Settlement - Far Eastern Redhills
[1][Main] Megaproject x2
[1][Main] War Mission - Northern Nomads
[1][Main] Megaproject x2 (-4 Econ, -4 Mystic, -2 Art)
[1][Main] Restore Order


——————————————————————————————————————————————
Task: Secondary

[48][Secondary] War Mission-Northern Nomads
[14][Secondary] Change Policy - Balanced
[9][Secondary] Change Policy-Balanced
[9][Secondary] War Mission-Northern Nomads
[7][Secondary] Change Policy-Expansion
[4][Secondary] Change Policy-Balanced
[4][Secondary] Expand Economy
[3][Secondary] Change Policy-Megaproject Support
[2][Secondary] Change Policy - Megaproject Support
[2][Secondary] War Mission - Northern Nomads
[1][Secondary] War Mission - Nomads
[1][Secondary] Survey Lands
[1][Secondary] Study Forests
[1][Secondary] Policy Change - Expansion
[1][Secondary] Change Policy - Expansion
[1][Secondary] New Settlement - Far Eastern Redhills
[1][Secondary] War Mission: Northern Nomads
[1][Secondary] Change Policy-Megaproject Support
[1][Secondary] Study Forests
[1][Secondary] Study Forest


——————————————————————————————————————————————
Task: Kick

[2][Kick] Sacred Forest Renewal


——————————————————————————————————————————————
Task: Sec

[1][Sec] Policy – Restoration

Total No. of Voters: 99
Where it'd be like half as long if you wiped out everything that was identical after a s/[^a-zA-Z0-9]//g filter. Note that some of these are even exactly identical but looking in the Manage Votes it seems some had a space after the task and some didn't.
 
Back
Top