Concerning the tied election (user search)
       |           

Welcome, Guest. Please login or register.
Did you miss your activation email?
June 10, 2024, 08:45:13 AM
News: Election Simulator 2.0 Released. Senate/Gubernatorial maps, proportional electoral votes, and more - Read more

  Talk Elections
  Atlas Fantasy Elections
  Atlas Fantasy Elections (Moderators: Southern Senator North Carolina Yankee, Lumine)
  Concerning the tied election (search mode)
Pages: [1]
Author Topic: Concerning the tied election  (Read 1654 times)
Southern Senator North Carolina Yankee
North Carolina Yankee
Moderator
Atlas Institution
*****
Posts: 54,118
United States


« on: October 24, 2016, 03:12:39 AM »

This has to be the most incredible presidential election ever.

First you have TM dropping out.

The Federalists scrape up a candidate at the last minute, stuffing in Yankee.

Then it comes to a tie.

You left out the part where I got injured at work and had to visit the ER just four days after getting in and two days before Hurricane Matthew knocked out my internet for five days and nearly flooded us out.
Logged
Southern Senator North Carolina Yankee
North Carolina Yankee
Moderator
Atlas Institution
*****
Posts: 54,118
United States


« Reply #1 on: October 24, 2016, 07:55:27 PM »

There were three tickets being voted on. Unless the second preferences of the third ticket split perfectly, I don't understand why everyone is freaking about a tie.
I think the issue was that in certain elections in the past, if it's tied then a tie-break has been to count how many Yankee voters put Blair as a preference and vice versa. The most second preferences at this stage would win the election.

The problem there people will just stop using preferences unless they are voting for third party candidate. They will mark their candidate with an X. This actually happened in a LG race in the South in Feb 2010 under a cumulative preference system, Deldem and TB75 were running against each other and tb75 won literally because tb75's remaining voters only preferenced him. This will produce a very dysfunctional fall back system for a tie and both parties will be discouraging second preferencing of the other candidate.


The best way is the way that it was done in June 2009. Lief had 1 more first preference than PiT. GPorter was eliminated and his 1 vote went to PiT, producing a tie in the second count. Lief was declared the winner because he had the most first preferences.

This is the way that ties have historically been broken in the past in Atlasia

MasterJedi that same election was reelected to Midwest Senate in a similar fashion. He got 8 first preference votes I think and the final count produced a single other candidate with 8 votes, Jedi was declared the winner again because he had more first preferences.

There were other examples I am sure.

The only instance of a runoff being necessary should be when you have a tie in first preferences, and the elimination of the other candidates results in the votes splitting evenly, preserving the tie. You cannot fall back on first preferences in that case, so a runoff makes sense.

I don't like the idea of the House or Senate getting to make the decision because they will always select the majority party's candidate not who the people expressed the most support for.

Logged
Southern Senator North Carolina Yankee
North Carolina Yankee
Moderator
Atlas Institution
*****
Posts: 54,118
United States


« Reply #2 on: October 24, 2016, 08:32:47 PM »

The most first preference was the tiebreaker (and most people probably thought that) for most of my time in Atlasia but one day Bacon King I believe showed the text of a law, proving we operated under a false presumption.

I don't like the first preference being the tiebreaker because it discourages voting for someone who is not considered a contender for the win. Like if you vote for a small party candidate you end up hurting the chances of your second chance candidate.

I think in one Senate election I did not even vote for myself because I was wasting my vote on myself (we operated probably falsely under first preference as tiebreaker), my second preference vote was worth less to this candidate than if I first preference the person.

The Northeast regional Senate race was sometimes very close and one time I even asked permission of another declared candidate to run because I didn't want to spoil his chances in case it was a tie and I got a few votes that would maybe transfer to that candidate as second preference. Being on the ballot can be a disadvantage for another candidate if the result is a tie.

Using first preference as tiebreaker (even if it was not legally correct) can cause worries to voter and candidate. 

No system is going to be perfect. All I am saying is that if people want to avoid presidential runoffs as much as possible, it is the least bad option.
Logged
Southern Senator North Carolina Yankee
North Carolina Yankee
Moderator
Atlas Institution
*****
Posts: 54,118
United States


« Reply #3 on: October 24, 2016, 09:04:53 PM »

There were three tickets being voted on. Unless the second preferences of the third ticket split perfectly, I don't understand why everyone is freaking about a tie.
I think the issue was that in certain elections in the past, if it's tied then a tie-break has been to count how many Yankee voters put Blair as a preference and vice versa. The most second preferences at this stage would win the election.

The problem there people will just stop using preferences unless they are voting for third party candidate. They will mark their candidate with an X. This actually happened in a LG race in the South in Feb 2010 under a cumulative preference system, Deldem and TB75 were running against each other and tb75 won literally because tb75's remaining voters only preferenced him. This will produce a very dysfunctional fall back system for a tie and both parties will be discouraging second preferencing of the other candidate.


The best way is the way that it was done in June 2009. Lief had 1 more first preference than PiT. GPorter was eliminated and his 1 vote went to PiT, producing a tie in the second count. Lief was declared the winner because he had the most first preferences.

This is the way that ties have historically been broken in the past in Atlasia

MasterJedi that same election was reelected to Midwest Senate in a similar fashion. He got 8 first preference votes I think and the final count produced a single other candidate with 8 votes, Jedi was declared the winner again because he had more first preferences.

There were other examples I am sure.

The only instance of a runoff being necessary should be when you have a tie in first preferences, and the elimination of the other candidates results in the votes splitting evenly, preserving the tie. You cannot fall back on first preferences in that case, so a runoff makes sense.

I don't like the idea of the House or Senate getting to make the decision because they will always select the majority party's candidate not who the people expressed the most support for.



Spoiler effect...

Save for the run that Poirot mentioned in the NE from July 2013 until Oct 2014, 1 vote elections and ties have been sporadic and therefore such a spoiler effect induced in that process is rather minimal.

Even so, it is more solid in that at the very least you can count on it to produce a candidate, whereas relying on most second preferences risks as I said a race to the bottom as I described above.
Logged
Southern Senator North Carolina Yankee
North Carolina Yankee
Moderator
Atlas Institution
*****
Posts: 54,118
United States


« Reply #4 on: October 25, 2016, 07:47:34 PM »

The right thing to do, like it or not, is to follow the American 12th Amendment.

You do realize Atlasian law is not a copied U.S. law?


I'm quite aware of that. I was just trying to make a suggestion on addressing the situation.

The discussion is academic at this point, regarding future instances of this occurring.
Logged
Pages: [1]  
Jump to:  


Login with username, password and session length

Terms of Service - DMCA Agent and Policy - Privacy Policy and Cookies

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines

Page created in 0.026 seconds with 11 queries.