Event Sheet Management

0 favourites
  • 7 posts
From the Asset Store
Very simple code without excess options (15 events for server and 11 events for client)
  • So I am new and trying to get better at C2 and wanted to see how you manage your Event Sheets. What are some common/best practice's? Things you have seen work better etc.. Do you have an Event Sheet for every layout or one for everything.

    Thanks

    Brett

  • Hey jbmoyer!

    Great question!

    Actually, I'm willing to read the opinion of our fellow developers!

    I normally have a general event sheet with the core gameplay functions so that all levels (layouts) are referenced to it.

    Tutorials, menus, or cutscenes are handled with other event sheets. If a a tutorial is similar to another menu/or cutscene, then I would implement just one event sheet to handle them.

    I wouldn't recommend having an event sheet per layout if those layouts perform similar functions.

    Memory/resourceswise I don't know if having more event sheets hinders the performance of your project. If there is someone who knows the answer to this question, it will be appreciated!

    Let us know what you're working on! If you need help, just ask!

  • I use a ton of groups for different functions so i can enable/disable them on the fly

  • Someone made a post not long ago , search for best practices ...

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • I use 1 layout and 1 event sheet for all my levels, 1 layout and sheet for main menu, and 1 layout for storing all the graphics. I have an additional event sheet for input code though which is included in both game and menu layouts.

    But yeah I find it easier to have 1 sheet for the bulk of my code, I think its cleaner and easier to work with that way.

  • Here

    construct.net/en

  • Great tips guys, thank you

    Brett

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)