[BUG] Grappled token desync and placement update issues for non-GM players

[Zimnyte]

Foundry VTT 13.347
DnD 5e 5.1.2
Rideable 4.0.15

When a Player or Trusted Player grapples a creature, the grappled token sometimes desynchronizes from the grappler’s position. This can cause the grappled token to appear far away from the actual grappling token. Additionally, the new D&D5e movement automation prevents moving in directions where the grappled token is incorrectly registered, leading to inconsistent movement behavior.

Furthermore, when a Player/Trusted Player attempts to change the placement of a grappled target an error is thrown, placement is technically updated but the visual update only occurs after the grappling token is moved.

FVTT_Desktop_Client_0OhPqccNix.mp4

[Saibot393]

Regarding the D&D5e movement blocking: Code to prevent this is already included and will be activated as soon as the system updates (probably)

The delay/desync might is probably an artefact of the token blocking and should probably be fixed together with that

For the position update i will release a patch momentarily

[Saibot393]

The error for player based grapple placement change should now be fixed with v4.0.16

[Zimnyte]

Updated to latest D&D5e version, same with rideable and the same behavior occurs.

[Zimnyte]

When two tokens are selected at the same time, you can move them. However, if you move only the grappling token, it remains blocked. The desync/displacement still occurs on the player’s account.

[Zimnyte]

There is some weird behavior even on GM's account as well.

FVTT_Desktop_Client_oUkedwzNIR.mp4

[Saibot393]

Some of the behaviour, at least the part with the blocking, should be fixed with a future version of the system. There is a bit of code that is already developed and with which rideable can already interact to prevent this, that is simply not released with the current versions

[Saibot393]

I have released a temporary work around for the token blocking problem with v4.0.19

[Zimnyte]

Thanks. I thought that you meant the 5.1.2 DND update and not a major 5.2 release.

[Saibot393]

I am actually a bit confused when exactly/under which version the required code for the intended rideable fix releases, i know that it has been accepted ~2 weeks ago but it seems like it is marked a low priority, so the work around will have to suffice for now