RobotChickens wrote:

Mozboz wrote:

(#1884)

mumu245 wrote:

So, how would we handle potential controller-only projects?

That probably wouldn't be allowed. All projects would probably have to have keyboard or mobile control. And even so, “Remix” exists.

Enforcing this would be super hard. Instead, people would complain in the comments and not heart/star the project. Most likely someone would remix it and add keyboard controls, which would get more popular than the original project anyways. That would be the creator's fault for not adding keyboard.
(What about the MicroBit-only projects?)

Mozboz wrote:

And even so, “Remix” exists.

sonic__fan wrote:

RobotChickens wrote:

Mozboz wrote:

(#1884)

mumu245 wrote:

So, how would we handle potential controller-only projects?

That probably wouldn't be allowed. All projects would probably have to have keyboard or mobile control. And even so, “Remix” exists.

Enforcing this would be super hard. Instead, people would complain in the comments and not heart/star the project. Most likely someone would remix it and add keyboard controls, which would get more popular than the original project anyways. That would be the creator's fault for not adding keyboard.
(What about the MicroBit-only projects?)

How would enforcing this rule be hard? Just add an option to report the project with the reason being “no keyboard support”.
And if a remix of the project got more popular than the OG because the OG didn't have keyboard support, isn't that good? The creator of the OG project got what they deserve.

Dogs-are-amazing1 wrote:

sonic__fan wrote:

RobotChickens wrote:

Mozboz wrote:

(#1884)

mumu245 wrote:

So, how would we handle potential controller-only projects?

That probably wouldn't be allowed. All projects would probably have to have keyboard or mobile control. And even so, “Remix” exists.

Enforcing this would be super hard. Instead, people would complain in the comments and not heart/star the project. Most likely someone would remix it and add keyboard controls, which would get more popular than the original project anyways. That would be the creator's fault for not adding keyboard.
(What about the MicroBit-only projects?)

How would enforcing this rule be hard? Just add an option to report the project with the reason being “no keyboard support”.
And if a remix of the project got more popular than the OG because the OG didn't have keyboard support, isn't that good? The creator of the OG project got what they deserve.

Why make a rule for it though? There’s no rules for keyboard only projects, mobile only projects, or other projects like those, do I don’t see why this is needed

Dogs-are-amazing1 wrote:

sonic__fan wrote:

RobotChickens wrote:

Mozboz wrote:

(#1884)

mumu245 wrote:

So, how would we handle potential controller-only projects?

That probably wouldn't be allowed. All projects would probably have to have keyboard or mobile control. And even so, “Remix” exists.

Enforcing this would be super hard. Instead, people would complain in the comments and not heart/star the project. Most likely someone would remix it and add keyboard controls, which would get more popular than the original project anyways. That would be the creator's fault for not adding keyboard.
(What about the MicroBit-only projects?)

How would enforcing this rule be hard? Just add an option to report the project with the reason being “no keyboard support”.
And if a remix of the project got more popular than the OG because the OG didn't have keyboard support, isn't that good? The creator of the OG project got what they deserve.

Why make a rule for it though? There’s no rules for keyboard only projects, mobile only projects, or other projects like those, do I don’t see why this is needed

medians wrote:

Also, if keyboard only projects were suddenly not allowed then.. I guess goodbye to a ton of projects from before 3.0

sonic__fan wrote:

Dogs-are-amazing1 wrote:

sonic__fan wrote:

RobotChickens wrote:

Mozboz wrote:

(#1884)

mumu245 wrote:

So, how would we handle potential controller-only projects?

That probably wouldn't be allowed. All projects would probably have to have keyboard or mobile control. And even so, “Remix” exists.

Enforcing this would be super hard. Instead, people would complain in the comments and not heart/star the project. Most likely someone would remix it and add keyboard controls, which would get more popular than the original project anyways. That would be the creator's fault for not adding keyboard.
(What about the MicroBit-only projects?)

How would enforcing this rule be hard? Just add an option to report the project with the reason being “no keyboard support”.
And if a remix of the project got more popular than the OG because the OG didn't have keyboard support, isn't that good? The creator of the OG project got what they deserve.

Why make a rule for it though? There’s no rules for keyboard only projects, mobile only projects, or other projects like those, do I don’t see why this is needed

Because not everyone has a controller to plug into their computer, meanwhile everyone has either a phone or a computer.

medians wrote:

Also, if keyboard only projects were suddenly not allowed then.. I guess goodbye to a ton of projects from before 3.0

No, they wouldn't be banned, as everyone has a keyboard (or at least can use an on-screen keyboard).

crawfishcode wrote:

I mean, a lot of the scratch community consists of little kids learning how to code, so it makes sense that they would put in extensions that are appealing to little kids. And, while I completely understand the purpose of these extensions, there are also teens (like myself) and adults who use Scratch who would like an idea of our own added, so they should listen to the community and implement something that us big kids want too. I mean, this thread has been going for almost 6 years (that's a long time, wow!) and still no response from the ST about our thread, except a few snips from the moderators.

ST, if you are reading this, PLEASE consider making a statement on whether or not you guys will implement this, so we can figure out whether or not we need to continue this thread. We are a small community of folks who are passionate about this idea, and this thread has over 1800 posts (that's a lot for a forum thread!) of us communicating back and forth about how to go forward and little extra mini-ideas we came up with in our spare time. You guys are the only ones who have the power to implement this function into your program, and we have been patiently waiting for almost 6 years for a response that gives us an idea on what the future of our idea will be. So PLEASE make a post on how it's all gonna go down.

Your friend,

crawfishcode

P.S. wasn't trying to sound rude, if it sounded that way i'm sorry

I mean, this thread has been going for almost 6 years (that's a long time, wow!) and still no response from the ST about our thread, except a few snips from the moderators.

I feel like if they do plan to implement controller support, they'll stay quiet until they've got it nearly done.

T_S_13 wrote:

Support. There are 11 extensions in the Scratch Editor, And it would be nice if there were more extensions.

mumu245 wrote:

sonic__fan wrote:

Dogs-are-amazing1 wrote:

sonic__fan wrote:

RobotChickens wrote:

Mozboz wrote:

(#1884)

mumu245 wrote:

So, how would we handle potential controller-only projects?

That probably wouldn't be allowed. All projects would probably have to have keyboard or mobile control. And even so, “Remix” exists.

Enforcing this would be super hard. Instead, people would complain in the comments and not heart/star the project. Most likely someone would remix it and add keyboard controls, which would get more popular than the original project anyways. That would be the creator's fault for not adding keyboard.
(What about the MicroBit-only projects?)

How would enforcing this rule be hard? Just add an option to report the project with the reason being “no keyboard support”.
And if a remix of the project got more popular than the OG because the OG didn't have keyboard support, isn't that good? The creator of the OG project got what they deserve.

Why make a rule for it though? There’s no rules for keyboard only projects, mobile only projects, or other projects like those, do I don’t see why this is needed

Because not everyone has a controller to plug into their computer, meanwhile everyone has either a phone or a computer.

medians wrote:

Also, if keyboard only projects were suddenly not allowed then.. I guess goodbye to a ton of projects from before 3.0

No, they wouldn't be banned, as everyone has a keyboard (or at least can use an on-screen keyboard).

Most people (I assume at least 75%) have a computer with keyboard and mouse. I have hardly seen any people with a controller, I think it's safe to assume less than 15% of Scratch users have one.

sonic__fan wrote:

RobotChickens wrote:

Mozboz wrote:

(#1884)

mumu245 wrote:

So, how would we handle potential controller-only projects?

That probably wouldn't be allowed. All projects would probably have to have keyboard or mobile control. And even so, “Remix” exists.

Enforcing this would be super hard. Instead, people would complain in the comments and not heart/star the project. Most likely someone would remix it and add keyboard controls, which would get more popular than the original project anyways. That would be the creator's fault for not adding keyboard.
(What about the MicroBit-only projects?)

How would enforcing this rule be hard? Just add an option to report the project with the reason being “no keyboard support”.
And if a remix of the project got more popular than the OG because the OG didn't have keyboard support, isn't that good? The creator of the OG project got what they deserve.

sonic__fan wrote:

Dogs-are-amazing1 wrote:

sonic__fan wrote:

RobotChickens wrote:

Mozboz wrote:

(#1884)

mumu245 wrote:

So, how would we handle potential controller-only projects?

That probably wouldn't be allowed. All projects would probably have to have keyboard or mobile control. And even so, “Remix” exists.

Enforcing this would be super hard. Instead, people would complain in the comments and not heart/star the project. Most likely someone would remix it and add keyboard controls, which would get more popular than the original project anyways. That would be the creator's fault for not adding keyboard.
(What about the MicroBit-only projects?)

How would enforcing this rule be hard? Just add an option to report the project with the reason being “no keyboard support”.
And if a remix of the project got more popular than the OG because the OG didn't have keyboard support, isn't that good? The creator of the OG project got what they deserve.

Why make a rule for it though? There’s no rules for keyboard only projects, mobile only projects, or other projects like those, do I don’t see why this is needed

Because not everyone has a controller to plug into their computer, meanwhile everyone has either a phone or a computer.

medians wrote:

Also, if keyboard only projects were suddenly not allowed then.. I guess goodbye to a ton of projects from before 3.0

No, they wouldn't be banned, as everyone has a keyboard (or at least can use an on-screen keyboard).

creeperyeettt wrote:

sonic__fan wrote:

Dogs-are-amazing1 wrote:

sonic__fan wrote:

RobotChickens wrote:

Mozboz wrote:

(#1884)

mumu245 wrote:

So, how would we handle potential controller-only projects?

That probably wouldn't be allowed. All projects would probably have to have keyboard or mobile control. And even so, “Remix” exists.

Enforcing this would be super hard. Instead, people would complain in the comments and not heart/star the project. Most likely someone would remix it and add keyboard controls, which would get more popular than the original project anyways. That would be the creator's fault for not adding keyboard.
(What about the MicroBit-only projects?)

How would enforcing this rule be hard? Just add an option to report the project with the reason being “no keyboard support”.
And if a remix of the project got more popular than the OG because the OG didn't have keyboard support, isn't that good? The creator of the OG project got what they deserve.

Why make a rule for it though? There’s no rules for keyboard only projects, mobile only projects, or other projects like those, do I don’t see why this is needed

Because not everyone has a controller to plug into their computer, meanwhile everyone has either a phone or a computer.

medians wrote:

Also, if keyboard only projects were suddenly not allowed then.. I guess goodbye to a ton of projects from before 3.0

No, they wouldn't be banned, as everyone has a keyboard (or at least can use an on-screen keyboard).

on screen keyboard dont work for scratch
and not everyone has a phone
not everyone has a computer
not everyone has a controller
its fine, I would bet more people have controllers then phones anyway

creeperyeettt wrote:

sonic__fan wrote:

RobotChickens wrote:

Mozboz wrote:

(#1884)

mumu245 wrote:

So, how would we handle potential controller-only projects?

That probably wouldn't be allowed. All projects would probably have to have keyboard or mobile control. And even so, “Remix” exists.

Enforcing this would be super hard. Instead, people would complain in the comments and not heart/star the project. Most likely someone would remix it and add keyboard controls, which would get more popular than the original project anyways. That would be the creator's fault for not adding keyboard.
(What about the MicroBit-only projects?)

How would enforcing this rule be hard? Just add an option to report the project with the reason being “no keyboard support”.
And if a remix of the project got more popular than the OG because the OG didn't have keyboard support, isn't that good? The creator of the OG project got what they deserve.

well we dont see people reporting if a project has no mobile or if it uses another extention like lego

creeperyeettt wrote:

fun fact over 50% of US households own a games console, meaning they most likely have controllers

iIovef4f wrote:

SArpnt wrote:

Q: what about wii remotes?
A: Most operating systems don't support wii remotes without extra software, and this could get a lot of people confused. pointing the wii remote also wouldn't work because you would need the wii sensor bar, which many people won't realize and create MANY help threads to try and get it to work. motion control and point sensing would be VERY hard for the scratch team to implement, and would only work for wii remotes. there will also likely be lots of suggestions about nunchuk support, classic controller, motion+, and every single other thing that can be connected to a wii remote, which each part being used extremely little. these controls also don't translate to mouse/keyboard well, which will likely result in tons of projects that only work with a woo (wii) remote, and leave people unable to play them. it also doesn't make sense what the blocks would be for this, they would either not be useful or be far too complicated for most people to use.
TLDR: too much work, doesn't make sense, too confusing for users, suggestions spam, and unplayable projects.

Uhmmm, Dualshock 4, Dualsense, Joy-Con, Switch Pro Controller, Ps Move, Oculus Quest Controller, PSVR2 Controller, Dreamcast Controller, etc.

Just give a position that's all you need just motion control x and y

(motion [x v] position::pen)

creeperyeettt wrote:

iIovef4f wrote:

SArpnt wrote:

Q: what about wii remotes?
A: Most operating systems don't support wii remotes without extra software, and this could get a lot of people confused. pointing the wii remote also wouldn't work because you would need the wii sensor bar, which many people won't realize and create MANY help threads to try and get it to work. motion control and point sensing would be VERY hard for the scratch team to implement, and would only work for wii remotes. there will also likely be lots of suggestions about nunchuk support, classic controller, motion+, and every single other thing that can be connected to a wii remote, which each part being used extremely little. these controls also don't translate to mouse/keyboard well, which will likely result in tons of projects that only work with a woo (wii) remote, and leave people unable to play them. it also doesn't make sense what the blocks would be for this, they would either not be useful or be far too complicated for most people to use.
TLDR: too much work, doesn't make sense, too confusing for users, suggestions spam, and unplayable projects.

Uhmmm, Dualshock 4, Dualsense, Joy-Con, Switch Pro Controller, Ps Move, Oculus Quest Controller, PSVR2 Controller, Dreamcast Controller, etc.

Just give a position that's all you need just motion control x and y

(motion [x v] position::pen)

its not that easy please re read what they wrote

creeperyeettt wrote:

on screen keyboard dont work for scratch

creeperyeettt wrote:

and not everyone has a phone

creeperyeettt wrote:

not everyone has a computer

creeperyeettt wrote:

not everyone has a controller

creeperyeettt wrote:

its fine, I would bet more people have controllers then phones anyway

sonic__fan wrote:

creeperyeettt wrote:

on screen keyboard dont work for scratch

right i forgot about that
But most people that play projects don't play on their phones anyway.

creeperyeettt wrote:

and not everyone has a phone

Then they use a computer.

creeperyeettt wrote:

not everyone has a computer

Then they use a phone. If you're using Scratch, you have either a phone or a computer.

creeperyeettt wrote:

not everyone has a controller

Then don't play controller-based projects.

creeperyeettt wrote:

its fine, I would bet more people have controllers then phones anyway

Most likely not. Game controllers are only useful for video games. Phones can do almost anything a regular computer can do (minus more intensive stuff, like video game emulators) and fit in your pocket.