Maybe there could be a special type of list, specially for forums. These would automatically tell us which user is writing
Offline
Pecola1 wrote:
Bklecka wrote:
Pecola1 wrote:
i would agree, but seeing that it could be used to ban someone from playing a game, this could be used for cyber bullying.
look inside button.
why not put in a window whenever this block is used!
it would ask "this project would like to use the (username) block will you allow it?"that would be good... but someone can still make it so if the username is '' then it will not play the game and say you must allow the block.
then use look inside and remove
if username = [guy you hate here]
stop all
else
play game
Offline
RedRocker227 wrote:
Wes64 wrote:
Pecola1 wrote:
i would agree, but seeing that it could be used to ban someone from playing a game, this could be used for cyber bullying.
That is true. What if we prevented the (username) block from being used in an operator? This would totally stop any locking-out.
You could just set a regular variable to the value of the (username) block, and then use the variable in operators, though.
Yes. So when a variable is set to the (username), that variable should also be prevented from being used in operators. My idea is that there could be a sort of hidden attribute on the username block, like this.
(username) = #Wes64
so if (var) is set to (username), (var) = #Wes64
and if (username) is added to a list, (item of list) = #Wes64
And if any variable contains the #, it is disallowed from being used in () = () , () contains () , etc
Additionally, we could have a prompt like with audio-using projects.
The project could say "This project wants your username, allow or disallow?"
Disallowing would prevent the user from participating in entering cloud data so anonymous trolls would be stopped.
Last edited by Wes64 (2012-06-11 18:43:35)
Offline
MathWizz wrote:
I just love the drama here. Just report the project/user if it is screwing with you.
I was just about to say that, if its a bad project then its a bad project so you can report it. (trollin = bad)
Pros n cons:
Pros:
1.Highscore lists and things could show the actual username of a user, to keep someone from making poor paddle2see look bad in the highscore list below:
Pecola1 = 1809577 MathWizz = 88530 Paddle2See = 0
2. You could tell if the user was a guest, and therefore could give the guest more instructions if needed
3. Would allow a ban system, if someone said something bad, or trolled, the user could be banned from that game.
Cons:
1. Someone could make a project which would not allow either guests, or certain users from playing the game, simply because the maker of the game wants to troll 'em. If the project was reported it could still take time until the game was removed, and if it was removed, then the user who was banned would not be able to play it. However maybe the admins/mods could edit the project...?
Overall I say the pros WAAAY outweigh the cons.
Offline
Pecola1 wrote:
However maybe the admins/mods could edit the project...?
That's a good idea, actually. But it would be better to just remove the project, you know, to teach a lesson. Also, if mods were given the privilege to edit someone else's projects, where would we draw the line? Just a personal preference but I wouldn't want anyone in my projects making changes, it just seems a bit invasive.
Offline