Old Chunk System Demo: Platform Maze
Old demo of my 3D chunk system for large game levels, previously hosted on my old personal portfolio website.
The system had a need to be able to generate physical connections between chunks, be they in the form of doors, bridges, tunnels, or whatever else. In this early experiment, each chunk has a square platform at the center and generates bridges leading outward, each of which has a randomized offset. Because neighboring chunks use the same coordinates to seed the random number generator when creating bridges, bridges leading out of one chunk should always connect with bridges leading in from their neighboring chunks (the exception is the first bridge leading out of the spawn chunk, which is a template I placed for convenience and thus should be the only case of a bridge not leading anywhere).
Read more on my blog about my progress with this system and my other projects.
Chunks in this demo also spawn chests that can be collected and "zombies" that follow and attack the player, although there is no health or score.
WASD to move
Space to jump
Escape to restart
Left shift to move slowly, which may help on the narrow bridges.
Ignore "rotate view" in the on-screen directions; the camera does not rotate.
After clicking "Play/Restart", click somewhere else to prevent the level from regenerating if you press Space.
The background for this page was made with JSplacement, a free tool for creating tiling textures that resemble armor, circuitry, and other artificial surfaces.
Status | Released |
Platforms | HTML5 |
Author | problemecium |
Genre | Platformer |
Made with | Unity |
Tags | 3D Platformer, Experimental, Procedural Generation, Top-Down |
Comments
Log in with itch.io to leave a comment.
Tip:
Unity's default UI setup activates the last control that was selected when the space bar is pressed on desktop platforms, so after clicking the start button, click somewhere else on the screen to deselect it so that when you jump it doesn't regenerate the maze.
For a quick demo like this I often don't get around to finding and addressing situations like this so apologies for the bug.