[BUG] CLIENT SPOOF NEXTGEN/LEGACY - Custom and other modes don't work properly

VilaED commented 2 weeks ago

LiquidBounce Branch

Both

LiquidBounce Build/Version

v0.15.2 NEXTGEN - b98 Legacy

Operating System

Windows 10

Minecraft Version

1.8.9.+

Describe the bug

Not even a version of liquidbounce with client spoof is working, the branch bypass I'm trying on this rust server minebuilders.me and when I select a mode in client spoof or deactivate anti forge it is not possible to enter the "rust v2 or other game" game mode it gives me It accuses me of using fabric/forge and not being able to enter it, I come to the conclusion that the payload is just alternating the name but not making the necessary changes. please correct

Steps to reproduce

go connect to server: minebuilders.me (using this one because I know that it blocks forge/fabric and clients in addition to labymod and their client, however, not even vanilla can enter because liquidbounce does not bypass)
select rust v2 game mode
you won't be able to get in

Client Log

[09:59:02] [Render thread/INFO]: [CHAT] You cannot use this client to play Minebuilders!
[09:59:02] [Render thread/INFO]: [CHAT] There's too many issues with the client you're using that will cause instability in-game. Please use Vanilla, LabyMod, or Minebuilders client.
[09:59:04] [Render thread/INFO]: [CHAT] Please pick a server from the menu!
[09:59:06] [Render thread/INFO]: [CHAT] You cannot use this client to play Minebuilders!
[09:59:06] [Render thread/INFO]: [CHAT] There's too many issues with the client you're using that will cause instability in-game. Please use Vanilla, LabyMod, or Minebuilders client.
[09:59:06] [Render thread/INFO]: [CHAT] Please pick a server from the menu!
[09:59:08] [Render thread/INFO]: [CHAT] Please pick a server from the menu!
[09:59:10] [Render thread/INFO]: [CHAT] Please pick a server from the menu!
[09:59:11] [Render thread/INFO]: [CHAT] You cannot use this client to play Minebuilders!
[09:59:11] [Render thread/INFO]: [CHAT] There's too many issues with the client you're using that will cause instability in-game. Please use Vanilla, LabyMod, or Minebuilders client.
[09:59:12] [Render thread/INFO]: [CHAT] Please pick a server from the menu!
[09:59:14] [Render thread/INFO]: [CHAT] Please pick a server from the menu!
[09:59:16] [Render thread/INFO]: [CHAT] Please pick a server from the menu!
[09:59:18] [Render thread/INFO]: [CHAT] Please pick a server from the menu!
[09:59:20] [Render thread/INFO]: [CHAT] Please pick a server from the menu!
[09:59:22] [Render thread/INFO]: [CHAT] Please pick a server from the menu!
[09:59:24] [Render thread/INFO]: [CHAT] Please pick a server from the menu!

Screenshots

VilaED commented 2 weeks ago

@1zun4 bot added tag for legacy but it is for nextgen too

ccetl commented 2 weeks ago

In nextgen it successfully spoofs the brand initially but there might be packets about the registry sent from fabric. This shouldn't be an issue on most servers tho since most servers just check for the brand. An easy fix would probably be blocking all packets that contain the word "fabric" or something.

VilaED commented 1 week ago

Contributor

yes it is bad because staffs /plugins and good anticheats can detect it i use flux and flux can bypass but nextgen no

@1zun4 @mems01 @superblaubeere27 @opZywl @ccetl

has solution?

opZywl commented 1 week ago

Hi, you is slayermaster on discord right? I remember talking to you on discord about this subject

1zun4 commented 1 week ago

I'm not even using a VPN... I had to use LiquidProxy Dedicated (VPN) to join their server + pass the AntiBot.

But now I am stuck:

What ever I click, nothing happens. Do you have any better server to try this on? I also feel like this issue you reported only is caused by ViaFabricPlus 1.8.X translation. Please tell me if you use protocol translation.

opZywl commented 1 week ago

I played this minigame as well; to access it, select the Rust V2 mode.

However, he forgot to mention that you can join the game using either the Vanilla client or the Minebuilders client. You can download the client to check its branding, but I believe that certain methods, like ViaFabric or protocols used by LiquidBounce, can't bypass the server restrictions—this includes the Legacy protocol.

I can access the game mode through the Legacy protocol. I remember that in the past, you had managed to bypass the restrictions using a resource pack spoof, but it looks like they’ve patched that method now.

And disable antiforge in legacy for join but legacy dont bypass rust v2 .-.

opZywl commented 1 week ago

@VilaED i send video for 1zuna trying join using nextgen

opZywl commented 1 week ago

legacy: https://youtu.be/C1GohvGp6z4

but v2 mode dont play

localpthebest commented 1 week ago

In nextgen it successfully spoofs the brand initially but there might be packets about the registry sent from fabric. This shouldn't be an issue on most servers tho since most servers just check for the brand. An easy fix would probably be blocking all packets that contain the word "fabric" or something.

ye i know that forge sends a packet with a list of all installed mods to the server maybe its the same for fabric?

ccetl commented 1 week ago

In nextgen it successfully spoofs the brand initially but there might be packets about the registry sent from fabric. This shouldn't be an issue on most servers tho since most servers just check for the brand. An easy fix would probably be blocking all packets that contain the word "fabric" or something.

ye i know that forge sends a packet with a list of all installed mods to the server maybe its the same for fabric?

There are (packet IDs) "fabric:custom_ingredient_sync", "c:register", "c:version", "minecraft:register". "minecraft:unregister", "fabric:registry/sync/complete", "fabric:registry/sync/direct", possible more, possible less sent by fabric. Some mods might send their own packets. All those packets might expose the client as being fabric to the server.

localpthebest commented 1 week ago

In nextgen it successfully spoofs the brand initially but there might be packets about the registry sent from fabric. This shouldn't be an issue on most servers tho since most servers just check for the brand. An easy fix would probably be blocking all packets that contain the word "fabric" or something.

ye i know that forge sends a packet with a list of all installed mods to the server maybe its the same for fabric?

There are (packet IDs) "fabric:custom_ingredient_sync", "c:register", "c:version", "minecraft:register". "minecraft:unregister", "fabric:registry/sync/complete", "fabric:registry/sync/direct", possible more, possible less sent by fabric. Some mods might send their own packets. All those packets might expose the client as being fabric to the server.

yeesh thats quite a lot to get rid of

EclipsesDev commented 5 days ago

@VilaED in legacy it seems lunarclient brand spoof works just fine

CCBlueX / LiquidBounce