Download PNG • 397KB
Download PNG • 679KB
Download PNG • 354KB
Download PNG • 370KB
All this was done by harnessing the power of really really bad fps, and high cpu usage. When these requirements were met, I just continually slammed into any and all borders, only one failed and that was the river near Otto's house.
Hey thanks so much for discovering this! I had noticed this behavior occasionally when playing around with the game speed, but I didn't think it could be replicated in the wild!
Your hypothesis is spot on; there are invisible walls stopping players from moving through certain objects, and if the fps is drastically reduced, when the game calculates the player's position, it bypasses the wall entirely. And I think your solution is perfect as well, by increasing the thickness of the walls, even a delayed calculation should still end up 'in' the wall, preventing the player from moving through it.
Thanks so much!!
Just a hypothesis, I believe that the issue is that the only thing stopping you from going past these "obstacles" is a thin invisible wall that disappears when you break said obstacle(the boulders, and the barricade). With the river next to Otto's house, I believe it's a full on border, so I wasn't able to lag through it.
Maybe making the "invisible wall" I'm not sure exactly what it's called, a bit thicker would fix it?
I forgot to include a couple things, sorry about that, here they are now.
My computer, it's a old "gaming" computer, but it can barely run web browser games. I was quite sure I wouldn't be able to properly play the game on it, but I was curious as to why. I found my answer and it's this bug right here I reported.
Is it repeatable? 100 percent, I had some fun with it and repeated it 2-3 times.
This is fascinating, and the first time we've heard of this issue. Thanks for sharing it here!