JaceG2918 wrote:

yeah! Thats a good idea!

-ads-

sir-wallace wrote:

Support would be good due to the massive amount of console players may be able to play scratch games from their console browsers on scratch.

Elijah999999 wrote:

(#1709)
This would be cool, but in the “explore” page, there should be a box labeled “allow controller extensions” so that users don't need to see games that they don't have the remotes for anyway.

RobotChickens wrote:

Elijah999999 wrote:

(#1709)
This would be cool, but in the “explore” page, there should be a box labeled “allow controller extensions” so that users don't need to see games that they don't have the remotes for anyway.

I think a general “sort by extension” sugestion would be a good idea!

Dogs-are-amazing1 wrote:

RobotChickens wrote:

Elijah999999 wrote:

(#1709)
This would be cool, but in the “explore” page, there should be a box labeled “allow controller extensions” so that users don't need to see games that they don't have the remotes for anyway.

I think a general “sort by extension” sugestion would be a good idea!

I think you should make a new topic for that, it seems useful

Newaccount231 wrote:

-mehheheheheheheh- did this but I can't get it to work

Minecraft_Master3964 wrote:

Newaccount231 wrote:

-mehheheheheheheh- did this but I can't get it to work

Please don't name third-party things.

Newaccount231 wrote:

Turbowarp did this but I can't get it to work

SArpnt wrote:

Scratch has a lot of extensions for things like lego, makey makey, generally some strange input types that aren't usable for a lot of projects.
adding support for controllers would help lots of projects, especially ones that work well with analog input, like driving games,

when button [a v] pressed :: extension hat // buttons include ABXY, dpad, L, R, L1, R1, L2, R2, L stick, R stick (analog sticks can be clicked down on some controllers)
// this could also have blocks dropped in as an input, just like you can for key pressed blocks.
// when dropping in blocks, it could take the button number ids, meaning that even unsupported controllers could work (to an extent)

when [L2 v] distance [= v] (100) % :: extension hat // input options are triggers and all stick movement (shown on next blocks)
// this block could also have blocks dropped in and take axis ids, just like the button blocks.

[normal v] rumble for (1) secs until done :: extension stack // different rumble strengths

[normal v] rumble for (1) secs :: extension stack // doesn't pause script to rumble

[normal v] rumble :: extension stack // just keeps rumbling until stopped

stop rumble :: extension stack

<button [a v] pressed? :: extension> // (can drop in blocks, like above)

([left v] stick x :: extension)

([left v] stick y :: extension)

([left v] stick direction :: extension)

([left v] stick distance :: extension) // how far the stick is from the center

([L2 v] distance :: extension) // how far the trigger is pushed down (can drop in blocks, like above)

triggers are LT, RT, L2, R2, or ZL, ZR. note that switch controllers (if they get support) just have triggers (ZL and ZR) be at either 0% or 100% since they aren't analog.
if possible, it would change these depending on the controller currently connected, but if it can't, it could just use positions for ABXY (like the switch does for single joycons), and just use L1/L2 (there's only 2 of them, anyone can figure out which is which easily just by trying it)

another thing that could be done is adding support for multiple controllers, for thigns like multiple players. with would modify the blocks to add player numbers from 1-4 (this would be the same as the player indicator on the controller) and add these blocks.

when player [1 v] connected :: extension hat

when player [1 v] disconnected :: extension hat

<player [1 v] connected? :: extension>

multiple controllers should probably be a togglable option (if added) because it does make things much more complicated.

FAQ:
Q: why not use joytokey or other controller remapping programs?
A: these programs don't run on all devices, you often have to pay for them, and it doesn't support proper analog movement.

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 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.

Q: what about bluetooth/wireless controllers?
A: yes, this is handled by the operating system AND the browser already, it will never matter how you connect your controller, and it likely can't even be detected.

Q: what about blocks to check what kind of controllers people are using?
A: no, this will generally only cause problems. it shouldn't matter what controller people are using. you can already represent most inputs by their positions like the switch does. if this were added, people would likely run into issues using rare controllers. it also isn't clear how scratch would detect the type of controller, the only information it can use is a name which varies wildly even for similar controllers.

Q: what about this controller?
A: if it looks like a regular controller (xbox, playstation, switch, gamecube), and you can easily connect it to your computer (so not the wii classic controller), then yes. if not, then it probably wouldn't be supported. keep in mind that “not supported” here doesn't neccicarily mean the controller won't connect, it may just behave oddly. you could still use these controllers with the button and distance blocks, you would just have to figure out how to get it to work manually.
for example, layouts like the n64 controller just are different buttons, and no second joystick. you would likely have issues using the dropdowns for buttons, but you could just input numbers yourself, including to get all the C buttons.
you can test out your controller on HTML5 gamepad tester, it shows you how all the inputs on your controller work.

mybirdiscrazy wrote:

(#1719)

SArpnt wrote:

-Giant OP snip-

Are you saying Xbox ,PlayStation or Nintendo

Minecraft_Master3964 wrote:

Newaccount231 wrote:

-mehheheheheheheh- did this but I can't get it to work

Please don't name third-party things.

mybirdiscrazy wrote:

SArpnt wrote:

one snip to snip them all.

Are you saying Xbox ,PlayStation or Nintendo

medians wrote:

Minecraft_Master3964 wrote:

Newaccount231 wrote:

-mehheheheheheheh- did this but I can't get it to work

Please don't name third-party things.

You can name turbowarp, just not browser extensions.