Stage fencing is useless, we don't need it. If you really need to make sure that your sprites don't go off the stage then use the

if on edge, bounce

block and then set the direction to what it was before.

me_the_super wrote:

Stage fencing is useless, we don't need it. If you really need to make sure that your sprites don't go off the stage then use the

if on edge, bounce

block and then set the direction to what it was before.

Why should we remove stage fencing when the project stage can't be resized? ¯\_(ツ)_/¯

ajskateboarder wrote:

me_the_super wrote:

Stage fencing is useless, we don't need it. If you really need to make sure that your sprites don't go off the stage then use the

if on edge, bounce

block and then set the direction to what it was before.

Why should we remove stage fencing when the project stage can't be resized? ¯\_(ツ)_/¯

That's not why I wanted it gone, sprite fencing adds an extra step when making some games so we need to remove it.

me_the_super wrote:

ajskateboarder wrote:

me_the_super wrote:

Stage fencing is useless, we don't need it. If you really need to make sure that your sprites don't go off the stage then use the

if on edge, bounce

block and then set the direction to what it was before.

Why should we remove stage fencing when the project stage can't be resized? ¯\_(ツ)_/¯

That's not why I wanted it gone, sprite fencing adds an extra step when making some games so we need to remove it.

Programming is largely about working around restrictions, which stage fencing is.
Also, it allows users to find their sprites consistently

ajskateboarder wrote:

me_the_super wrote:

Stage fencing is useless, we don't need it. If you really need to make sure that your sprites don't go off the stage then use the

if on edge, bounce

block and then set the direction to what it was before.

Why should we remove stage fencing when the project stage can't be resized? ¯\_(ツ)_/¯

some people love rpg's

sprites can disappear

me_the_super wrote:

Stage fencing is useless, we don't need it. If you really need to make sure that your sprites don't go off the stage then use the

if on edge, bounce

block and then set the direction to what it was before.

stage fencing is for newer scratchers so they don't “lose” their sprites.
for example, what if someone brand new used a script like this:

when gf clicked
forever
change x by (100)
end

it would cause confusion when their sprite is just instantly gone off to the right. The stage fencing prevents this problem for newer scratchers.
Also, there's a workaround with a bigger costume you can do something like this:

define offscreen          //run without screen refresh
switch costume to [BIG v] 
go to x: (500) y: (0)
switch costume to [costume you want to see v]

So, stage fencing isn't useless its actually helpful.
It also requires people to have to think a little more for you to do something you want to happen.

GlitchedThrough wrote:

me_the_super wrote:

ajskateboarder wrote:

me_the_super wrote:

Stage fencing is useless, we don't need it. If you really need to make sure that your sprites don't go off the stage then use the

if on edge, bounce

block and then set the direction to what it was before.

Why should we remove stage fencing when the project stage can't be resized? ¯\_(ツ)_/¯

That's not why I wanted it gone, sprite fencing adds an extra step when making some games so we need to remove it.

Programming is largely about working around restrictions, which stage fencing is.
Also, it allows users to find their sprites consistently

Isn't it the Game Engine's job to make sure there are the least amount of restrictions they can get? Just make your sprite goto point (0,0) and that should let you find it.

undeterminstic wrote:

sprites can disappear

Then do this:

set [ whatever v] to (direction)
if on edge, bounce
point in direction (whatever)

me_the_super wrote:

GlitchedThrough wrote:

me_the_super wrote:

ajskateboarder wrote:

me_the_super wrote:

Stage fencing is useless, we don't need it. If you really need to make sure that your sprites don't go off the stage then use the

if on edge, bounce

block and then set the direction to what it was before.

Why should we remove stage fencing when the project stage can't be resized? ¯\_(ツ)_/¯

That's not why I wanted it gone, sprite fencing adds an extra step when making some games so we need to remove it.

Programming is largely about working around restrictions, which stage fencing is.
Also, it allows users to find their sprites consistently

Isn't it the Game Engine's job to make sure there are the least amount of restrictions they can get? Just make your sprite goto point (0,0) and that should let you find it.

NO! then it becomes hard to position stuff perfectly.

undeterministic

undeterministic wrote:

me_the_super wrote:

GlitchedThrough wrote:

me_the_super wrote:

ajskateboarder wrote:

me_the_super wrote:

Stage fencing is useless, we don't need it. If you really need to make sure that your sprites don't go off the stage then use the

if on edge, bounce

block and then set the direction to what it was before.

Why should we remove stage fencing when the project stage can't be resized? ¯\_(ツ)_/¯

That's not why I wanted it gone, sprite fencing adds an extra step when making some games so we need to remove it.

Programming is largely about working around restrictions, which stage fencing is.
Also, it allows users to find their sprites consistently

Isn't it the Game Engine's job to make sure there are the least amount of restrictions they can get? Just make your sprite goto point (0,0) and that should let you find it.

NO! then it becomes hard to position stuff perfectly.

