Age Block?
-
The age block would be great for horror games, since you could restrict younger audiences and forward it to older audiences. It would pick up the age that you provided on your profile, and then to do the calculations, you can do:
Current Year and Month - Users Year and Month provided
đź‘‹
-
The age block would be great for horror games, since you could restrict younger audiences and forward it to older audiences. It would pick up the age that you provided on your profile, and then to do the calculations, you can do:
Current Year and Month - Users Year and Month provided
@jd131111 People can very well just lie about their age, as I usually do with sites I’m not familiar with or don’t trust.
-
The age block would be great for horror games, since you could restrict younger audiences and forward it to older audiences. It would pick up the age that you provided on your profile, and then to do the calculations, you can do:
Current Year and Month - Users Year and Month provided
We try to avoid exposing information about a user’s birth year/month to other users/programs.
Maybe we can allow the author of a project to assign a rating to their project, so our system can automatically hide the “horror” level projects from young users?
-
We try to avoid exposing information about a user’s birth year/month to other users/programs.
Maybe we can allow the author of a project to assign a rating to their project, so our system can automatically hide the “horror” level projects from young users?
@info-creaticode How about instead of exposing the age directly, instead a block that returns the maturity rating based on the user’s age. For example, a block that might return G, PG, or M, based on the user’s age.
-
@info-creaticode How about instead of exposing the age directly, instead a block that returns the maturity rating based on the user’s age. For example, a block that might return G, PG, or M, based on the user’s age.
-
We try to avoid exposing information about a user’s birth year/month to other users/programs.
Maybe we can allow the author of a project to assign a rating to their project, so our system can automatically hide the “horror” level projects from young users?
@info-creaticode
Couldn’t you just watch someone’s profile (on the forums) and see what day the “AGE: XX” goes up?I understand it’s to protect minors, but there’s like- thousands of kids on the age… lets say 11. It’s nearly impossible to find someone just from their first name (unless it’s highly unique), and their birthday.
-
We try to avoid exposing information about a user’s birth year/month to other users/programs.
Maybe we can allow the author of a project to assign a rating to their project, so our system can automatically hide the “horror” level projects from young users?
@info-creaticode This is a good idea, but for project settings, I think project settings should be moved from the top navbar
to a seperate page where below canvas and viewport size settings, it would say “Edit project settings” Or just have a link at the top labelled “Project settings” to make it easier to find, and there it would let you change title, description & credits (rather than having to go to the project page to edit those), and age rating settings.Age rating settings could just be like:
Restrict ages below to use this project?
-
@info-creaticode
Couldn’t you just watch someone’s profile (on the forums) and see what day the “AGE: XX” goes up?I understand it’s to protect minors, but there’s like- thousands of kids on the age… lets say 11. It’s nearly impossible to find someone just from their first name (unless it’s highly unique), and their birthday.
@c Well malicious projects might want to do things like target certain ages and provide content to their advantage, like perhaps horror/inappropriate content.
#LLJW
<span style="color:white;background-image:linear-gradient(to right, lightblue, navy)">My name is Jeff</span> -
@c Well malicious projects might want to do things like target certain ages and provide content to their advantage, like perhaps horror/inappropriate content.
@jeffreyrb03-gmail
Yeah. -
@mod-squadacademy
Well, in theory, we shouldn’t want to expose any information about a user to others, right?
@info-creaticode What I am suggesting wouldn’t expose their age. If would still use their age, but it wouldn’t display it. It would only display a maturity rating.
The alternative is to adopt Gandi IDE’s rating system. This means you can either set the project as being for everyone, or not for everyone.
-
@info-creaticode What I am suggesting wouldn’t expose their age. If would still use their age, but it wouldn’t display it. It would only display a maturity rating.
The alternative is to adopt Gandi IDE’s rating system. This means you can either set the project as being for everyone, or not for everyone.
@mod-squadacademy that’s exactly what they said, so that stuff will be done server-side and not expose age to the project, as age is none of the project’s business, and it would be a project setting to deny running the project for people below a specified age or using preset age ratings (like 13,10, or 18)
-
@info-creaticode This is a good idea, but for project settings, I think project settings should be moved from the top navbar
to a seperate page where below canvas and viewport size settings, it would say “Edit project settings” Or just have a link at the top labelled “Project settings” to make it easier to find, and there it would let you change title, description & credits (rather than having to go to the project page to edit those), and age rating settings.Age rating settings could just be like:
Restrict ages below to use this project?
@jeffreyrb03-gmail said in Age Block?:
let you change title, description & credits (rather than having to go to the project page to edit those)
Well, this would be counterintuitive since most users are already used to changing them on the project page, right?
-
@jeffreyrb03-gmail said in Age Block?:
let you change title, description & credits (rather than having to go to the project page to edit those)
Well, this would be counterintuitive since most users are already used to changing them on the project page, right?
@info-creaticode Maybe, but users would get used to that quickly since it’d only need 1-2 clicks to get there, and having a page/modal popup for it would let you put a lot more settings/customization for a project there to add for the future when more needs to be added. An age restriction is also sort of a mischallenous setting but also important so if someone needs to put one they’d likely find it easily by going to a project settings page.
#LLJW
<span style="color:white;background-image:linear-gradient(to right, lightblue, navy)">My name is Jeff</span> -
@info-creaticode Maybe, but users would get used to that quickly since it’d only need 1-2 clicks to get there, and having a page/modal popup for it would let you put a lot more settings/customization for a project there to add for the future when more needs to be added. An age restriction is also sort of a mischallenous setting but also important so if someone needs to put one they’d likely find it easily by going to a project settings page.
@jeffreyrb03-gmail I think that an age restrictions should be on the main project page, since stuff in the editor is related to building, and everything the developer can access on the project page is related to publishing (description and credits and title are mainly only on there, title would count as coding for organizing) so age restriction should go there, the viewport and canvas sizes are also not related to publishing
<div component="post/signature" data-uid="255" class="post-signature">Check out my chat room project so you ppl can not use forums as chat rooms! https://play.creaticode.com/projects/66f2e1dcd1be43d82b886fbd?version=1 <p dir="auto">
</div> -
@jeffreyrb03-gmail I think that an age restrictions should be on the main project page, since stuff in the editor is related to building, and everything the developer can access on the project page is related to publishing (description and credits and title are mainly only on there, title would count as coding for organizing) so age restriction should go there, the viewport and canvas sizes are also not related to publishing
@tyller_ That’s actually a pretty good idea, it fits more with the nature of Scratch and CreatiCode rather than my idea
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better đź’—
Register Login