Mozboz wrote:

crawfishcode wrote:

I put a comment on Paddle2See's project asking if he knows anything. He might not answer, but it was worth a shot.

I think if you're going to try to reach him, Contact Us is the best way.

crawfishcode wrote:

Also everyone, thank you all so much for the positive responses toward my post! I didn't know how everyone would react after I posted it, but I logged on scratch just now to find that I got 2 new folllowers and positive comments on the forum! Again, Thank you!

Minecraft_Master3964 wrote:

crawfishcode wrote:

Also everyone, thank you all so much for the positive responses toward my post! I didn't know how everyone would react after I posted it, but I logged on scratch just now to find that I got 2 new folllowers and positive comments on the forum! Again, Thank you!

You’re welcome!

crawfishcode wrote:

I don't think we should do a PR, for a couple of reasons:

1. None of us (that I know of) are experienced in any coding language (except Scratch), and learning the language required to code the PR could take months, maybe even years!
2. We can't share any personal info (as enforced by the Community Guidelines), so communicating/coordinating in real time outside of Scratch would be impossible without getting banned/warned not to do it again.
3. It would take a long time to code the PR (I don't know the exact time, because I don't use Github) and for it to get reviewed.
4. The ST might not even approve it, and it might get denied, which means all the time we took to code it would be wasted.

This is what I think about it, just please don't be mean about my opinion.

Mozboz wrote:

(#1850)

crawfishcode wrote:

I don't think we should do a PR, for a couple of reasons:

1. None of us (that I know of) are experienced in any coding language (except Scratch), and learning the language required to code the PR could take months, maybe even years!
2. We can't share any personal info (as enforced by the Community Guidelines), so communicating/coordinating in real time outside of Scratch would be impossible without getting banned/warned not to do it again.
3. It would take a long time to code the PR (I don't know the exact time, because I don't use Github) and for it to get reviewed.
4. The ST might not even approve it, and it might get denied, which means all the time we took to code it would be wasted.

This is what I think about it, just please don't be mean about my opinion.

What's a PR again? I forgot.

misaPuding wrote:

Mozboz wrote:

(#1850)

crawfishcode wrote:

I don't think we should do a PR, for a couple of reasons:

1. None of us (that I know of) are experienced in any coding language (except Scratch), and learning the language required to code the PR could take months, maybe even years!
2. We can't share any personal info (as enforced by the Community Guidelines), so communicating/coordinating in real time outside of Scratch would be impossible without getting banned/warned not to do it again.
3. It would take a long time to code the PR (I don't know the exact time, because I don't use Github) and for it to get reviewed.
4. The ST might not even approve it, and it might get denied, which means all the time we took to code it would be wasted.

This is what I think about it, just please don't be mean about my opinion.

What's a PR again? I forgot.

Pull Request, basically you ask someone to add your code to the repository
also, regarding crawfish´s points:
1) I know a littlebit (though prob not enough), but GlitchInTheMatrix could do it i think
2) github usernames thankfully don´t cause alerts for now
3) it would be worth it
4) kinda good point, but it´d help you learn how to code

crawfishcode wrote:

misaPuding wrote:

Mozboz wrote:

(#1850)

crawfishcode wrote:

I don't think we should do a PR, for a couple of reasons:

1. None of us (that I know of) are experienced in any coding language (except Scratch), and learning the language required to code the PR could take months, maybe even years!
2. We can't share any personal info (as enforced by the Community Guidelines), so communicating/coordinating in real time outside of Scratch would be impossible without getting banned/warned not to do it again.
3. It would take a long time to code the PR (I don't know the exact time, because I don't use Github) and for it to get reviewed.
4. The ST might not even approve it, and it might get denied, which means all the time we took to code it would be wasted.

This is what I think about it, just please don't be mean about my opinion.

What's a PR again? I forgot.

Pull Request, basically you ask someone to add your code to the repository
also, regarding crawfish´s points:
1) I know a littlebit (though prob not enough), but GlitchInTheMatrix could do it i think
2) github usernames thankfully don´t cause alerts for now
3) it would be worth it
4) kinda good point, but it´d help you learn how to code

I asked GlitchInTheMatrix if they could help us, and they said that they would only help us after it's been coded

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

(motion [x v] position::pen)

TheEpikGamer211 wrote:

your saying a wireless non-bluetooth logitech mouse can be a controller?

sonic__fan wrote:

TheEpikGamer211 wrote:

your saying a wireless non-bluetooth logitech mouse can be a controller?

???
Where in this entire topic does it say that???
But no, your mouse cannot be used as a controller because your computer will register it as a mouse, not controller.

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

TheEpikGamer211 wrote:

sonic__fan wrote:

TheEpikGamer211 wrote:

your saying a wireless non-bluetooth logitech mouse can be a controller?

???
Where in this entire topic does it say that???
But no, your mouse cannot be used as a controller because your computer will register it as a mouse, not controller.

then why is it having a usb port?

crawfishcode 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 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)

Don't quote backwards that far!

sonic__fan wrote:

ChildWithKeyboard wrote:

Most computers don't have any port to put in the cord for a game console or controller, so we would have to change every computer to have that, or it would only work on new models with console ports if we made those. It would also only be compatible with the newest model of consoles, as, for example, a WiiMote has different buttons than a Switch controller.

bruh what
PS4, Xbox One, and Switch Pro Controllers all work via USB wires.
As for older controllers (Wii U, PS3, Xbox 360), all of those consoles are discontinued and more than 10 years old (PS3 in 2006, 360 in 2005, Wii U in 2012).
As for Wii remotes, there's a seperate topic for that.

Wifi_Spider wrote:

sonic__fan wrote:

ChildWithKeyboard wrote:

Most computers don't have any port to put in the cord for a game console or controller, so we would have to change every computer to have that, or it would only work on new models with console ports if we made those. It would also only be compatible with the newest model of consoles, as, for example, a WiiMote has different buttons than a Switch controller.

bruh what
PS4, Xbox One, and Switch Pro Controllers all work via USB wires.
As for older controllers (Wii U, PS3, Xbox 360), all of those consoles are discontinued and more than 10 years old (PS3 in 2006, 360 in 2005, Wii U in 2012).
As for Wii remotes, there's a seperate topic for that.

the could do the wierder ones with bluetooth

iIovef4f wrote:

crawfishcode wrote:

iIovef4f wrote:

SArpnt wrote:

-snip-

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)

Don't quote backwards that far!

Wdym???

Hamland2 wrote:

(Yes)