OnTheCode99 wrote:

Support. BUT there is one issue. Some PlayStation controllers are wired, and they don’t use the same buttons as controllers usually have. I also think that it should be wireless, but I guess that would make the bug I stated more widespread.

snapkin wrote:

However, generally, the phones are expensive as is, and people don’t want to spend the extra money for a controller that they’d only use for a Scratch project. And most controllers are pretty expensive too.

OnTheCode99 wrote:

Support. BUT there is one issue. Some PlayStation controllers are wired, and they don’t use the same buttons as controllers usually have. I also think that it should be wireless, but I guess that would make the bug I stated more widespread.

Bla-Games wrote:

Support
It would be really cool

ALLEN_VAN wrote:

(#1548)

Bla-Games wrote:

Support
It would be really cool

It would be very cool

Crispydogs101 wrote:

Is this based of a rejected feature? I think it is but at the same time not.

Minecraft_Master3964 wrote:

Crispydogs101 wrote:

Is this based of a rejected feature? I think it is but at the same time not.

Scratch for consoles is rejected, but not USB controllers.

GameKlikk_Studios wrote:

Support

mumu245 wrote:

The problem with analog input is that it can't be mapped to a mouse/keyboard, and I don't want people to make controller-only projects, because many people, including me, haven't got a controller.

cookieclickerer33 wrote:

Switch controllers don’t have analog triggers
Xbox controllers have an extra button
All these controllers have a completely different syntax so you would be to re code everything for each controller
The joy cons, like
How would those even work with the motion sensors

There’s too many logistical issues for me to be able to support, I want to but I just don’t think there’s a way ST could generalize a system that works on all controllers without simplifying it down to an nes controller

Maybe a specific controller built for scratch that works with other programs like the scratchbit?

Mainly I think people don’t realize that all controllers are coded differently and st would need to modify the blocks to work with every possible connectible controllers, they don’t all work the same

DerpyHead0 wrote:

cookieclickerer33 wrote:

Switch controllers don’t have analog triggers
Xbox controllers have an extra button
All these controllers have a completely different syntax so you would be to re code everything for each controller
The joy cons, like
How would those even work with the motion sensors

There’s too many logistical issues for me to be able to support, I want to but I just don’t think there’s a way ST could generalize a system that works on all controllers without simplifying it down to an nes controller

Maybe a specific controller built for scratch that works with other programs like the scratchbit?

Mainly I think people don’t realize that all controllers are coded differently and st would need to modify the blocks to work with every possible connectible controllers, they don’t all work the same

have you ever worked with controllers in a web browser? this isn't true. the controllers DO work almost exactly the same, except the joycons. xbox, ps4, and switch pro are all basically the same except for tiny differences in triggers or extra buttons. “completely different syntax” doesn't mean anything, those words don't even go together like that.

this doesn't need support for every controller, an easy way to do it would be to support only the main things the switch pro has, and then every other controller has it. no motion controls, no analog triggers, nothing else weird. it would still have two analog sticks, face buttons, dpad, many shoulder buttons, etc.

mumu245 wrote:

The problem with analog input is that it can't be mapped to a mouse/keyboard, and I don't want people to make controller-only projects, because many people, including me, haven't got a controller.

cookieclickerer33 wrote:

Also syntax is the way that you can use the controller in an IO situation and the way that you make requests to that. The controllers have different syntaxes

TheGlassPenguin wrote:

cookieclickerer33 wrote:

Also syntax is the way that you can use the controller in an IO situation and the way that you make requests to that. The controllers have different syntaxes

i thought syntax referred to a way the code itself is typed? not referring to input/output?

i think the scratch team would implement this through the javascript gamepad api, which i have tested with an xbox controller and a generic controller, and they worked nearly identically to each other

cookieclickerer33 wrote:

It’s both

And yes the way the code is typed is different


The offline editor and editor itself isn’t coded in JavaScript