One Giant Event Sheet

I've been developing my game for a while using a single event sheet and setting every parameter as "if LayoutName = "Whateverthelayoutnameis", and then having all of my events under those for each layout. While everything works fine this way, I loaded up the debugger just to play around with, and it looks like stuff that should NOT be utilizing CPU actually is (very minimal, 0.1% here or there, but it adds up rather quickly).

Is the way I'm going about this wrong? Should I have an event sheet for each layout? Or is there a better way to do a one event sheet game?

Why do you need to use one event sheet?

I use one event sheet for each layout.Another event sheet(s) for animations,player,environment etc.It's much easier and cleaner.

DoCai - Originally I thought it would be easier to search for certain things. I suppose I could make an event sheet for each layout, but I have over 60 layouts; it might be a bit of pain at this point. I wouldn't count it out if I couldn't find a solution, however.

Similar thread with great info

You should use event sheet includes to share common events between layouts, and have a separate event sheet for layout-specific events. Having one sheet which checks the layout name will be harder to manage and unnecessarily degrade performance.

I was afraid of that :X

Thanks!