What kinds of weird dreams have you all been having lately? Generally I feel like I have a lot of dreams but most of them don't stick in my head or I don't write them down.
I had a dream about working at a hospital that was actually a crime front that felt like it went on for forever but I remember like none of the details.
I think someone mentioned before dreaming about speedrunning but I don't think that's ever happened to me.
Zombie Glitch allows you to take unlimited hits from all sources except for pits which will instant kill regardless.
During the zombie state, checkpoints can still be activated. Collecting a coin breaks the zombie state but restores the player to full health. Music will be broken after the death sound effect is played, but other sound effects will still happen.
Clip of glitch being discovered:
The glitch can be performed by pausing roughly half a second before receiving damage while already hurt. If timed too late, the player will reset to the last checkpoint, but if timed too early, the normal death animation will play. If no death animation plays and the player is labeled 'Dead', the glitch is now active.
Upon finishing a level during the zombie state, the game will complete the level normally. However, once all the lives are removed to add to the score, the game will send the player back to the start, and enable practice mode.
Despite this, the next level is still unlocked and the level is counted as complete, even in this state. Proof with save info deleted beforehand:
This glitch will be useful for later levels in the run where waiting on enemy cycles is more constant, but likely not for Area A.
Avoids the longest remaining gem in the game and is fairly doable. Only issue is you have a single chance at it (you have to go through the entire gem path again to try another time), but doing it second try is still faster than doing the normal way perfectly.
Due to the addition of an auto-splitter, I've decided to add a section on the leaderboard to include them once people start to use it. In the future I would like to require it/sort times by it, but for the time I would just highly recommend it so that we can have a more fair leaderboard.
Not sure which way is the best to contact you so I'll try a few:
If you wouldn't mind, could you change the game name to Overgrowth instead of Lugaru? Lugaru is the prequel to this game and it was sorta tough to find the right game when it's listed under the wrong place.
Also if you have no intentions to add rules or do any custom things for the page I would be willing to moderate or super mod the page since I already do that for a few leaderboards. I have another couple of runners that are interested in doing this so it'd be cool to have someone actively here.
Let me know your thoughts.
I've contacted the devs and asked them to make 1.0 always available so that any runners could be on an even playing field if and when they decide to update the game, especially if it breaks extended climbing or blocks us from reaching the upper areas of maps.
(Obviously we could just back up the data ourselves and revert it on our own but this seemed like a simpler and more easily accessible way if they were willing to help out.)
Got a response back pretty quick and if you go into the game properties on Steam, in betas there's now an option to revert back to 1.0. Just thought I'd let everyone know about so once we go past the current patch everyone knows the way to go back.
Not sure if anyone else has ran into this issue, but recently after quitting once the red message shows up after Hacker and re-entering for me makes it where OBS no longer records the game capture until you disable and re-enable the capture. If you don't, the next 3-4 minutes of gameplay won't show up, but will randomly re-enable itself sometime later (for me it was Office). This doesn't seem to happen when quitting the game normally to reset or otherwise, but only when it plays the segment after being forced to leave and coming back.
I just wanted to throw that out there in case other people didn't know to keep their eye out for it, and see if anyone else that has encountered the issue has some sort of solution or reasoning for it happening. It doesn't seem to 100% happen, but just sporadically.