-
Notifications
You must be signed in to change notification settings - Fork 18
Suggestion: Make Extension Add Ability to Make "Hacked Blocks" #16
Comments
Hmm, so, perhaps via the search menu that open when the user presses Control+Space? I think that maybe only a few should be included. I would probably say these: -- All at once, an obsolete c shaped-control block that runs the code inside without screen refresh. |
I was thinking more about making all blocks "droppable", but that would work too. |
@AmazingMech2418 What do you mean by that? |
i guess he means making custom blcoks have dropdown input like |
@Explosion-Scratch I mean like when you used to be able to set the variable name to another variable's value or something. |
that can be made by right clicking on the variable and change it to the variable you want |
@scratchusernamemrtbts That's not what I mean. I mean like in the |
@AmazingMech2418 do you mean that you can put reporter block into this block |
But would this actually reset the timer or would it set a variable with the output of the timer to 0? |
@Explosion-Scratch That would set a variable that is the same name as the timer value to 0. |
@AmazingMech2418. Makes sense! :) |
If he can do that can you make this kind of thing happen with the list category too? |
I fully support this. That way, you could reuse scripts on different lists. |
Having looked through the code for the scratch-vm, i've realized that the extension cannot make anything which can't be done in regular scratch as while the extension could create hacked blocks, these blocks will have opcodes which aren't supported by scratch-vm, and so the project cannot be compiled. |
i think you can now close this issue and this is not an issue btw . |
This is not an issue but feature request can be make in the issue tab |
No , its been 3 MONTHS since this is opened , and griffpatch hasen't responded yet , though he has responded to issues opened after this , so probably means to close . |
He doesn’t respond yet but he already see this
He isn’t very active
… เมื่อ 17 ก.ย. 2563 เวลา 19:37 เขียนโดย Akash Karthik ***@***.***>:
i think you can now close this issue and this is not an issue btw .
This is not an issue but feature request can be make in the issue tab
No , its been 3 MONTHS since this is opened , and griffpatch hasen't responded yet , though he has responded to issues opened after this , so probably means to close .
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#16 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APZ7UQPFAXPEDLCVMTLVM6DSGH7IPANCNFSM4OIYZGJA>.
|
i know he has seen it , but ignored , so close it , lol |
We can close an issue only when it is fixed or there are no way to make that feature
btw. I can’t close it
… เมื่อ 17 ก.ย. 2563 เวลา 20:20 เขียนโดย Akash Karthik ***@***.***>:
He doesn’t respond yet but he already see this He isn’t very active
… <x-msg://7/#>
เมื่อ 17 ก.ย. 2563 เวลา 19:37 เขียนโดย Akash Karthik @.***>: i think you can now close this issue and this is not an issue btw . This is not an issue but feature request can be make in the issue tab No , its been 3 MONTHS since this is opened , and griffpatch hasen't responded yet , though he has responded to issues opened after this , so probably means to close . — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#16 (comment) <#16 (comment)>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/APZ7UQPFAXPEDLCVMTLVM6DSGH7IPANCNFSM4OIYZGJA <https://github.com/notifications/unsubscribe-auth/APZ7UQPFAXPEDLCVMTLVM6DSGH7IPANCNFSM4OIYZGJA>.
i know he has seen it , but ignored , so close it , lol
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#16 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APZ7UQOL5DK4XWR4J45KBPLSGIEJRANCNFSM4OIYZGJA>.
|
i know |
Bump |
bump ? |
This is not a good plan - I was super burned by using hacked blocks when
Scratch moved from v2 to v3 - I won't be making that mistake again! :D
…On Fri, 5 Mar 2021 at 12:45, Akash Karthik ***@***.***> wrote:
bump ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#16 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABTM3PWOWH5BEC3TDFUBTA3TCDG7FANCNFSM4OIYZGJA>
.
|
that would be fine , it would probably ruin the real scratch coding tho not worth trying rlly . But i did find a scratch tutorial to make hacked blocks there are actually many https://scratch.mit.edu/search/projects?q=hacked%20blocks |
With Scratch 3.0, many projects broke and many abilities were taken away by the removal of "hacked blocks". Though, it still might be possible to edit the JSON to create a "hacked block", although the JSON is now less readable than it was before. Also, it might be possible to make blocks "droppable" by injecting code into scratch-vm (I see you were able to get into Blockly with this extension) which would in turn allow "hacked blocks" to be made. Additionally, given that the Scratcher did not click "see inside" since the transition to 3.0, the project will still contain an sb2 format, meaning that the "droppable" blocks would convert to Scratch 3.0 properly instead of breaking the project. I'm not sure if this can be done in an extension quite yet, but I think it would be a great feature to add! Also, if there is any way I can help with the development of this, I'd be happy to help!
The text was updated successfully, but these errors were encountered: