Rideable not working only for players pf2e

[ChrisPMohr]

I just installed Rideable and am having an issue using the module in a player account, but it works fine on a GM account. Using either the mount hotkey, mount button, or mount macro have no effect when logged in as a player account. I have disabled all modules other than Rideable, routinglib, and the module for the adventure path I'm using. I've confirmed that the player is the owner of both the mount and rider actors.

There's no errors in the console logs, but I do notice that if I right click on the mount actor, I see a log from MountingScript.js:455:13 which differs whether I'm logged in as the player or GM. This is from when I have both actors on the same scene, but not mounted.

As a GM I see:

Array [ {…} ]
0: Object { constructed: true, name: "Rosa", displayName: 20, … }
length: 1
<prototype>: Array []

(just the mount actor)

but as a player I see:

Array [ {…}, {…} ]
0: Object { constructed: true, name: "Rosa", displayName: 20, … }
1: Object { constructed: true, name: "Esmera", displayName: 20, … }
length: 2
<prototype>: Array []

(both the mount and the actor)

Module settings: Player:

GM:

Foundry: version 11.315 Rideable: version 2.19.5

[Saibot393]

For Rideable to work a GM has to be logged in. Reason being, that the module allows players to move tokens thy don't own (if they e.g. own the mount), which foundry won't allow, so instead the GM basically moves those tokens for them (automated by rideable).

[ChrisPMohr]

That would explain it. I was testing by myself, switching between player and GM accounts. Thanks!

On Sun, Feb 11, 2024, 3:47 PM Saibot393 @.***> wrote:

For Rideable to work a GM has to be logged in.

— Reply to this email directly, view it on GitHub https://github.com/Saibot393/Rideable/issues/65#issuecomment-1937865286, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABBT5D63I6PK7UXRH6PPPGDYTEU6FAVCNFSM6AAAAABDDZKX32VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZXHA3DKMRYGY . You are receiving this because you authored the thread.Message ID: @.***>

[Saibot393]

Note that a lot of automation modules that allow players to do things they normally couldn't, use similar ways of "outplaying" foundrys permission limitations, and therefore need a GM to be online