i am trying to goto my most recent death, i cant figure out how to select it from the other, nor can i click on either one.
im just wondering if im being an idiot or not
im on 1.19.1 forge

how do you even use that in forge 1.19? the version is not even supportet.

I cant click things in chat either. Im on 1.19.1. Using the artifacts from actions

other mods?

Same here, only mod I use and can't click in chat. 1.19.1 Fabric

ok. yeah, just tested. is valid 1 moment...

same here. 1.19,2 fabric

Good to know. I'll try writing out the waypoint with timestamp tomorrow, and see if it'll correctly set the goal.

I don't think you'll be happy using the timestamps yourself (it's not as easy as typing some chat output back in because the timestamp is in seconds since some fixed date and wp list shows them in a human readable format).

I still think a scheme like "death-n" is better than relying on timestamps,

That's essentially preventing duplicate names by forced renaming, you can do that yourself as well (#sethome and bedwaypoints would still need some change though).

especially because this issue about clicking is still not resolved.

Have a look at #3592. Until it's merged and released (can take quite some time for the release to happen) I suggest you use the CI build.

Btw on a note that's more related to this issue, I can confirm that none of the chat clicks I tried work at all, including but probably not limited to #set page selection and clicking for setting details, and of course waypoints, like reported by OP.

Known and fixed in #3592. This bug does indeed affect all chat buttons.

Also autocomplete is pretty broken too, idk if that's tracked yet.

I don't think there is an issue for it, but it's been known for a looong time now. Probably since it exists.

Ok so the CI build isn't for 1.19.2. Are there any breaking changes or do I just need to change the version number?

the timestamp is in seconds since some fixed date

I assume it's UNIX time, I don't have an issue with using that if necessary.

That's essentially preventing duplicate names by forced renaming

I'd argue that especially since, like you said, the chat click fix will take a while to release, that would be an acceptable bandaid fix.

I suggest you use the CI build

I'll try that. Is it up-to-date with the rest of baritone? And most importantly, compatible with 1.19.2? It looks like the branch is 9 commits behind, and one of those commits seems to also mess with chat clicking. Seems like I might have to do some manual merging...

I don't think there is an issue for it, but it's been known for a looong time now. Probably since it exists.

Maybe that could be fixed by using the vanilla autocomplete for / commands? Earthcomputer's clientcommands mod has working autocomplete, and afaik it's because it just injects into clientside vanilla commands. It'd mean dropping the #, but at least it might work?

well, if you look at the 1.19.2 pr changes (#3597), yeah it's just version number changes in a few files...

Is there any way to access waypoints other than their name or clicking? By DB practice we should have a unique ID, it makes sense for it to be the same here. Maybe make it go like "death-1", "death-2" etc.

By fixing the click mechanic we're just putting a bandaid on the problem. There is a command to select waypoints by name, and that command should always work no matter what. Clicking is a different interface that should also work, but it shouldn't be a fix for broken commands.

Chat buttons are just a convenient way to run commands so if the command was broken like you implied there would be no way for the chat gui to work. The reason why the clickable chat text can distinguish between equally named waypoints while you cannot is that it uses undocumented internal forms of the waypoints command to specify waypoints by timestamp (which is the unique id you proposed, you can see it in the output of #waypoints list)

Good to know. I'll try writing out the waypoint with timestamp tomorrow, and see if it'll correctly set the goal. I still think a scheme like "death-n" is better than relying on timestamps, especially because this issue about clicking is still not resolved.

Btw on a note that's more related to this issue, I can confirm that none of the chat clicks I tried work at all, including but probably not limited to #set page selection and clicking for setting details, and of course waypoints, like reported by OP. Also autocomplete is pretty broken too, idk if that's tracked yet.

#3592 is now merged.