[Bug] ESP broken in 26.2

[5-door]

Describe the bug

Activating ESP on 26.2 crashes the game.

Steps to reproduce

ESP Module Settings:

    - Mode - Shader
    - Outline Width - 1
    - Glow Multiplier - 0.500
    - Shape Mode - Lines
    - Fade Distance - 1.000
    - Entities Selected - All monsters except sulfer cube.  Bats and players also selected.
    - Color Mode - Entity Type
    - Toggle on Bind Release - Off
    - Chat Feedback - Off

Meteor Version

6a26187

Minecraft Version

26.2

Operating System

Windows

Before submitting a bug report

• This bug wasn't already reported (I have searched bug reports on GitHub).

• This is a valid bug (I am able to reproduce this on the latest dev build).

[FemBoysAreCut3]

26.2 isnt supported yet

[5-door]

26.2 isnt supported yet

Doesn't matter. The bug exists, regardless. Just here to inform the devs of the bug so they can look into it once it IS supported.

[barrygb]

how do you KNOW this bug happens? if i try to launch meteor on 26.2, it gives me a fabric error. How can you manage to find this bug pre-existance?

[5-door]

how do you KNOW this bug happens? if i try to launch meteor on 26.2, it gives me a fabric error. How can you manage to find this bug pre-existance?

Because I'm using Meteor on 26.2.

[barrygb]

how do you KNOW this bug happens? if i try to launch meteor on 26.2, it gives me a fabric error. How can you manage to find this bug pre-existance?

Because I'm using Meteor on 26.2.

yes, but meteor is only fabric if im correct, and fabric is VERY strict about mod versions(like all other loaders), attempting to load it will give you an error. You are ragebaiting.

[5-door]

how do you KNOW this bug happens? if i try to launch meteor on 26.2, it gives me a fabric error. How can you manage to find this bug pre-existance?

Because I'm using Meteor on 26.2.

yes, but meteor is only fabric if im correct, and fabric is VERY strict about mod versions(like all other loaders), attempting to load it will give you an error. You are ragebaiting.

I'm just barely smart enough to update source code of Minecraft mods to newer versions of Minecraft and compile a working .jar file. Especially with a little help from AI. However, I'm not smart enough to dive deeper into the source code to correct bugs and crashes. I downloaded the Meteor source code repository, updated it to 26.2 and got it to successfully compile and work with Fabric. Been using it for about 3 weeks now.

I don't rage bait. You asked how I knew, I answered with the simplest and direct to the point answer possible.

[barrygb]

how do you know that the AI will keep the code exactly to its original? An AI can easily mess up and ruin some code, ESP could be perfectly fine in 26.2, but AI messed it up.

[5-door]

how do you know that the AI will keep the code exactly to its original? An AI can easily mess up and ruin some code, ESP could be perfectly fine in 26.2, but AI messed it up.

Because the code to update the version is separate from the code that actually runs the modules.

[Watchedfungus88]

how do you know that the AI will keep the code exactly to its original? An AI can easily mess up and ruin some code, ESP could be perfectly fine in 26.2, but AI messed it up.

u might just be stupid bruv.

[Frko5000]

Okay you might be smart enough to update the code but that does not matter 26.2 is not the current meteor client version. Even if you update the code perfectly that doesnt concern meteor client

[5-door]

Okay you might be smart enough to update the code but that does not matter 26.2 is not the current meteor client version. Even if you update the code perfectly that doesnt concern meteor client

It has already been stated, I completely understand that. My post was nothing more than a courtesy just in case any of the devs felt like scribbling a note to themselves to have a look at it, if and when they do update it to 26.2.

[OrangeMan432]

Okay you might be smart enough to update the code but that does not matter 26.2 is not the current meteor client version. Even if you update the code perfectly that doesnt concern meteor client

It has already been stated, I completely understand that. My post was nothing more than a courtesy just in case any of the devs felt like scribbling a note to themselves to have a look at it, if and when they do update it to 26.2.

you might want to check out #6439 and bug test that instead

[Frko5000]

Okay you might be smart enough to update the code but that does not matter 26.2 is not the current meteor client version. Even if you update the code perfectly that doesnt concern meteor client

It has already been stated, I completely understand that. My post was nothing more than a courtesy just in case any of the devs felt like scribbling a note to themselves to have a look at it, if and when they do update it to 26.2.

Ah okay i understand :3 sorry if i was mean