TheSuccessor wrote:
nXIII wrote:
TheSuccessor wrote:
And if your mod doesn't support list reporters...
Then too bad for you!
Everything always seems to be too bad for me. I wonder how I survive.
![]()
![]()
I was kidding! You can just use "list imageForm" in the reporter tooltip to show an image of the list.
Last edited by nXIII (2010-09-06 13:52:30)
Offline
Did you find that out yourself or nick it from BYOB?
Offline
johnnydean1 wrote:
Recently there has been alot of talk of new blocks.
In this topic, I just want a list of the code for the new blocks and the name of them.
Ill start.
Offline
Honestly, the clone block is the STUPIDEST block ever. What if we want to give it different scripts in the middle of the project? Then what? What if you use the delete block to delete itself? What if the clone block finds itself into a forever loop? Memory overload? Honestly, it's stupid. Both of these ideas are stupid and hard to implement. Don't bother trying to do this at home, kids. It's a waste of time. As for the camera block, it's kinda ridiculous because what will it be named? Enter presentation: What will happen online? Record sound: See camera block. Attach/detach: What does that mean? Save picture and close scratch: See Enter presentation block. All keys pressed(nXIII): Get real. Who would bother to press every button on their keyboard just to make a block return true? Seriously? Though it is an interesting idea. Wonder who would try that.
Overall, most of these are the stupidest blocks ever CONCEIVED. However, any key pressed and hidden? would easily find a way into my heart. Very useful indeed.
Congrats to sparks, who claims that he implemented some of these in Panther. Nice job. Honestly.
Last edited by fmasroor (2010-12-10 15:50:35)
Offline
fmasroor wrote:
Honestly, the clone block is the STUPIDEST block ever. What if we want to give it different scripts in the middle of the project? Then what? What if you use the delete block to delete itself? What if the clone block finds itself into a forever loop? Memory overload? Honestly, it's stupid. Both of these ideas are stupid and hard to implement. Don't bother trying to do this at home, kids. It's a waste of time. As for the camera block, it's kinda ridiculous because what will it be named? Enter presentation: What will happen online? Record sound: See camera block. Attach/detach: What does that mean? Save picture and close scratch: See Enter presentation block. All keys pressed(nXIII): Get real. Who would bother to press every button on their keyboard just to make a block return true? Seriously? Though it is an interesting idea. Wonder who would try that.
Overall, most of these are the stupidest blocks ever CONCEIVED. However, any key pressed and hidden? would easily find a way into my heart. Very useful indeed.
Congrats to sparks, who claims that he implemented some of these in Panther. Nice job. Honestly.
The clone and delete blocks are actually very useful when used responsibly. They allow you to create multiple sprites for things like brick breakers. Want to change a script halfway through a project? I'm sure you can press stop, delete the extras and edit the original's code. In Panther, the clones self-delete and can also be named so that they can be treated individually. I have made entire projects out of clones including a few games, so they really are a space saving method of writing projects.
Again, Panther has camera blocks for webcam that are very useful and fun to play with.
Attatch/detatch allowds you to nest sprites together like in BYOB.
The added keyboard keys are actually really useful! Having the full keyboard really increases the power of projects, using control you can give two meanings to one key, using backspace you can replace the stupid left arrow for typing projects.
I think your main argument here is that they don't work online, and my only repetoir is that if that's the price of more power and control then I'll take it and host my project instead
nXIII should be credited for adding the blocks in Panther, he implimented them not me
Offline
Oh. I must have misunderstood the clone block. If it is like a normal block, for example [blocks]<switch to costume[ [/blocks], then yes, it is a dumb idea to use online in a forever loop. But if it's just a button, for example the 'Surprise Sprite', then yeah. Go ahead!
Wait. Isn't there already a duplicate feature? Right click on the sprite and click 'duplicate'. Am I still not understanding?
Oh, and don't forget to close those parentheses, sparks.
Last edited by fmasroor (2010-12-30 08:52:49)
Offline
fmasroor wrote:
Oh. I must have misunderstood the clone block. If it is like a normal block, for example [blocks]<switch to costume[ [/blocks], then yes, it is a dumb idea to use online in a forever loop. But if it's just a button, for example the 'Surprise Sprite', then yeah. Go ahead!
Wait. Isn't there already a duplicate feature? Right click on the sprite and click 'duplicate'. Am I still not understanding?
Oh, and don't forget to close those parentheses, sparks.
The clone block is indeed a normal block, and it would clearly be stupid to use it in a forever loop. However, a clone block can be very useful in certain situations, such as when you need to create new sprites in the middle of a project depending on what a user does, such as a wall building program where a user clicks where they want a brick. Here you can clone a sprite and send it to the mouse pointer, keeping all the functionality of the original sprite which is lost if stamping is used. Also, if a game required lots of the same sprite, but only at a particular time, it would useful to have a clone block to make the project easier, faster and more efficient.
Offline