Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(+1)

My god. This was amazing. It really reminded me of the video of corridor digitals. Really love this. How did you do that?

(1 edit) (+1)

Thanks for the comment! Indeed i got the inspiration from Corridor Digital's video.

It's really simple, you just gotta wrap your head around the mechanic. Preety much you have a script on the player that "Lists" (kind of like arrays but endless) stuff like the player's position, and when he shoots.

I store all of that data in a "loop" container, and when the game is "reset" i.e when you run out of time, i spawn "puppets" that use the lists in their corresponding loop to mimick the player's actions.

(+1)

Isnt that like really memory heavy?

Frankly it doesn't seem like it. It's on a FixedUpdate() so it only updates 60 times a second. At worst a loop can last 30s so a list can be 3600 entries tops. Might seem like alot but it's like 3600 Vector3s or bools or floats, it's maybe slightly RAM intensive but i doubt it has a significant impact on performance.