Ok this is madness. The code is a mess, I have no idea how the hell anyone can work like that....
But that's reality so screw it. For some reason 3 of the 76 events in Episode 2 are empty here, they never trigger, and thus never increment event counter, may have to do with compressed version of something, but this means it's virtually impossible to get 74.
Also, to try and make some sense out of this madness I put together a half-assed kinda-mod-thinggie. No idea if it works for everyone or whatever, and to be honest I don't care all that much, but this lists all friggin events, with lines of code that lead to said event, meaning you get some context. Is it perfect? No it isn't. The requirements are still a mess. Still, this helps somewhat, and the only way to do a good job here would be to refactor half of the crazyness in the game files.... Seriously AT LEAST put all events in a list and get the number of events by counting the events that are marked as done... Like e2_events = [0, 0, 0, 0 ...... 0].
Well either way I just wanted to point out that the art is amazing and the story is great but the code is a nightmare, so bugs and quirks and stuff are a given. Extracting this on game folder will put a "Cheats" text on bottom left of the screen, clicking it will bring up a menu with a few kinda-helpful stuff. Missing Events only works for Episode 2 for now, and you will probably have to check julias_events (Or others) manually to figure out some stuff, but hey, at least there will be some info...
Also
Celaviegroup seriously you need to do some refactoring ASAP. God you must be going through hell dealing with bugs, seriously, nobody deserves working like that, especially since it's totally unnecessary. Ok, Ren'Py probably pushes you towards madness, but it's always possible to improve things, and I'd be happy to give you some pointers, I don't usually do Ren'Py but I've been coding for some good 20 years, and I just made sense of your code (and figured a way to check it automatically) in a few hours, so it's not like I have no idea what I'm talking about...
p.s.: Oh yeah, I actually wrote a parser that extracts events from the code. I'm not attaching it here 'cause it's not supposed to run with the game, I just used it to generate the json, still if anyone's curious, load each .rpy file and evaluate the indentation to create a tree. The tree is saved as JSON, then the mod attached here traverses the tree to find where events are changed to "1", and prints all the parent nodes and context leading to that. Thus, for each event you basically get the lnes of code that will be executed and what is necessary for them to trigger the event, including conditions you have to fulfill and choices you have to make.
I may improve on this, or not, or whatever. But if anyone's interested in the parser just ask, and if anyone wants to changes this or whatever, feel free,