undeterministic

Again:

set [ whatever v] to (direction)
if on edge, bounce
point in direction (whatever)

me_the_super wrote:

undeterminstic wrote:

sprites can disappear

Then do this:

set [ whatever v] to (direction)
if on edge, bounce
point in direction (whatever)

and scratch is meant to be a beginner programming language. I would be utterly terrified if my sprite went off screen.

undeterministic

me_the_super wrote:

GlitchedThrough wrote:

me_the_super wrote:

ajskateboarder wrote:

me_the_super wrote:

Stage fencing is useless, we don't need it. If you really need to make sure that your sprites don't go off the stage then use the

if on edge, bounce

block and then set the direction to what it was before.

Why should we remove stage fencing when the project stage can't be resized? ¯\_(ツ)_/¯

That's not why I wanted it gone, sprite fencing adds an extra step when making some games so we need to remove it.

Programming is largely about working around restrictions, which stage fencing is.
Also, it allows users to find their sprites consistently

Isn't it the Game Engine's job to make sure there are the least amount of restrictions they can get? Just make your sprite goto point (0,0) and that should let you find it.

Scratch ain’t a game engine, it’s a programming language.
Kids don’t necessarily understand that, and might not know how Scratch’s coordinate system works.

malicondii wrote:

stage fencing is for newer scratchers so they don't “lose” their sprites.
for example, what if someone brand new used a script like this:

when gf clicked
forever
change x by (100)
end

it would cause confusion when their sprite is just instantly gone off to the right. The stage fencing prevents this problem for newer scratchers.

^ Just wanted to highlight this as the answer. Yes, if stage fencing didn't exist, then there is a workaround for those who want to use it; but new Scratchers will not necessarily know that workaround. They are likely to be confused if they can no longer find their sprite.

I found a way to remove fencing entirely

switch costume to [0x0 v]
set size to [Infinity] %
go to x: (1000) y: (0)
switch costume to [last costume v]
set size to (last size) %

me_the_super wrote:

GlitchedThrough wrote:

me_the_super wrote:

ajskateboarder wrote:

me_the_super wrote:

Stage fencing is useless, we don't need it. If you really need to make sure that your sprites don't go off the stage then use the

if on edge, bounce

block and then set the direction to what it was before.

Why should we remove stage fencing when the project stage can't be resized? ¯\_(ツ)_/¯

That's not why I wanted it gone, sprite fencing adds an extra step when making some games so we need to remove it.

Programming is largely about working around restrictions, which stage fencing is.
Also, it allows users to find their sprites consistently

Isn't it the Game Engine's job to make sure there are the least amount of restrictions they can get? Just make your sprite goto point (0,0) and that should let you find it.

No, a game engine's job is to allow you to create a game. Scratch's job, unlike your traditional “game engines” is to teach children (or non-children, but moreso children) programming, thus, the ST has to consider that not everyone is able to figure out how “things going out of the given camera area” works, and don't say “no-one is that stupid” because I was that stupid B)

undeterministic wrote:

me_the_super wrote:

undeterminstic wrote:

sprites can disappear

Then do this:

set [ whatever v] to (direction)
if on edge, bounce
point in direction (whatever)

and scratch is meant to be a beginner programming language. I would be utterly terrified if my sprite went off screen.

undeterministic

An 8-year-old could probably figure out how to get it back.

GlitchedThrough wrote:

me_the_super wrote:

GlitchedThrough wrote:

me_the_super wrote:

ajskateboarder wrote:

me_the_super wrote:

Stage fencing is useless, we don't need it. If you really need to make sure that your sprites don't go off the stage then use the

if on edge, bounce

block and then set the direction to what it was before.

Why should we remove stage fencing when the project stage can't be resized? ¯\_(ツ)_/¯

That's not why I wanted it gone, sprite fencing adds an extra step when making some games so we need to remove it.

Programming is largely about working around restrictions, which stage fencing is.
Also, it allows users to find their sprites consistently

Isn't it the Game Engine's job to make sure there are the least amount of restrictions they can get? Just make your sprite goto point (0,0) and that should let you find it.

Scratch ain’t a game engine, it’s a programming language.
Kids don’t necessarily understand that, and might not know how Scratch’s coordinate system works.

It's still the programming language's job to make sure there's the least amount of limitations. Yes, they do want to make it overly simple so kids can easily make games, but they can just add a tutorial on how to fix this.

me_the_super wrote:

It's still the programming language's job to make sure there's the least amount of limitations. Yes, they do want to make it overly simple so kids can easily make games, but they can just add a tutorial on how to fix this.

No it isn’t. It’s the languages job to allow the programmer to tell the computer what to d without using pure binary, not necessarily to have no limitations. Most languages, even low level languages, have extreme limitations.

gdfsgdfsgdfg wrote:

Whats going on?

I'm wondering why we need stage fencing. Maybe you could read the replies to this post for extra context.