You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a "Custom Action" for a Hero System character sheet, it can't figure out who invoked the command and instead relies on the current speaker settings.
For players, this is fine, as they usually only control one character each. But for the GM, this often means the OCV of the last speaker is used, instead of the OCV of the character sheet containing the invocation.
I am very new to both javascript and the Roll20 API or I might have attempted a fix.
Ideally, the best thing would be to be able to autodetect being invoked from a character sheet. Failing that, having an option like:
--as:Heritic
would greatly aid in running games.
The text was updated successfully, but these errors were encountered:
I know we discussed this on the API Forum, but for the benefit of others who might see the above request, it is in version 1.2.1, and is discussed here: https://app.roll20.net/forum/permalink/9956423/
Alas, although this USED to work, recent changes to the Roll20 API have broken it again. Currently the --as: option does not work embedded in a character sheet, although it still works in chat.
Okay, it mostly works. If I put a roll like
As a "Custom Action" for a Hero System character sheet, it can't figure out who invoked the command and instead relies on the current speaker settings.
For players, this is fine, as they usually only control one character each. But for the GM, this often means the OCV of the last speaker is used, instead of the OCV of the character sheet containing the invocation.
I am very new to both javascript and the Roll20 API or I might have attempted a fix.
Ideally, the best thing would be to be able to autodetect being invoked from a character sheet. Failing that, having an option like:
would greatly aid in running games.
The text was updated successfully, but these errors were encountered: