OH THAT'S RIGHT - I MOVED THEM TO A NEW HUD!!

I didn't set the new HUD to parallax to 0% x 0%

Thank you Thank You THANK YOU!!

I've been going nuts for over an hour!!

Thank You!!!!

I'm starting to think I may not understand how to use a boolean. Typically I use a global variable, I set them to 0 or 1 and everything works just ducky. This time I decided to use booleans true/false and everything seems to be hit or miss.

On start of layout 'hasWon' and 'hasLost' are set to false and the sprites 'win' and 'loss' are set to invisible.

When the player wins 'hasWon' is set to True, but the 'win' sprite doesn't become visible, same if the player loses.

Am I misunderstanding the point of booleans? Or are my events wrong?

Any help is appreciated.

drive.google.com/file/d/16OU53KRUeUIfoJdDlEta5aaYizqHSGLR/view

—,

YES!!! That's it!!

Thank You!!!

I am so excited - I'm starting a new game tonight.

Thank you. Thank you. Thank you.

—,

Thank you for your reply.

I'm still missing something.

You said: "on start of layout + if layoutname = "Level 2""

I have 'on start of layout'. I assume "+ if layoutname" is referring to a condition and that you're referring to the condition from your last comment "compare two values", yes?

I go there and under 'value' I put: LayoutName = (is equal to)

but when I try to type Level 2 and I get a syntax error.

Am I over thinking or way off?

Please don't give up on me, I know I'm close.

Thanks again.

—

Well, you're probably going to think I'm being silly, but before I build the game I build a simple template.

This template is setup so that it has 1 event sheet with local storage that remembers the levels the player has completed. Each level is a different layout. I have 15 different layouts that represent 15 different levels. They don't look different now, but they will when I build the game. All the sprites are on a sprite sheet so I can keep track of them.

What I'm looking to do is to create a new challenge for every level. In this case I'm just looking to get the challenge buttons to show up on each level.

I want to use just 1 event sheet for the game.

So on level 2 I'm trying to make the sprite named challenge A appear and maybe blink. And then on level 2 I want to make challenge B appear and maybe have a sine behavior. Then on level 3 have challenge A sprite to have the sine behavior and challenge C sprite do something different.

It's my way of learning, by doing. When I build the actual game I will have actual challenges, but this how I plan out the game and test it out.

What I don't know is how to put on the event sheet: Only on level 2 do X and only on level 7 do Y.

Here is a fresh copy of what I'm working with.

drive.google.com/file/d/1FKffLty7Y3I867e4k-YP_echr8Mds8t7/view

Any help is appreciated.

I've never played pokemon, but by your description it sounds like when the player is overlapping another object or comes in contact with another object (the door) the player is teleported to another layout - I'm a close?

If that's what you're looking for, there is a demo create to show you how to do that: howtoconstructdemos.com/a-system-of-doors-portals-to-travel-between-layouts

Sorry, if I'm way off, I'm now too.

calminthenight,

Thank you. I'll work on that tonight.

I know how to get it to stop, but I can't think off the top of my head how I would get it going again. But I will figure that out tonight.

Thanks again.

Is there away to specify layout X or level X in the event sheet.

If every level is nearly the same, but every 5th level a new challenge is added. Is there away to say Level 5 do Y, then Level 10 start doing Z?

There has to be away. I can't image there needs to be a specific event sheet for each level.

Thank you.

calminthenight

Thank you for the info.

I think I figured it out, at least for the player. When the player comes out of the transport sometimes the phone is tilted to the side a bit so it's rematerializing (so to speak) inside the wall. This could be important information for future transporter operations (lol)

Guess I'll be doing some MacGyvering to fix that.

Thanks again.