Some information

Operating system: Windows 10 (amd64) version 10.0
Java version: Java: 1.8.0_51
Minecraft version: 1.16.3
Baritone version: 1.6.1
Forge mods (if used): None

Exception, error or logs

Please find your latest.log or debug.log in this folder and attach it to the issue
latest.log

How to reproduce

Add your steps to reproduce the issue/bug experienced here.

1. put the ReplayMod and Baritone into the Aristois mods folder and launch MC + Aristois
2. record a replay
3. When you try to watch a replay the game will crash

Modified settings

To get the modified settings run #modified in game
AllowParkour - True
chatControl - false

Final checklist

• I know how to properly use check boxes
• I have included the version of Minecraft I'm running, baritone's version and forge mods (if used).
• I have included logs, exceptions and / or steps to reproduce the issue.
• I have not used any OwO's or UwU's in this issue.

Looks like you are using Fabritone not Baritone

This is a duplicate. Please search before creating an issue next time.

@ZacSharp I'll say this one time. Baritone == Fabritone. The Fabritone name was also deprecated and no longer in usage and due to the parity, @leijurv did grant me usage of the Baritone name on the Fabric branch as well.

here is a log that wasn't using aristois and just had baritone and replay mod, it crashes when you try to watch a replay in the replay viewer https://paste.ee/p/HmdTw

It used to be that the "default" Fabritone people used was too different from Baritone to support it in this repo, and people were supposed to go to the Fabritone repo.

Fabritone's vanilla branch is just Baritone with Fabric mappings and is allowed to use the Baritone name, and as such is supported here.

ok, so changed mappings is ok, new features not
Thanks for the clarification

different* not difficult, my bad

@ZacSharp Yup! Since every fabritone feature was merged into Baritone officially, there's no further need to retain the Fabritone name, hence why in the repo, every occurrence of Fabritone's name (Except the repo name itself) was changed back to Baritone

Sorry if i seemed rude as well, mostly was a tad irritated since I'm trying to quickly get people permanently off of the older Fabritone and into the 1:1 version

I'll make this info into an issue I can link in a bit

I'll make this info into an issue I can link in a bit

I'll make this info into an issue I can link in a bit

Ooof rip my internet. What's the first version of Fabritone to be 1:1 Baritone @CDAGaming?

https://gitlab.com/CDAGaming/fabritone/-/jobs/793196448

October 15th was the initial rollout that kicked off the migration that removed the Fabritone name and re-synced everything to be 1:1

The migration completed later that day/October 16th at most.

Thanks!

@CDAGaming
I wrote this based comments like #2027 (comment), #1997 (comment), #1972 (comment), #1969 (comment), #1940 (comment), #1938 (comment), #1934 (comment), #1918 (comment), #1871 (comment), #1858 (comment), #1844 (comment), #1842 (comment), #1841 (comment), #1835 (comment), #1828 (comment), #1821 (comment), #1705 (comment), #1608 (comment), #1540 (comment), #1365 (comment), #1362 (comment), #1335 (comment), #1299 (comment), #1284 (comment), #1257 (comment), #1188 (comment), #1106 (comment), #1105 (comment), #1090 (comment), #1080 (comment), #1075 (comment), #647 (comment) but maybe things changed.
Is this a combined issue tracker for both now or are issues only existing with fabric still invalid?

I'll say this one time.

This sounds a bit unfriendly to me. Did I get you wrong there or are you telling me that I'm dumb because I didn't get that fabritone is now supported here yet?

So issues that only exist on fabric and are not specific to a mod are left open in case CDA wants to handle them?
Or should they be closed and redirected to the fabritone repo for CDA to handle them there?

If it's on latest Baritone Fabric, then they should be opened here.

Then it is 100% like Forge except the main devs won't fix it if it does not occur without fabric

Yes, but the issue is just as valid and someone else is free to fix it.

What???

If it is literally the exact same thing but with different mappings then I see no reason why the name should be different 😉

There is something to be said for maybe fabric having a handful of differences from vanilla, just like forge. For example, when we first came up with the Forge build way back when, freelook didn't work on specific versions of forge and it was a huge massive pain in the ass to fix (the actual fix wasn't complicated, it was 7dd881a, but figuring out exactly what commit in what version of forge caused the issue was super annoying, as well as determining the workaround needed).

So, here's how I see it: Issues that only exist on baritone forge but not vanilla are valid, and shouldn't be closed. Issues that only exist in the presence of specific forge mods are borderline. This is not a clear cut case. Some patches (for example, 7e3a2d3) have the sole purpose of making Baritone more compatible with other Forge mods. Other times, the mod is Doing Something Weird. Replaymod appears to be creating a minecraft world object with certain fields set to null, judging from that stack trace? java.lang.NullPointerException: null at baritone.cache.WorldProvider.initWorld.

I think fabric should be treated the same way, ideally. I think in an ideal world we would want this remapping to be a build step, like how Forge for 1.15 is a build step that reruns with different mappings. Then the jars would be in baritone's official releases. At that point I would be 100% fine with fabric being treated exactly the same as forge has been, as I described ^. Until that point, I do not personally plan to handle issues that only exist on fabric (but maybe CDA might want to). Issues that only occur in the presence of specific other fabric mods should probably be ignored.

Issues that cannot be reproduced on the latest commit on any mainline MC version branch of this repo (baritone) should still be ignored unconditionally, IMO. This can include anything from the old Fabritone builds, or even old Baritone builds.