All right, the first matter of importance is to eliminate the unhelpful folks out there. If you find your argument against my idea running along the lines of “new Scratchers may/will be confused by this”, then, right now, I politely assure you that you are wrong, and not-so-politely tell you to clear off this thread until you have re-evaluated your assessment of the intelligences of young children (programmers, no less). Also, if you have no intention of properly reading this, then go away.

Sorry. Instinct from the 1.4 forums. Anyways, on to my idea. It occurred to me while I was thinking about the idea of sprites calling other sprites' methods. Through a long stretch, I reached this idea:
Add an option to create “child sprites,” sprites that are extended versions of other sprites, designed to perform more specific tasks, very much like inheritance in object-oriented programming. Child sprites are like duplicates, except the scripts and block definitions belong to the parent sprite, and don't show up in the child sprite. The child sprite possesses its own scripts and custom blocks, as well as those contained within its parent sprite. Also, the child sprite should have the ability to override block definitions in parent sprites.

Why not just duplicate it, you ask? Well, for large-scale sprites, it creates a great deal less clutter to have child sprites, and, if necessary, child sprites of child sprites, and so on. It also allows for a very organized approach to programming. Sprite inheritance would be a useful addition to Scratch.

I agree

lalala3 wrote:

Why not just duplicate it, you ask? Well, for large-scale sprites, it creates a great deal less clutter to have child sprites, and, if necessary, child sprites of child sprites, and so on. It also allows for a very organized approach to programming. Sprite inheritance would be a useful addition to Scratch.

Isn't that what clones are for?

I_LOVE_TO_MAKE_STUFF wrote:

lalala3 wrote:

Why not just duplicate it, you ask? Well, for large-scale sprites, it creates a great deal less clutter to have child sprites, and, if necessary, child sprites of child sprites, and so on. It also allows for a very organized approach to programming. Sprite inheritance would be a useful addition to Scratch.

Isn't that what clones are for?

Yeah I feel like clones can accomplish a lot of this

Wahsp wrote:

I_LOVE_TO_MAKE_STUFF wrote:

lalala3 wrote:

Why not just duplicate it, you ask? Well, for large-scale sprites, it creates a great deal less clutter to have child sprites, and, if necessary, child sprites of child sprites, and so on. It also allows for a very organized approach to programming. Sprite inheritance would be a useful addition to Scratch.

Isn't that what clones are for?

Yeah I feel like clones can accomplish a lot of this

Clones inherit the properties of a SINGLE sprite. For clones of clones, you have to define your own variables, properties, etc. I believe custom blocks are global by default.

I agree so I don't have to change every enemy in my game the have the same stuff.

game600 wrote:

I agree so I don't have to change every enemy in my game the have the same stuff.

please do not necropost

CodeComet6161 wrote:

game600 wrote:

I agree so I don't have to change every enemy in my game the have the same stuff.

please do not necropost

necroposting doesnt rlly exist in suggestions