A few more random questions about this program

Can I just use conditional branches and variables the whole way through?I'd like to use the self switch and event pages as little as possible and rely on just making multiple variable names and conditional branches.I don't know why this method is easier for me it just is :/

And my second question is, can I just use on event page for events in an entire game?I'm being serious, I'd prefer it if it's possible.I'm just creating a tiny little game that is about a couple of hours long as a hobby but have trouble with the method shown in deb's tutorial despite it being detailed and clear.The variable stuff is graspable but im not gonna get event pages and self switches so I'd like to know if i could just not use em.

Event pages and self switches are actually simpler than variables...

Technically, no, you don't have to use self-switches and event pages. But using them makes your eventing so much easier. It's really worth the effort to learn them, and I promise they're not all that complicated. :)

Basically no, you don't have to use self-switches or multiple event pages with conditions.


But as Lunarea said, they are there for specific reasons and to make things easier for you - and not using them can get you into trouble or limit your options.


Consider this scenario: you have several treasure chests in your game. Each treasure should only be taken once of course.


Now, if you use a general switch to remember whether a chest had been opened or not, then you need one general switch per chest - that can be a lot of switches depending on the number of treasure chests in your game.


However, if you use self-switches, then each chest automatically has its own switch - because that is the special ability of self-switches, they are event-based and neither need a definition outside the event, nor can they affect other items.


And to top this, there is a limit to the number of general switches per game - the number of self-switches is effectively unlimited because they are stored in the events, not in the database.


An additional problem when using general switches for chests is that if you need another chest and decide to copy one of the existing chests, then with general switches you need to edit the new chest to give it a new general switch - with self-switches, that is automatic and you never need to edit the new chests after copying them.


And there are other examples, for example multiple event pages can not only have different sprites (without the use of change graphic commands), but they can also have different autonomous movement settings (which is simply impossible to make without multiple pages)...


So yes, you can make games without them - but it would be a lot easier for yourself if you take the time to learn how to use them.

After looking at her tutoria again it seems like she switches the variable on after she's done messing about in an event page.So it's like a less cluttered version of what I'd do.

She uses her variables in two ways it seems.the obvious one was the lottery and number based sections that had the usual stuff.The less obvious one was leaving some of them variable blank and just using them to house custom self switches with conditional branches, which I did not notice at all till a few whiles ago.

Ill figure out self switches later on, think there's a "seperate treasure chest event" tutorial on youtube somewhere

Capture.bmp