An alternative FreeCam implementation.

[commandblock2]

This alternative implementation is theoretically 100% legit since this is based on changing the position/angle of the camera.

Demo: https://www.bilibili.com/video/BV1rv411N7SC/
The commit is here: https://github.com/commandblock2/LiquidBounce/commit/4d54b5a8e4b48dd68779678b22ee81f9b3aeb54d

I wrote this simply to prove this idea could work and this is currently not intended to merge to the official branch as there could be tons of improvement (

• able to cancel player movement input
• absolute coord choice (doesn't move according to player)
• proper injection near net/minecraft/client/render/GameRenderer.java:1043 (maybe) instead of in Camera class
• etc.
  ) and I am just too lazy/busy to make any of that. Anyone who wants it should make the improvement and make the pr.

0 commandblock2 committed to commandblock2/LiquidBounce

added FreecamAlternative

[suicidemouse33]

@commandblock2 kinda late but this is actually a good idea, because some freecams which don't change the pos/angle of the camera causes instabans

[Plumer Man]

config issue

[privatetaj]

This post is deleted!

[A Former User]

I am interested in this idea, but I instead decided to improve the way the module responds to packets. I made a module that displays the packet type and its parameters in chat to get an idea of how an AFK player sends movement packets, and that way I made FreeCam module behave the same way.

[suicidemouse33]

@mems ok

[suicidemouse33]

@bobismymanager liquidbounce in fortnite

[A Former User]

@mems said in An alternative FreeCam implementation.:

I am interested in this idea, but I instead decided to improve the way the module responds to packets. I made a module that displays the packet type and its parameters in chat to get an idea of how an AFK player sends movement packets, and that way I made FreeCam module behave the same way.

It ended up not being a good idea, so I tried your method and here are the results:

https://streamable.com/s4wwtm

and

https://streamable.com/4xsjwp

It's a great idea, because you don't have to modify packets. The only small thing I have noticed is that you have to (at least from the way I coded it) detect if buttons are pressed with InputUtils.isKeyPressed(mc.window.handle, mc.options.forwardKey.boundKey.code instead of mc.options.forwardKey.isPressed for example.

EDIT: Found a completely new method, which doesn't require detecting button presses with InputUtils, basically nothing related to it anymore.