# Yet Another Hollow Knight Demake **URL:** \ **Category:** Show & Tell\ **Tags:** game\ **Created:** [September 6, 2026, 6:50pm UTC](https://forum.makecode.com/t/yet-another-hollow-knight-demake/45741 "2026-09-06T18:50:36Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![teal256](https://avatars.discourse-cdn.com/v4/letter/t/f1d935/32.png) [@teal256](https://forum.makecode.com/u/teal256)\ **Post date:** [September 6, 2026, 6:50pm UTC](https://forum.makecode.com/t/yet-another-hollow-knight-demake/45741/1 "2026-09-06T18:50:36Z")
I know it’s already been done a few times, but my goal is to be as faithful to the game as possible (within reason). This project is VERY early in development, and I have only implemented basic running and jumping. But I took time to polish the movement as much as possible by taking pixel and frame measurements of the actual game and tuning parameters to match. Most of the time spent to reach this point was on creating all the player animations. > **[Hollow Knight basic movement tech demo](https://arcade.makecode.com/S16853-06911-75913-29495)** > > Made with ❤️ in Microsoft MakeCode Arcade. Assuming I don’t give up, I plan on “at least” completing King’s Pass. My next goals are: - Smoother/more accurate camera movement - Nail attacks in four directions - A basic enemy, probably a Crawlid - Damage, healing, soul, and the HUD I will post a new version once I add these features. ---
**Author:** ![kirbob](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/kirbob/32/34880_2.png) [@kirbob](https://forum.makecode.com/u/kirbob)\ **Post date:** [September 6, 2026, 11:43pm UTC](https://forum.makecode.com/t/yet-another-hollow-knight-demake/45741/2 "2026-09-06T23:43:02Z")
best hollow knight movement ive ever seen ---
**Author:** ![coppercode](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/coppercode/32/26022_2.png) [@coppercode](https://forum.makecode.com/u/coppercode)\ **Post date:** [September 6, 2026, 11:54pm UTC](https://forum.makecode.com/t/yet-another-hollow-knight-demake/45741/3 "2026-09-06T23:54:15Z")
ok the movement is very good but the camera needs some work but that should be easy to fix best of luck! ---
**Author:** ![teal256](https://avatars.discourse-cdn.com/v4/letter/t/f1d935/32.png) [@teal256](https://forum.makecode.com/u/teal256)\ **Post date:** [September 7, 2026, 7:49pm UTC](https://forum.makecode.com/t/yet-another-hollow-knight-demake/45741/4 "2026-09-07T19:49:30Z")
> I took time to polish the movement as much as possible by taking pixel and frame measurements of the actual game and tuning parameters to match. Turns out I completely forgot about terminal velocity! This changes the time it takes to jump, so I’ll have to tune it again for the next update. ---
**Author:** ![teal256](https://avatars.discourse-cdn.com/v4/letter/t/f1d935/32.png) [@teal256](https://forum.makecode.com/u/teal256)\ **Post date:** [September 9, 2026, 2:34am UTC](https://forum.makecode.com/t/yet-another-hollow-knight-demake/45741/5 "2026-09-09T02:34:58Z")
So right now I’m implementing a freeze-frame upon player damage, but I can’t find a sensible way to do it. It needs to: - Pause all physics and animations - Start two animations and render their first frames on the exact frame the damage happens - Apply a screen shake during the freeze-frame My first solution was to pause game updates until the timer ran out, but this made it impossible to shake the screen during the pause. I’m pretty sure I wouldn’t be able to render new images either because it would wait until the next update. The only other solution I could think of would be to save the velocity and acceleration of all sprites into an array, set these to 0, and then apply these values in the array back to the sprites. This would effectively freeze physics without surpressing the game update. Does anyone know of a simpler way to pause physics without freezing the entire game? ---
**Author:** ![TheEarth](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/theearth/32/34579_2.png) [@TheEarth](https://forum.makecode.com/u/TheEarth)\ **Post date:** [September 9, 2026, 5:21pm UTC](https://forum.makecode.com/t/yet-another-hollow-knight-demake/45741/6 "2026-09-09T17:21:36Z")
maybe use scene.pop or push or something if your using js but that creates a new “scene” with nothing in it so youd have to have everything re render itself without falling or anything but that’s only in js and its gonna lag ---
**Author:** ![TheEarth](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/theearth/32/34579_2.png) [@TheEarth](https://forum.makecode.com/u/TheEarth)\ **Post date:** [September 9, 2026, 5:21pm UTC](https://forum.makecode.com/t/yet-another-hollow-knight-demake/45741/7 "2026-09-09T17:21:42Z")
> [@teal256](#): > > Assuming I don’t give up I need to use this more often tbh ---
**Author:** ![teal256](https://avatars.discourse-cdn.com/v4/letter/t/f1d935/32.png) [@teal256](https://forum.makecode.com/u/teal256)\ **Post date:** [September 9, 2026, 6:45pm UTC](https://forum.makecode.com/t/yet-another-hollow-knight-demake/45741/8 "2026-09-09T18:45:16Z")
Yeah, this would probably just be even more complex than my existing solution. It works for now, it will just become less manageable once I add more moving entities to the game. Unless there’s a way to copy and load the entire state of the game without looping through every sprite? I could be misunderstanding what scene.pop and scene.push do, I couldn’t find any documentation ---
**Author:** ![teal256](https://avatars.discourse-cdn.com/v4/letter/t/f1d935/32.png) [@teal256](https://forum.makecode.com/u/teal256)\ **Post date:** [September 11, 2026, 4:52pm UTC](https://forum.makecode.com/t/yet-another-hollow-knight-demake/45741/9 "2026-09-11T16:52:59Z")
I have a short update on the project: It’s most likely going to be a week or more until the next playable version is out, as I am trying to perfect each feature as I add them. In addition to many bug fixes and other improvements, here is a quick sneak peek of some new (unfinished) features! **Hud appear animation:** ![ezgif-2e1279889c0224a9](https://us1.discourse-cdn.com/flex020/uploads/makecode/original/3X/e/7/e70e4165fedd2b3462f179ff10e42b22aa5b5b0d.gif) **Player damage:** ![ezgif-2ed8700bd3fdd98f](https://us1.discourse-cdn.com/flex020/uploads/makecode/original/3X/c/c/cc8f156abe747f9bb472c8c45747bf33e1cf9448.gif) **Hard falls:** ![ezgif-21e91fd877aea6f2](https://us1.discourse-cdn.com/flex020/uploads/makecode/original/3X/2/6/263a5c052e7da5cf1d3840d6b72530813ee5141b.gif) **Look up & down:** ![ezgif-29455f28b72954e3](https://us1.discourse-cdn.com/flex020/uploads/makecode/original/3X/7/8/786541b9c8746b91c84029b2d3e50fd77dd03d25.gif) Some other notable changes are: - Smoother camera - Lots of player animation fixes - Coyote time - Lowered resolution slightly and re-tuned all movement (result of a measuring error while making the first version) - Terminal velocity ---
**Author:** ![teal256](https://avatars.discourse-cdn.com/v4/letter/t/f1d935/32.png) [@teal256](https://forum.makecode.com/u/teal256)\ **Post date:** [September 17, 2026, 9:41pm UTC](https://forum.makecode.com/t/yet-another-hollow-knight-demake/45741/10 "2026-09-17T21:41:39Z")
Ok, it’s gonna take a lot longer than expected to release the next version, BUT it’s for some very good reasons. First of all, the original code had become super messy because I didn’t really know what I was doing. So I’m rewriting the entire project from scratch and taking advantage of things like sprite data and more functional programming. Also, I’ve been learning how to datamine Hollow Knight and have realized that despite my best efforts, there were still many inaccuracies in my original project. On the bright side, datamining will make it MUCH easier to find various parameters. For example, how I previously calculated run speed was by screen-recording Hollow Knight, frame-advancing the video in a media player, taking screenshots of individual frames, and measuring the pixel distances between the frames. Now all I have to do is look at the “RUN\_SPEED” constant in CinematicUnityExplorer and multiply it by a scale factor. **TL;DR: I’m redoing everything, but “properly” this time. Development has temporarily slowed down, but it should be much faster from now on.**