Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reverse engineer level data #3

Open
Calinou opened this issue Sep 19, 2021 · 0 comments
Open

Reverse engineer level data #3

Calinou opened this issue Sep 19, 2021 · 0 comments
Labels
help wanted Extra attention is needed mvp Required for a working game

Comments

@Calinou
Copy link
Owner

Calinou commented Sep 19, 2021

Related to #1.

To play the game, we need to figure out how to load levels and their textures from the original MDK data files. From what I've seen, levels are loaded using some kind of chunk system, but we can probably load everything at once on today's hardware (at least as an initial implementation).

I don't know how gameplay triggers were stored (in the level files or in the executable). Gameplay triggers will need to be ported somehow, likely by creating Area nodes at run-time that are connected to functions implemented in GDScript.

Gameplay triggers are quite varied, and many of them are only used in a single level. Some examples:

  • Display a message at the center to the screen.
  • Open/close a door.
  • Start a different music track.
  • End the level.
    • In some levels, this happens after a boss was killed instead.
@Calinou Calinou added mvp Required for a working game help wanted Extra attention is needed labels Sep 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed mvp Required for a working game
Projects
None yet
Development

No branches or pull requests

1 participant