as well as the cutscene parser, I had another way to control game logic as you were playing – a monolithic state machine, which had gotten completely out of control by the end of the project! You can find it in Game::updatestate, and I kinda recommend checking this out even if you don’t read anything else! This controls things like triggering the start of more complicated cutscenes, where teleporters send you, the timing of the level completion animation, and other miscellaneous things that I just wanted to kludge in quickly. The states are numbered, and it counts all the way up to 4099, with gaps. When I was developing the game, I kept a notepad nearby with the important numbers written down – 1,000 triggers the collection of a shiny trinket, 3,040 triggers one particular level completion, 3,500 triggers the ending. This dumb system is the underlying cause of this amazing 50.2 second any% speedrun of the game.

I dunno, what can I say? I was young and more interested in getting something on the screen than implementing it properly. Maybe the best thing about VVVVVV’s source code is that is stands as proof of what you can hack together even if you’re not much of a programmer.

switch-то и то попонятнее и попроще в отладке и исправлении выглядит.

блокнотик с ключевыми state'ами, что характерно, все равно придется держать под руками.

Кстати, вышла за несколько лет до VVVVVV и изначально была бесплатной. А вскоре и сорцы открыли.

Та же Celeste была для меня на порядок сложнее (конечно она вышла позже сабжа).
Wings of Vi ещё сложнее, я её не осилил.