Recently, I shared a poll. When I checked how the poll was going, I realised that one user had kept on voting on the same option, massively disrupting the results (Check the data log- I've reset it now to what it's meant to be). I've tried my best to reduce repeated voting, scripting it so that users must press the flag again to vote a second time. Of course, there is a way to prevent this entirely, by converting user's names to numbers and so on… I'll implement that in my next project but should I have to? And would new scratchers know how to?

But I was wondering if there's anything that I can do, such as reporting the user. I see this as a clear attempt to mess up my project that I spent a very long time on and lots of new scratchers won't know how to fix this problem.

Here's the project, there's a secret in that if you press the F key, it will show the results without having to cast your own vote.

http://scratch.mit.edu/projects/11877781/

Once we have cloud lists (which I still think is in a while), you can simply make a list of who's voted. In the meantime, the best option is to make an encoder. It's kind of difficult, but it works reasonably well.

How about you slow down the repeated voting by having this:

when Coca Cola clicked
if <voted? = 0>
change Coke Votes by 1
change voted? by 1
else
You already voted
end elseif

when Pepsi clicked
if <voted? = 0>
change Pepsi Votes by 1
change voted? by 1
else
You already voted
end elseif

Set “voted?” to 0 before you leave the editor, and that's it. Don't set it to 0 when green flag clicked.

ProdigyZeta7 wrote:

How about you slow down the repeated voting by having this:

when Coca Cola clicked
if <voted? = 0>
change Coke Votes by 1
change voted? by 1
else
You already voted
end elseif

when Pepsi clicked
if <voted? = 0>
change Pepsi Votes by 1
change voted? by 1
else
You already voted
end elseif

Set “voted?” to 0 before you leave the editor, and that's it. Don't set it to 0 when green flag clicked.

Good idea, thanks. Although if they REALLY wanted to mess it up they could refresh the page but I like your method

PhirripSyrrip wrote:

Recently, I shared a poll. When I checked how the poll was going, I realised that one user had kept on voting on the same option, massively disrupting the results (Check the data log- I've reset it now to what it's meant to be). I've tried my best to reduce repeated voting, scripting it so that users must press the flag again to vote a second time. Of course, there is a way to prevent this entirely, by converting user's names to numbers and so on… I'll implement that in my next project but should I have to? And would new scratchers know how to?

But I was wondering if there's anything that I can do, such as reporting the user. I see this as a clear attempt to mess up my project that I spent a very long time on and lots of new scratchers won't know how to fix this problem.

Here's the project, there's a secret in that if you press the F key, it will show the results without having to cast your own vote.

http://scratch.mit.edu/projects/11877781/

You can add a script saying:
if not<<(username) = [user]>>{
say[You Can't Vote!]
else
change[vote] by (1)
}

BigBlueBlock wrote:

PhirripSyrrip wrote:

Recently, I shared a poll. When I checked how the poll was going, I realised that one user had kept on voting on the same option, massively disrupting the results (Check the data log- I've reset it now to what it's meant to be). I've tried my best to reduce repeated voting, scripting it so that users must press the flag again to vote a second time. Of course, there is a way to prevent this entirely, by converting user's names to numbers and so on… I'll implement that in my next project but should I have to? And would new scratchers know how to?

But I was wondering if there's anything that I can do, such as reporting the user. I see this as a clear attempt to mess up my project that I spent a very long time on and lots of new scratchers won't know how to fix this problem.

Here's the project, there's a secret in that if you press the F key, it will show the results without having to cast your own vote.

http://scratch.mit.edu/projects/11877781/

You can add a script saying:
if not<<(username) = [user]>>{
say[You Can't Vote!]
else
change[vote] by (1)
}

Fine. Have a look now.

PhirripSyrrip wrote:

BigBlueBlock wrote:

PhirripSyrrip wrote:

Recently, I shared a poll. When I checked how the poll was going, I realised that one user had kept on voting on the same option, massively disrupting the results (Check the data log- I've reset it now to what it's meant to be). I've tried my best to reduce repeated voting, scripting it so that users must press the flag again to vote a second time. Of course, there is a way to prevent this entirely, by converting user's names to numbers and so on… I'll implement that in my next project but should I have to? And would new scratchers know how to?

But I was wondering if there's anything that I can do, such as reporting the user. I see this as a clear attempt to mess up my project that I spent a very long time on and lots of new scratchers won't know how to fix this problem.

Here's the project, there's a secret in that if you press the F key, it will show the results without having to cast your own vote.

http://scratch.mit.edu/projects/11877781/

You can add a script saying:
if not<<(username) = [user]>>{
say[You Can't Vote!]
else
change[vote] by (1)
}

Fine. Have a look now.

It won't let me vote.

Ugh, it seems almost everyone is voting three or more times. I won't name names here, but check the log.

I think you'll have to make an encoder
or just blacklist almost everyone

scratchisthebest wrote:

Ugh, it seems almost everyone is voting three or more times. I won't name names here, but check the log.

I think you'll have to make an encoder
or just blacklist almost everyone

Yes, I'll do that in the next poll. I think I'll let people vote for more than one option if they can't make their mind up but I won't let people vote more than once on the same answer.

Its very annoying. Someone also did that on mine.
What I did is if the persons username equal to the username of the person who voted multiple times it hide all the sprites so they can't vote.

when username clicks the button, check if he had voted(see next step) add it to a local list, if username isnt in local list, add him then add 1 vote, if username is already on the list, tell him YOU ALREADY VOTED <3

ProdigyZeta7 wrote:

How about you slow down the repeated voting by having this:

when Coca Cola clicked
if <voted? = 0>
change Coke Votes by 1
change voted? by 1
else
You already voted
end elseif

when Pepsi clicked
if <voted? = 0>
change Pepsi Votes by 1
change voted? by 1
else
You already voted
end elseif

Set “voted?” to 0 before you leave the editor, and that's it. Don't set it to 0 when green flag clicked.

This would only work if they were trying to repeatedly vote without refreshing the page, eventually someone would figure it out and mess it up again.

But, otherwise, I like your method.

You could try adding the person's username as a (cloud?) variable, and saying:
If username = or , etc.
Switch background to “You have already voted..”

Or:
Define NoVotingTwice
If username equals (variable)
End All Scripts


You'd have to create a Variable every time the gf was clicked, set it to the username, and add it to the Define NoVotingTwice script…

JAVAProgramming wrote:

You could try adding the person's username as a (cloud?) variable, and saying:
If username = or , etc.
Switch background to “You have already voted..”

Or:
Define NoVotingTwice
If username equals (variable)
End All Scripts


You'd have to create a Variable every time the gf was clicked, set it to the username, and add it to the Define NoVotingTwice script…

You know what'd help? Cloud Lists…

JAVAProgramming wrote:

JAVAProgramming wrote:

You could try adding the person's username as a (cloud?) variable, and saying:
If username = or , etc.
Switch background to “You have already voted..”

Or:
Define NoVotingTwice
If username equals (variable)
End All Scripts


You'd have to create a Variable every time the gf was clicked, set it to the username, and add it to the Define NoVotingTwice script…

You know what'd help? Cloud Lists…

Yes, I'm making a poll that should be shared later today that uses an encoder to basically create a cloud list. I'll let you know when it's done.