Baritone: Baritone 1.16 and fabric support?

[c0d3rb0y]

Ok so we're already at 1.16.1, and a lot of servers are updated. When is baritone 1.16? And also, can we have official support for fabric? Fabritone just isn't the same...

[l1ving]

no

[l1ving]

stop asking

[c0d3rb0y]

On Wed, Jun 24, 2020 at 8:58 PM Dominika [e-mail] wrote:

stop asking

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cabaletta/baritone/issues/1823#issuecomment-649167819,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APSTV5ZRFVOG4CFBSMPYESTRYKVLDANCNFSM4OHSMPXQ
.

So for 1.16 or fabric? Im fine with no fabric, but 1.16 baritone is a need.

[l1ving]

1.16 literally came out 2 days ago. You'll find out when and if baritone updates.

[UltraBlackLinux]

why even fabric? Just use json patches

[TlNT0]

when is it coming out????!!!

[TlNT0]

like how hard can it be, you just have to change some code to make it work for this version and add a few blocks

[l1ving]

then do it yourself if it's that easy.

[c0d3rb0y]

Idk how to do java :/

On Sat, Jun 27, 2020 at 5:06 PM Dominika [e-mail] wrote:

then do it yourself if it's that easy.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cabaletta/baritone/issues/1823#issuecomment-650637786,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APSTV54LG4CT5Q7R6EOHE63RYZUN5ANCNFSM4OHSMPXQ
.

[l1ving]

wasn't replying to you.

[UltraBlackLinux]

@TlNT0 If it was that easy, to "change some code" and "add a few blocks" than it would have been done already. Every block has specific properties tose have to get added (propably via a list but if not, every block would have a seperate codeblock - class? - those are Including Hitbox, properties,...)

[l1ving]

not to mention MCP 1.16 won't be released for at least another few weeks (fabric kinda do be on top tho 😳)

[Krunkeneer1]

Thanks for making baritone, its fun and easy to use. 👍
When MCP is released will work on baritone 1.16 be started?

[l1ving]

I didn't make Baritone, I'm just a collaborator.

I have no idea when MCP 1.16 will be released, they usually take their time. Yarn 1.16 was released 2 minutes after the official Minecraft 1.16 release, which is just one of the reasons why I greatly prefer Fabric over Forge / MCP

[c0d3rb0y]

Woah, didn't actually know it was THAT fast. I saw Fabric 1.16 like 5hr
after release.

On Tue, Jun 30, 2020 at 9:17 AM Dominika [e-mail] wrote:

I didn't make Baritone, I'm just a collaborator.

I have no idea when MCP 1.16 will be released, they usually take their
time. Yarn 1.16 was released 2 minutes after the official Minecraft 1.16
release, which is just one of the reasons why I greatly prefer Fabric over
Forge / MCP

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cabaletta/baritone/issues/1823#issuecomment-651821336,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APSTV57YNGX77SAJABOIMXLRZHXZFANCNFSM4OHSMPXQ
.

[l1ving]

No, there were already fabric builds a few minutes after release lmao

[c0d3rb0y]

so now that mcp 1.16.1 is out is 1.16 in the making?

https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon
Virus-free.
www.avast.com
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Tue, Jun 30, 2020 at 10:13 AM Dominika [e-mail] wrote:

No, there were already fabric builds a few minutes after release lmao

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cabaletta/baritone/issues/1823#issuecomment-651857820,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APSTV54COYCNXKPMMA7NJ5LRZH6H3ANCNFSM4OHSMPXQ
.

[l1ving]

it has been literally 11 days, chill

[TlNT0]

then do it yourself if it's that easy.

already did!

[l1ving]

k

[c0d3rb0y]

ok well where is the 1.16 thing, man. not saying to domnika. rather saying to TlNT0

[ClientKitty]

Ok well now the realese has been out for a while Soo...

[l1ving]

sooooooooooo...............................................

[CDAGaming]

Please try to be patient. Releasing it now bares the risk of unintented side effects and bugs, as at this time it is releasable but isnt atm to give more time for testing.

This aditionally applies to Fabritone, as Im awaiting a specific bug fix to rebase fabritone for 1.16.1. To those also saying it isnt the same as this, can feel free to use the other branch of fabritone which IS 1:1 with Baritone.

[Brhsoftco]

@CDAGaming @dominikaaaa @leijurv do you have dev docs? I'm interested in your collective project. Understandably, this is the "wrong place" to insert such a query, but I cannot find an adequate avenue. I wish to ask if you would be willing to allow me to become a contributor for Baritone? I have been monitoring progress of the 1.16.1 port, and feel I may be able to help it along in a more official manner (other than a fork).

[l1ving]

https://baritone.leijurv.com

[CDAGaming]

@Brhsoftco Anyone can contribute for Baritone via pull requests. Though as for 1.16.1 Baritone, it is in a 99% feature complete state, with merely testing remaining on it and an issue with #goto portal

If you do wish to contribute, investigation into #goto portal on 1.16.1 is very much needed to deem the 1.16.1 port releaseable with 100% parity, as this appears to be the only mismatch.

[Brhsoftco]

@CDAGaming many thanks for the input. In relation to your portal problem, '#goto portal' will not execute at all, and complains of block metadata errors, but '#goto nether_portal' works flawlessly.

@dominikaaaa thanks for the API reference, but I was referring to code coverage.

[Brhsoftco]

And that was for the 1.16.1 Git branch as well.

[CDAGaming]

@Brhsoftco For #goto nether_portal, it executed but doesnt actually go towards the portal block for some unknown reason, which is the issue. #goto portal wouldnt work since portal was changed to nether_portal as it's block id

[Brhsoftco]

interesting. It looks like specifying minecraft:nether_portal other than nether_portal causes baritone to immediately locate the correct block.

[Brhsoftco]

seemingly, minecraft:* does not make a difference as I thought earlier. It looks like on intervals of two, baritone will locate the correct portal block. E.g. running '#goto nether_portal' twice will result in a correct path on the second try (at least from my tests).

[Brhsoftco]

finally, I've narrowed this down to one issue from my tests. Upon navigating to a portal in baritone, the player will hit a collision mesh with the portal and hence, teleports to the nether. In doing this, baritone's pathing system seemingly goes haywire. If one instructs '#stop', then '#goto nether_portal' once more, it will work correctly. The only issue that I have come across is when one tries to cross over dimensions, other than that, it works (for me at least). When you instruct baritone #stop immediately after running a #goto nether_portal, it will of course, stop. However, running the command again causes baritone to once again locate the correct block. This leads me to believe that when terrain is generated in another dimension, baritone may have already started pathing before the terrain has successfully generated (e.g. before the portal blocks have loaded into the chunk).

[l1ving]

I think it would be helpful if this was moved to a properly documented issue so it doesn't get lost :p