Transition scene to test scene loading events (breadcrumbs)

[semuserable]

• New TransitionScene with two buttons: load BugFarmScene and ThrowNull.
• New button (Load TransitionScene) in BugFarmScene

Now can test load scene events.

[bitsandfoxes]

Now that we have multiple scenes we could rename them to BugFarmLevel_1 / Level_2 respectively. Other than us noone knows what a "TransitionScene" is and what it's for. With the numeric postfix there is an implied hierarchy that helps with self documenting.

[bitsandfoxes]

This is nitpicking but please reset the transform on the TransitionScene/Scripts GameObject.

[semuserable]

Now that we have multiple scenes we could rename them to BugFarmLevel_1 / Level_2 respectively. Other than us noone knows what a "TransitionScene" is and what it's for. With the numeric postfix there is an implied hierarchy that helps with self documenting.

I have no strict preference to naming the scenes, but I prefer to give descriptive names. "Us" is developers who develop the package, so "we" understand what "TransitionScene" means. We can also document it.

[bitsandfoxes]

Now that we have multiple scenes we could rename them to BugFarmLevel_1 / Level_2 respectively. Other than us noone knows what a "TransitionScene" is and what it's for. With the numeric postfix there is an implied hierarchy that helps with self documenting.

I have no strict preference to naming the scenes, but I prefer to give descriptive names. "Us" is developers who develop the package, so "we" understand what "TransitionScene" means. We can also document it.

But it's not just "us developers" who get to see and use it, right? We ship it as sample with our package to users. And they should not need to read the documentation to know which scene is the first they should want to open.

[semuserable]

Now that we have multiple scenes we could rename them to BugFarmLevel_1 / Level_2 respectively. Other than us noone knows what a "TransitionScene" is and what it's for. With the numeric postfix there is an implied hierarchy that helps with self documenting.

I have no strict preference to naming the scenes, but I prefer to give descriptive names. "Us" is developers who develop the package, so "we" understand what "TransitionScene" means. We can also document it.

But it's not just "us developers" who get to see and use it, right? We ship it as sample with our package to users. And they should not need to read the documentation to know which scene is the first they should want to open.

As I was saying, I have no strong preference about scene namings. If in Unity community it's better to name scenes like Level_n, then sure, let's do that.

[semuserable]

Updated.

[bitsandfoxes]

Looks good to me! Thanks!